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

Introduction to Unified Checkout
- Unified Checkout Flow
- Server-Side Set Up
- Client-Side Set Up
  - Loading the JavaScript Library and Invoking the Accept Function
  - Complete Integration Examples
- Transient Tokens
  - Transient Token Format
  - Token Verification
  - Dual-Branded Cards
- Authorizations with a Transient Token
- Capture Context API
  - Features
  - Client Version History
  - 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
    - Enrolling in Google Pay
    - Managing Google Pay Authentication Types
  - Manage Permissions
    - Managing Permissions as a Direct Merchant
    - Managing Permissions as a Portfolio Administrator
- 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
  - JSON Web Tokens
  - Unified Checkout Integration Examples
    - Unified Checkout with Authorization
    - Unified Checkout with Sale
    - Unified Checkout with Sale and Decision Manager
    - Unified Checkout without Service Orchestration
  - Supported Locales
  - Reason Codes

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

On This Page

Supported Locales

The locale field within the capture context request consists of an ISO 639 language code, an underscore (_), and an ISO 3166 region code. The locale controls the language in which the application is rendered. The following locales are supported:

ar_AE

bg_BG

ca_ES

cs_CZ

da_DK

de_AT

de_DE

el_GR

en_AU

en_CA

en_GB

en_IE

en_NZ

en_PK

en_US

es_AR

es_CL

es_CO

es_ES

es_MX

es_PE

es_US

fi_FI

fr_CA

fr_FR

he_IL

hr_HR

hu_HU

id_ID

it_IT

ja_JP

km_KH

ko_KR

lo_LA

ms_MY

nb_NO

nl_NL

pl_PL

pt_BR

ro_RO

ru_RU

sk_SK

sl_SI

sv_SE

th_TH

tl_PH

tr_TR

ur_PK

vi_VN

zh_CN

zh_HK

zh_MO

zh_SG

zh_TW