Recent Revisions to This Document

About This Guide

Digital Accept Overview
- Unified Checkout Integration
- REST APIs

Flex API
- Establish a Payment Session with a Capture Context
  - REST Example: Establishing a Payment Session with a Capture Context
- Validate the JSON Web Token
  - Retrieve the Public Key ID
  - Retrieve the Public Key
  - JAVA Example: Validating the Transient Token
- Populate the JSON Web Token with Customer Information
  - Constructing the JSON Payload
  - Generate a JWE (JSON Web Encryption) Data Object
  - Populate the Token Request

Unified Checkout
- Unified Checkout Flow
  - Enabling Unified Checkout in the Business Center
- Transient Tokens
  - Transient Token Format
  - Token Verification
- Capture Context API
  - Required Fields for Requesting the Capture Context
  - Optional Fields for Requesting the Capture Context
  - REST Example: Requesting the Capture Context
- Payment Details API
  - REST Example: Retrieving Transient Token Payment Details Response
- Unified Checkout Configuration
  - Upload Your Encryption Key
    - Generate a Public Private Key Pair
    - Uploading Your Key Pair
  - Enable Digital Payments
    - Enrolling in Apple Pay
    - Enrolling in Click to Pay
    - Enrolling in Google Pay
  - Manage Permissions
    - Managing Permissions as a Direct Merchant
    - Managing Permissions as a Portfolio Administrator
- 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
- Supported Countries for Digital Payments
- Supported Locales

Processing Authorizations with a Transient Token
- Authorization with a Transient Token
  - Required Fields for an Authorization with a Transient Token
  - REST Interactive Example: Authorization with a Transient Token
  - REST Example: Authorization with a Transient Token
- Authorization and Creating TMS Tokens with a Transient Token
  - Required Fields for an Authorization and Creating TMS Tokens with a Transient Token
  - REST Interactive Example: Authorization and Creating TMS Tokens with a Transient Token
  - REST Example: Authorization and Creating TMS Tokens with a Transient Token

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

On This Page

REST API

PCI DSS Guidance

Any merchant accepting payments must comply with the PCI Data Security Standards (PCI DSS). Microform Integration’s approach facilitates PCI DSS compliance through self-assessment and the storage of sensitive PCI information.

Self Assessment Questionnaire

Microform Integration handles the card number input and transmission from within iframe elements served from Cybersource controlled domains. This approach can qualify merchants for SAQ A-based assessments. Related fields, such as card holder name or expiration date, are not considered sensitive when not accompanied by the PAN.

Storing Returned Data

Responses from Microform Integration are stripped of sensitive PCI information such as card number. Fields included in the response, such as card type and masked card number, are not subject to PCI compliance and can be safely stored within your systems. If you collect the CVN, note that it can be used for the initial authorization but not stored for subsequent authorizations.