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

completeMandate.type

This field is required to run the complete mandate and is used to indicate how a payment should be processed.

Possible values:

AUTH

: Authorize the payment and capture the funds at a later date.

CAPTURE

: Perform a sale. A sale is a combined authorization and capture in a single request.

PREFER_AUTH

: Perform an authorization if possible. If a payment method requires the funds to be captured immediately, then Unified Checkout captures the payment.

Back to top