API Overview

Digital Accept Secure Integration Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introducing Digital Accept Secure Integration Product Suite

Flex API v2
- Flex API v2 Integration Task List
- 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
- JSON Web Tokens

Introduction to Unified Checkout
- Unified Checkout Quick Start
  - Step 1: Enable Unified Checkout
  - Step 2: Set Up the Server-Side Component
  - Step 3: Set Up the Client-Side Component
  - Step 4: Configure Unified Checkout
  - Step 5: Test Your Unified Checkout Integration
- Unified Checkout Flow
- Payment Methods
  - Cards
    - Pay with Token
  - Digital Wallets
    - Apple Pay
      - Enrolling in Apple Pay
      - Preparing a Device for Testing Apple Pay on Unified Checkout
      - Apple Pay UI
    - Google Pay
      - Enrolling in Google Pay
      - Managing Google Pay Authentication Types
      - Google Pay UI
    - Click to Pay
      - Enabling Click to Pay in the Gateway Portal
        Set Up Customer Authentication for Visa Click to Pay
        Click to Pay Customer Authentication
      - Click to Pay UI
      - Click to Pay UI Guidelines
      - Click to Pay UI Examples
- Server-Side Set Up
- Client-Side Set Up
  - Loading the JavaScript Library
  - Complete Integration Examples
- Configuration
  - Configure the Unified Checkout Merchant Experience
    - Enable Unified Checkout
    - Configure Payment Options
    - Customize the Unified Checkout Look and Feel
    - Look and Feel UI Examples
    - Configure Customer Data and Payment Flow
    - Capture Context Fields in the Gateway Portal
    - Manage Permissions
      - Managing Permissions as a Direct Merchant
  - Process Payments with Unified Checkout
  - Webhooks Support
- Sessions API
  - Capture Context Components
    - Allowed Card Networks
    - Target Origins
    - Allowed Payment Types
    - Client Version
    - Auto-check Enrollment
    - Button Type
    - Customize Button Text
    - Complete Mandate
      - completeMandate.type
      - completeMandate.decisionManager
      - completeMandate.consumerAuthentication
      - completeMandate.tms
    - Capture Mandate
      - captureMandate.CPF
      - captureMandate.requestSaveCredentials
      - captureMandate.showConfirmationStep
      - captureMandate.billingType
      - captureMandate.requestEmail
      - captureMandate.requestPhone
      - captureMandate.requestShipping
      - captureMandate.shipToCountries
    - Include Card Prefix
    - Email Autolookup
    - Mobile as Identity for Click to Pay
  - Example: Unified Checkout Complete Capture Context
  - Validating the Capture Context
  - Session Validation
- Transient Tokens
  - Transient Token Format
  - Token Verification
  - Dual-Branded Cards
  - Authorizations with a Transient Token
- Test Your Configuration
  - Unified Checkout Test Cards
  - Visa and Mastercard Click to Pay Test Cards
  - Test Cards for Authentication by Click to Pay
  - Test Authentication
  - Handle Errors
  - Reason Codes
- Payment Details API
- JavaScript API Reference
- Update to Unified Checkout Version 1
  - Update Reason Codes
  - Version 1 Update Checklist
- Appendix
  - JSON Web Tokens
  - Supported Locales
  - Security Recommendations
  - PCI Compliance
  - Client Version History

Processing Authorizations with a Transient Token
- Authorization with a Transient Token
- Authorization and Creating TMS Tokens with a Transient Token

On This Page

Sessions API

Use the Sessions API to generate a capture context. The capture context contains all of the merchant-specific parameters that tell the front-end JavaScript library what to do within your payment experience.

Back to top