Unified Checkout Integration - Beta Release
- How It Works

Unified Checkout Integration Flow
- Server-Side Setup
- Capture Context
  - Required Fields
  - Requesting the Capture Context
  - Example: Capture Context Request
- Client-Side Setup
  - Setting Up the Client
  - Loading the Javascript Library and Invoking the Accept Function
    - Example: Request to Initialize the SDK
  - Add the Button Widget and Payment Acceptance
    - Example: Basic Setup with Full Sidebar
    - Example: Basic Setup Using the Embedded Widget

Transient Tokens
- Transient Token Format
- Token Verification

Payment Authorizations with Tokens
- Example: Authorization Request with a Transient Token

Transient Token Payment Details
- Retrieving Transient Token Payment Details Using the REST API
- Example: Retrieving Transient Token Payment Details Response

Data Validations

Supported Countries

Supported Languages

On This Page

Server-Side Setup

The server-side component provides this information:

A transaction-specific public key. This key is used by the customer's browser to protect the Unified Checkout Integration transaction.

An authenticated context description package that manages the payment experience on the client. It includes payment options available, payment interface styling, and interaction methods.

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