API Overview

About This Guide
- Recent Revisions to This Document
- Related Documents

Solution Overview

MID Structure

Smartpay Fuse Payment Services
- Smartpay Fuse Main Transaction Identifiers
- Authorization
  - Supported Authorization Features
  - 0£ Authorization
- Capture (Settlement)
- Authorization Reversal
- Credit (Refund)
  - Follow-on Credit
  - Stand-alone Credit
- Acquirer Cut-off Time
- Void
- Order Cancellation Workflow
- Payment Services Workflow

Tokenization

3-D Secure Payer Authentication Service

Alternative Payment Methods

Integration Methods
- Front-End Integration Methods
  - Secure Acceptance Hosted Checkout
  - Secure Acceptance Checkout API
  - Flex API
  - Microform Integration
- Back-End Integration Methods
  - REST API

Smartpay Fuse Portal Access

Transactional Security Keys

Reporting
- Smartpay Fuse Portal Reporting Overview
- Report Reconciliation

Reason Codes
- Reason Codes

Testing

On This Page

Flex API

Flex API

integration replaces the PAN field with a permanent token. The PAN field is encrypted during transmission to

Smartpay Fuse

for tokenization.

Flex API

integration should be used for mobile applications development when native code is required.

Flex API

offers these benefits:

Merchant-hosted payment page which allows you to apply for SAQ A-EP PCI DSS scope.

Full checkout page customization.

Flex API

only supports token creation. Other payment services like authorization, authorization reversal, capture, credit, sale, and void must be implemented using back-end API integration.

See the Digital Accept Secure Integration Developer Guide for more information.

Back to top