Recent Revisions to This Document

About This Guide

Unified Checkout

Unified Checkout Flow
- Enabling Unified Checkout in the Business Center

Server-Side Set Up
- Capture Context

Client-Side Set Up
- Loading the JavaScript Library and Invoking the Accept Function
  - JavaScript Example: Initializing the SDK
- Adding the Payment Application and Payment Acceptance
  - JavaScript Example: Setting Up with Full Sidebar
  - JavaScript Example: Setting Up with the Embedded Component

Transient Tokens
- Transient Token Format
- Token Verification

Authorizations with a Transient Token
- Required Field for an Authorization with a Transient Token
- REST Example: Authorization with a Transient Token

Capture Context API
- Required Fields for Requesting the Capture Context
- REST Example: Requesting the Capture Context

Payment Details API
- Required Field for Retrieving Transient Token Payment Details
- REST Example: Retrieving Transient Token Payment Details

Unified Checkout Configuration
- Enable Digital Payments
  - Enabling Click to Pay
  - Enrolling in Google Pay
- Manage Permissions
  - Managing Permissions as a Direct Merchant
  - Managing Permissions as a Portfolio Administrator

Unified Checkout 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 Countries for Digital Payments A-D
- Supported Countries for Digital Payments E-K
- Supported Countries for Digital Payments L-R
- Supported Countries for Digital Payments S-Z

Supported Locales

Reason Codes

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

REST API

Server-Side Set Up

This section contains the information you need to set up your server. Initializing Unified Checkout within your webpage begins with a server-to-server call to the sessions API. This step authenticates your merchant credentials, and establishes how the Unified Checkout frontend components will function. The sessions API request contains parameters that define how Unified Checkout performs.

The server-side component provides this information:

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