API Overview

Unified Checkout Developer Guide
- Recent Revisions to This Document

Introduction to Unified Checkout

Unified Checkout Quick Start
- Step 1: Enable Unified Checkout
- Step 2: Set Up the Server-Side Component
- Step 3: Set Up the Client-Side Component
- Step 4: Configure Unified Checkout
- Step 5: Test Your Unified Checkout Integration

Unified Checkout Flow

Server-Side Set Up

Client-Side Set Up
- Loading the JavaScript Library
- Complete Integration Examples

Configuration
- Configure the Unified Checkout Merchant Experience
  - Enable Unified Checkout
  - Configure Payment Options
  - Customize the Unified Checkout Look and Feel
  - Look and Feel UI Examples
  - Configure Customer Data and Payment Flow
  - Capture Context Fields in the Smartpay Fuse Portal
  - Manage Permissions
    - Managing Permissions as an Administrator
- Process Payments with Unified Checkout
- Webhooks Support

Transient Tokens
- Transient Token Format
- Token Verification
- Dual-Branded Cards
- Authorizations with a Transient Token

Test Your Configuration
- Unified Checkout Test Cards
- Visa and Mastercard Click to Pay Test Cards
- Test Cards for Authentication by Click to Pay
- Test Authentication
- Handle Errors
- Reason Codes

Payment Details API

JavaScript API Reference

Appendix
- JSON Web Tokens
- Supported Countries for Digital Payments
- Supported Locales
- Update to Unified Checkout Version 1
  - Update Reason Codes
  - Version 1 Update Checklist
- Security Recommendations
- PCI Compliance

On This Page

captureMandate.billingType

PARTIAL

: Only the billing postal code and billing country are collected in the UI. Set to this value when you use relaxed address verification services (AVS). This includes markets where postal code and billing country are enough for successful payment processing.

NONE

: No fields are shown in the UI to capture cardholder billing details. If you are using the Complete Mandate, you must provide billing details in the capture context. All information that is collected from these fields is tokenized in the transient token and sent for payment processing. For information about which fields are required for payment processing, see the Payments Developer Guide.

FULL

: These fields are shown in the UI to capture cardholder billing details. When you include the billing details in the capture context, these details are pre-filled in the Unified Checkout UI. All information that is collected from these fields are tokenized in the transient token and sent for payment processing where the Complete Mandate is used.

Back to top