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

JSON Web Tokens

JSON Web Tokens (JWTs) are digitally signed JSON objects based on the open standard RFC 7519. These tokens provide a compact, self-contained method for securely transmitting information between parties. These tokens are signed with an RSA-encoded public/private key pair. The signature is calculated using the header and body, which enables the receiver to validate that the content has not been tampered with. Token-based applications are best for applications that use browser and mobile clients.

A JWT takes the form of a string, consisting of three parts separated by dots:

Header

Payload

Signature

This example shows a JWT:

xxxxx.yyyyy.zzzzz