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

Capture Context API

The capture context request contains all of the merchant-specific parameters that tell the frontend JavaScript library how to behave within your payment experience.

The capture context is a signed JSON Web Token (JWT) containing this information:

Merchant-specific parameters: manages the customer payment experience for the current payment transaction.

A one-time public key: secures the information flow during the current payment transaction.

For information on JSON Web Tokens, see JSON Web Tokens.

The capture context is signed with long‑lasting keys so that its authenticity can be validated.

You can define the payment cards and other application features in the capture context. Use the

allowedCardNetworks

field to define the card types. Available card networks:

American Express

Diners Club

Discover

JCB

Mastercard

Visa

Use the

allowedPaymentTypes

field to define the digital payment methods.

For more information on enabling and managing these digital payment methods, see these topics:

Enrolling in Apple Pay

Enrolling in Click to Pay

Enrolling in Google Pay

Endpoint

Production:

POST https://api.cybersource.com/up/v1/capture-contexts

Test:

POST https://apitest.cybersource.com/up/v1/capture-contexts