API Overview

Digital Accept Secure Integration Developer Guide
- Recent Revisions to This Document

Introducing Digital Accept Secure Integration Product Suite

Flex API v2
- Flex API v2 Integration Task List
- Generating the Capture Context
  - REST Example: Generating the Capture Context
- Validating the Capture Context
- Securing Payment Information
- Tokenizing Payment Information
- Validate the Transient Token
- Using the Transient Token to Process a Payment

Microform Integration v2
- How It Works
- PCI Compliance
- Getting Started
- Accept Card Information
  - Server-Side Setup
    - Capture Context
    - Creating the Server-Side Capture Context
    - Validating the Server-Side Capture Context
  - Client-Side Setup
  - Transient Tokens for Accepting Card Information
    - Transient Token Time Limit
    - Transient Token Response Format
    - Validating the Transient Token
    - Using the Transient Token to Process a Payment
- Accept eCheck Information
  - Server-Side Setup
    - Capture Context
    - Creating the Server-Side Capture Context
    - Validating the Server-Side Capture Context
  - Client-Side Setup
  - Transient Tokens for Accepting eCheck Information
    - Transient Token Time Limit
    - Transient Token Response Format
    - Validating the Transient Token
- Next Steps
  - Styling
  - Events
  - Security Recommendations
- Reference
  - JavaScript API Reference
    - Class: Field
    - Module: FLEX
    - Class: Microform
    - Class: MicroformError
    - Global
  - Capture Context API
    - REST Example: Requesting the Capture Context
  - Getting Started Examples
  - JSON Web Tokens
  - Browser Support
  - PCI DSS Guidance
  - Test Card Numbers

Introduction to Unified Checkout
- Unified Checkout Flow
  - Enabling Unified Checkout in the Smartpay Fuse Portal
- Server-Side Set Up
  - Capture Context
- Client-Side Set Up
  - Loading the JavaScript Library and Invoking the Accept Function
    - JavaScript Example: Initializing the SDK
    - JavaScript Example: Displaying the Button List
    - JavaScript Example: Client-Defined Trigger for Click to Pay or PAN Entry
    - JavaScript Example: Processing a Payment
  - Complete Integration Examples
    - JavaScript Example: Setting Up with Full Sidebar
    - JavaScript Example: Setting Up with the Embedded Component
- Transient Tokens
  - Transient Token Format
    - Example: Transient Token Format
  - Token Verification
  - Dual-Branded Cards
- Authorizations with a Transient Token
  - REST Example: Requesting an Authorization with a Transient Token
- Capture Context API
  - Features
  - Client Version History
  - Requesting the Capture Context
    - Required Fields for Requesting the Capture Context
    - REST Example: Requesting the Capture Context
  - Validating the Capture Context
- Payment Details API
- Unified Checkout Configuration
  - Webhooks Support
  - Enable Digital Payments
    - Enrolling in Apple Pay
    - Preparing a Device for Testing Apple Pay on Unified Checkout
    - Enabling Click to Pay
      - Set Up Customer Authentication for Visa
    - Enrolling in Google Pay
    - Managing Google Pay Authentication Types
  - Manage Permissions
- Test Your Unified Checkout Configuration
  - Test Payment Details
  - Customer Authentication
- Payment Methods
  - Cards
- Unified Checkout Appendix
  - Unified Checkout UI
    - Apple Pay UI
    - Click to Pay UI
    - Google Pay UI
    - Manual Payment Entry UI
    - Paze UI
  - JSON Web Tokens
  - Unified Checkout Integration Examples
    - Unified Checkout with Authorization
      - Example: Unified Checkout with Authorization
    - Unified Checkout with Sale
      - Example: Unified Checkout with Sale
    - Unified Checkout with Sale and Decision Manager
      - Example: Unified Checkout with Sale and Decision Manager
    - Unified Checkout without Service Orchestration
      - Example: Unified Checkout without Service Orchestration
  - Supported Countries for Digital Payments
    - Supported Countries for Digital Payments A-D
    - Supported Countries for Digital Payments E-K
    - Supported Countries for Digital Payments L-R
    - Supported Countries for Digital Payments S-Z
  - Supported Locales
  - Reason Codes

Processing Authorizations with a Transient Token
- Authorization with a Transient Token
  - Required Field for an Authorization with a Transient Token
  - REST Example: Authorization with a Transient Token
- Authorization and Creating TMS Tokens with a Transient Token
  - Required Fields for an Authorization and Creating TMS Tokens with a Transient Token
  - REST Example: Authorization and Creating TMS Tokens with a Transient Token

On This Page

Set Up Customer Authentication for Visa

Follow these steps to use the Smartpay Fuse Portal to enable customer authentication through

Click to Pay

. Authentication methods differ in each region and are dependent on the issuer, the cardholder device, and the

Click to Pay

configuration. These authentication methods are available:

3-D Secure

FIDO

Card verification value (CVV)

One-time password (OTP)

IMPORTANT

After you complete these steps, Visa determines which authentication method to use. When Visa determines that they will authenticate, they authenticate each

Click to Pay

transaction through the appropriate method. This may be a frictionless authentication or the customer may need to provide more information when required by the issuer.

Log in to the Smartpay Fuse Portal:

Test URL:

https://admin.smartpayfuse-test.barclaycard/ebc2

Production URL:

https://admin.smartpayfuse.barclaycard/ebc2/

If you are unable to access this page, contact your sales representative.

In the Smartpay Fuse Portal, go to the left navigation panel and choose Payment Configuration
> Unified Checkout
.

You must have

Click to Pay

enabled as a digital payment method in order to use this method of authentication. Click Manage
to view the digital payment methods that you have enabled.

If

Click to Pay

is not enabled, click On
next to

Click to Pay

.

Click Set up
under Value Added Solutions. The Value Added Solutions page appears.

Click Set up
to set up 3-D Secure. The 3DS page appears.

Enter the required information in the Merchant Details section. You must enter the information that is provided to you by

Barclays

or your processor

.

Step Result

This completes the authentication setup for the entered acquirer merchant ID and BIN. If you do not know what these values are, you must contact

Barclays

. Completing this information enables Barclays to send Visa the information that is required for authentication.

IMPORTANT

Charges for 3-D Secure may apply. You must speak with your acquirer for more information about the charges associated with 3-D Secure.

Back to top