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: 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
  - Support for Dual-Branded Cards
- Authorizations with a Transient Token
  - REST Example: Requesting an Authorization with a Transient Token
- Capture Context API
  - Features
  - Requesting the Capture Context
    - Required Fields for Requesting the Capture Context
    - REST Example: Requesting the Capture Context
  - Validating the Capture Context
- Payment Details API
  - REST Example: Retrieving Transient Token Payment Details
- JavaScript API Reference
  - Class: Accept
  - Class: AcceptError
  - Class: UnifiedPayments
- Unified Checkout Configuration
  - Enable Digital Payments
    - Enrolling in Apple Pay
    - Preparing a Device for Testing Apple Pay on Unified Checkout
    - Enabling Click to Pay
    - Enrolling in Google Pay
    - Managing Google Pay Authentication Types
    - Enrolling in Echeck/ACH Services
  - Manage Permissions
    - Managing Permissions as a Direct Merchant
    - Managing Permissions as a Portfolio Administrator
- Test Your Unified Checkout Configuration
  - Test Payment Details
  - Customer Authentication
    - Set Up Customer Authentication for Visa
    - Authentication Methods
- Unified Checkout Appendix
  - Unified Checkout UI
    - Apple Pay UI
    - Click to Pay UI
    - Google Pay UI
    - Manual Payment Entry UI
    - Pay with Bank Account UI
    - Paze UI
  - JSON Web Tokens
  - Client Version History
  - Webhooks Support
  - 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
    - Echeck Payment with a Transient Token
      - Example: Echeck Payment with a Transient Token
  - 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

Server-Side Setup

This section contains the information you need to set up your server. Initializing Microform Integration within your webpage begins with a server-to-server call to the sessions API. This step authenticates your merchant credentials and establishes how the Microform Integration front-end components will function. The sessions API request contains parameters that define how Microform Integration performs.

The server-side component provides this information:

A transaction-specific public key is used by the customer's browser to protect the transaction.

An authenticated context description package that manages the payment experience on the client side. It includes available payment options such as card networks, payment interface styling, and payment methods.

The functions are compiled in a JSON Web Token (JWT) object referred to as the capture context
. For information about JWTs, see JSON Web Tokens.