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

Getting Started

Microform Integration replaces the primary account number (PAN) or card verification number (CVN) field, or both, in your payment input form. It has two components:

Server-side component to create a capture context request that contains limited-use public keys from the Flex API v2 suite.

Client-side JavaScript library that you integrate into your digital payment acceptance web page for the secure acceptance of payment information.

Implementing Microform Integration is a three-step process:

Creating the Server-Side Capture Context

Setting Up the Client Side

Validating the Transient Token

Version Numbering

Microform Integration follows Semantic Versioning. Cybersource recommends referencing the latest major version, v2, to receive the latest patch and minor versions automatically. Referencing a specific patch version is not supported.

Upgrade Paths

Because of semantic versioning, every effort will be made to ensure that upgrade paths and patch releases are backwards-compatible and require no code change.