API Overview

Unified Click to Pay Developer Guide
- Pilot Release
- Recent Revisions to This Document

Introduction to Unified Click to Pay
- Enabling Click to Pay in the Business Center
- Upload Your Encryption Key
- Set Up Customer Authentication for Unified Click to Pay

Unified Click to Pay Customer Workflows
- Recognized Click to Pay Customer
- Unrecognized Click to Pay Customer
- Guest Customer
- Supplementary Flows
  - Link Card for a Returning Customer
  - Switch ID
  - Retrigger One Time Password

Unified Click to Pay Integration
- Server-Side Set Up
- Client-Side Set Up
  - Loading the JavaScript Library

Get Started with Unified Click to Pay
- initialize()
- getCards()
- checkout()
- initiateIdentityValidation()
- unbindAppInstance()

API Specifications
- Sessions API
  - Request Parameters
  - Response
  - Handle Errors
  - Validating the Capture Context
- initialize()
- getCards()
- checkout()
- initiateIdentityValidation()
- unbindAppInstance()

Test Your Click to Pay Configuration
- Test Payment Details

Appendix
- Client and Server Keys
  - API Authentication Keys
  - JWT Validation Keys
  - Client-Side PAN Encryption Keys
  - Token Management MLE Keys
- Client Version Changes
- JSON Web Tokens
- Merchant Boarding for Portfolio Users
  - Add Unified Click to Pay to a Merchant Account
  - Add Unified Click to Pay to an Existing Organization
  - Modify a Unified Click to Pay Configuration for an Organization
- Use Case Dictionary
- Supported Countries for Unified Click to Pay

On This Page

Merchant Boarding for Portfolio Users

This section contains information about enabling and configuring Unified Click to Pay for your merchants using the Business Center.

Prerequisites

You must meet these requirements to enable and configure Unified Click to Pay for your merchants:

Unified Checkout must be enabled at the portfolio level before it can be added to merchant accounts. To enable at the Unified Checkout at the portfolio level, contact your sales representative.

Create a REST API Shared Secret Key.

Enable message-level encryption.

Back to top