Recent Revisions to This Document

About This Guide

Digital Accept Overview
- Unified Checkout Integration
- REST APIs

Flex API
- Establish a Payment Session with a Capture Context
  - REST Example: Establishing a Payment Session with a Capture Context
- Validate the JSON Web Token
  - Retrieve the Public Key ID
  - Retrieve the Public Key
  - JAVA Example: Validating the Transient Token
- Populate the JSON Web Token with Customer Information
  - Constructing the JSON Payload
  - Generate a JWE (JSON Web Encryption) Data Object
  - Populate the Token Request

Unified Checkout
- Unified Checkout Flow
  - Enabling Unified Checkout in the Business Center
- Transient Tokens
  - Transient Token Format
  - Token Verification
- Capture Context API
  - Required Fields for Requesting the Capture Context
  - Optional Fields for Requesting the Capture Context
  - REST Example: Requesting the Capture Context
- Payment Details API
  - REST Example: Retrieving Transient Token Payment Details Response
- Unified Checkout Configuration
  - Upload Your Encryption Key
    - Generate a Public Private Key Pair
    - Uploading Your Key Pair
  - Enable Digital Payments
    - Enrolling in Apple Pay
    - Enrolling in Click to Pay
    - Enrolling in Google Pay
  - Manage Permissions
    - Managing Permissions as a Direct Merchant
    - Managing Permissions as a Portfolio Administrator
- 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
- Supported Countries for Digital Payments
- Supported Locales

Processing Authorizations with a Transient Token
- Authorization with a Transient Token
  - Required Fields for an Authorization with a Transient Token
  - REST Interactive Example: 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 Interactive Example: Authorization and Creating TMS Tokens with a Transient Token
  - REST Example: Authorization and Creating TMS Tokens with a Transient Token

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

REST API

Server-Side Setup

Initializing Unified Checkout within your webpage begins with a server-to-server call to the sessions API. This step is used to authenticate your merchant credentials, as well as set how the Unified Checkout frontend components will function. The sessions API request contains parameters that define how Unified Checkout will perform.

The server-side component provides this information:

A transaction-specific public key. This 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. It includes payment options available such as card networks, payment interface styling, and interaction methods.

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