API Overview

Click to Pay Drop-In UI Developer Guide
- Recent Revisions to This Document

Introduction to the Click to Pay Drop-In UI
- Click to Pay Customer Workflows
  - Recognized Click to Pay Customer
  - Unrecognized Click to Pay Customer
  - Guest Customer

Click to Pay Drop-In UI Flow
- Add Click to Pay to a Merchant Account
- Enable Click to Pay
  - Enabling Click to Pay Drop-In UI Using the API
    - Required Fields for Enabling Click to Pay Drop-In UI
    - Optional Fields for Enabling Click to Pay Drop-In UI
    - REST Example: Enabling Click to Pay Drop-In UI
  - Enabling Click to Pay in the Business Center

Server-Side Set Up

Client-Side Set Up
- Loading the JavaScript Library and Invoking the Accept Function
- Adding the Payment Application and Payment Acceptance

Transient Tokens

Payment Details API

Payment Credentials API

JavaScript API Reference

Unified Checkout Configuration
- Upload Your Encryption Key
  - Generate a Public Private Key Pair
  - Uploading Your Key Pair
- Manage Permissions
  - Managing Permissions as a Direct Merchant
  - Managing Permissions as a Portfolio Administrator
- Click to Pay Customer Authentication
  - Set Up Customer Authentication for Click to Pay
  - Enable Click to Pay Customer Authentication Using the API
    - Required Fields for Enabling Click to Pay Authentication
    - Optional Fields for Enabling Click to Pay Authentication
    - REST Example: Enabling Click to Pay Authentication
  - Enable Click to Pay Customer Authentication Using the Business Center

Update to Click to Pay Drop-In UI Version 1
- Update Reason Codes
- Version 1 Update Checklist

Click to Pay UI Guidelines
- Click to Pay UI Examples

Test Your Click to Pay Configuration
- Test Payment Details
- Handle Errors

Appendix
- Client Version History
- Customization Matrix
- JSON Web Tokens
- Reason Codes
- Supported Countries for Click to Pay
- Supported Locales

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

Email Autolookup

When you include Click to Pay as an

allowedPaymentType

, an automatic email lookup occurs when an email address is included in the capture context request in the

data.billTo.email

field.. If the user has a Click to Pay account but is not on a recognized device, a one-time password (OTP) screen appears and the user is prompted to enter their OTP. If the user does not have a Click to Pay account, the user must enter their card information manually. They will have the option to create a Click to Pay account.

Back to top