API Overview

Digital Accept Secure Integration Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introducing Digital Accept Secure Integration Product Suite

Flex API v2
- Flex API v2 Integration Task List
- Generating the Capture Context
- Validating the Capture Context
- Securing Payment Information
- Tokenizing Payment Information
- Validate the Transient Token
- Using the Transient Token to Process a Payment

Microform Integration v2
- How It Works
- PCI Compliance
- Getting Started
- Accept Card Information
  - Server-Side Setup
    - Capture Context
    - Creating the Server-Side Capture Context
    - Validating the Server-Side Capture Context
  - Client-Side Setup
  - Transient Tokens for Accepting Card Information
    - Transient Token Time Limit
    - Transient Token Response Format
    - Validating the Transient Token
    - Using the Transient Token to Process a Payment
- Accept eCheck Information
  - Server-Side Setup
    - Capture Context
    - Creating the Server-Side Capture Context
    - Validating the Server-Side Capture Context
  - Client-Side Setup
  - Transient Tokens for Accepting eCheck Information
    - Transient Token Time Limit
    - Transient Token Response Format
    - Validating the Transient Token
- Next Steps
- Reference
  - JavaScript API Reference
  - Capture Context API
  - Getting Started Examples
  - JSON Web Tokens
  - Browser Support
  - PCI DSS Guidance
  - WCAG 2.2 Compliance
  - Test Card Numbers

Introduction to Unified Checkout
- Unified Checkout Flow
- Server-Side Set Up
- Client-Side Set Up
  - Loading the JavaScript Library and Invoking the Accept Function
  - Complete Integration Examples
- Transient Tokens
  - Transient Token Format
  - Token Verification
  - Dual-Branded Cards
- Authorizations with a Transient Token
- Capture Context API
  - Features
  - Client Version History
  - Requesting the Capture Context
  - Validating the Capture Context
- Payment Details API
- JavaScript API Reference
- Unified Checkout Configuration
  - Webhooks Support
  - Enable Digital Payments
    - Enrolling in Apple Pay
    - Preparing a Device for Testing Apple Pay on Unified Checkout
    - Enabling Click to Pay
    - Enrolling in Google Pay
    - Managing Google Pay Authentication Types
    - Enrolling in Echeck/ACH Services
    - Enrolling in Alternative Payment Methods
  - Manage Permissions
    - Managing Permissions as a Direct Merchant
    - Managing Permissions as a Portfolio Administrator
- Test Your Unified Checkout Configuration
- Payment Methods
  - Cards
  - Online Bank Transfers
    - Bancontact
    - DragonPay
    - iDeal
    - MyBank
    - Multibanco
    - Przelewy24|P24
    - Tink Pay By Bank
    - Verify Status for Online Bank Transfers (PPRO Enabled)
    - Verify Status for Online Bank Transfers (Tink Pay By Bank)
    - Handle Responses
  - Buy Now, Pay Later
    - Afterpay
    - Handle Responses
    - Captures
  - Post-Pay Reference Payments
    - Konbini
    - Verify Status for Post-Pay Reference (PPRO Enabled)
    - Handle Responses
- Unified Checkout Appendix
  - Unified Checkout UI
    - Apple Pay UI
    - Click to Pay UI
    - Google Pay UI
    - Manual Payment Entry UI
    - Pay with Bank Account UI
    - Paze UI
  - JSON Web Tokens
  - Unified Checkout Integration Examples
    - Unified Checkout with Complete Mandate
    - Unified Checkout with Sale
    - Unified Checkout with Sale and Decision Manager
    - Unified Checkout without Service Orchestration
    - Echeck Payment with a Transient Token
    - Example: Unified Checkout Complete Capture Context
  - Supported Countries for Digital Payments
  - Supported Locales
  - Reason Codes
  - Unified Checkout Field Reference
  - Test Authentication
  - Click to Pay UI Guidelines
    - Click to Pay UI Examples

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
  - 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
- Capture Context API
  - Features
  - Client Version History
  - Requesting the Capture Context
  - Validating the Capture Context
- 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
  - Enable Click to Pay
    - Enabling Click to Pay
  - Manage Permissions
    - Managing Permissions as a Direct Merchant
    - Managing Permissions as a Portfolio Administrator
  - Click to Pay Customer Authentication
    - Set Up Customer Authentication for Visa Click to Pay
    - Authentication Methods
- Test Your Click to Pay Configuration
  - Test Payment Details
- Appendix
  - JSON Web Tokens
  - Reason Codes
  - Supported Countries for Click to Pay
  - Supported Locales

Processing Authorizations with a Transient Token
- Authorization with a Transient Token
- Authorization and Creating TMS Tokens with a Transient Token

On This Page

Test Payment Details

Use these test card numbers to test your Click to Pay configuration.

Combine the BIN with the card number when sending to Click to Pay.

Visa `Click to Pay` Test Cards

These Visa test cards can be added to your Click to Pay wallet. Replace the X in the card number with 0.

You can manage your Visa Click to Pay test cards and account here:

Production:
login

Test:
login

To manage Visa test cards for customer authentication, contact your implementation consultant or technical account manager.

IMPORTANT

These test cards are not valid for testing in production. To test in production, you must leverage production credentials.

Visa Test Card Numbers
Card Number	Expiration Date	CVV
46229431231X2700	12/2026	938
46229431231X2718	12/2026	605
46229431231X2726	12/2026	579
46229431231X2734	12/2026	141
46229431231X2742	12/2026	279
46229431231X2759	12/2026	669
439584XXX449X11X	12/2025	509
439584XXX282X11X	12/2025	693

These Visa test card numbers can be used to test ECI05 frictionless authentication. Replace the X in the card number with 4.

ECI05 Authentication Test Card Numbers
Card Number	Expiration Date	CVV
X6229X3123113723	12/2027	929
X6229X3123113731	12/2027	217

These Visa test card numbers can be used to enroll in Passkey Service. Replace the X in the card number with 4.

Passkey Enrollment Test Card Numbers
Card Number	Expiration Date	CVV
X3958X0327800110	12/2027	832
X3958X0328300110	12/2027	474

Mastercard `Click to Pay` Test Cards

Mastercard test cards can be added to your Click to Pay wallet. You must retrieve Mastercard test cards from their Click to Pay test page: #test-cards

Mastercard has different test cards for retrieving tokenized and non-tokenized data. Cybersource recommends that you use these test cards as follows:

Test cards to retrieve PAN data: Use these cards when the customer is completing checkout as a one-time guest and does not have a Click to Pay account or want to create one.

Test cards to retrieve token data: Use these cards for tokenized Click to Pay transactions.

You can manage your Mastercard Click to Pay test cards and account here:

Live:
enroll

SBX:
enroll

To manage Mastercard test cards for customer authentication, contact your implementation consultant or technical account manager.

Back to top