Recent Revisions to This Document
25.05.01
This revision contains only editorial changes and no technical updates.
25.04.01
- Unified Checkout
- Added a client version history and the features included in each version. See Client Version History.Added information on the available features and the fields specific to each feature to the Capture Context API. See Capture Context API
- Microform Integration
- Added more information on nested iframes in the capture context. See Capture Context.
- Click to Pay
- Added more information on nested iframes in the capture context. See Capture Context.
25.04.01
- Unified Checkout
- Added more information on nested iframes in the capture context. See Capture Context.
- Microform Integration
- Added more information on nested iframes in the capture context. See Capture Context.
- Click to Pay
- Added more information on nested iframes in the capture context. See Capture Context.
25.03.01
- Microform Integrationv2
- Added information about choosing your preferred card number prefix length and supported scenarios. See the Include Card Prefix sections of these topics:
- Capture Context (server-side set up for the capture context)
- Capture Context API (requesting the capture context using the capture context API)
- Updated the description of Transient Token Time Limit for accepting card information and for acceptingeCheckinformation. See these topics:
- Transient Token Time Limit (server-side set up for accepting card information)
- Transient Token Time Limit (server-side set up for accepting eCheck information)
- Replaced the termcheck informationwiththroughout the section Microform Integration v2.eCheckinformation
- Updated code examples for accepting card information withMicroform Integration:
- Example Code for Loading the Script Dynamically Following JWT Extraction Tags, in Client-Side Setup
- Example: Creating the Pay Button with Event Listener for Accepting Card Information, in Transient Token Time Limit
- Updated code examples for acceptingeCheckinformation withMicroform Integration:
- Example Code for Loading the Script Dynamically Following JWT Extraction Tags, in Client-Side Setup
- Example: Creating the Pay Button with Event Listener for AcceptingeCheckInformation, in Transient Token Time Limit
- Unified Checkout
- Added information about choosing your preferred card number prefix length and supported scenarios. See the Include Card Prefix sections of these topics:
- Capture Context (server-side set up for the capture context)
- Capture Context API (requesting the capture context using the capture context API)
- Replacedcheckdigital payment method withdigital payment method throughout Capture Context.eCheck
- Corrected the example code in REST Example: Requesting the Capture Context.
- Added information on using customer authentication withClick to Payfor Visa transactions. See Customer Authentication.
- Click to Pay
- Added information about choosing your preferred card number prefix length and supported scenarios. See the Include Card Prefix sections of these topics:
- Capture Context (server-side set up for the capture context)
- Capture Context API (requesting the capture context using the capture context API)
25.01.02
- Unified Checkout
- Added optional set-up parameters to control the types of credentials that Google Pay onUnified Checkoutreceives from Google. See Managing Google Pay Authentication Types.
- Added test card numbers. See Test Payment Details.
- Microform Integration
- Added test card numbers. See Test Card Numbers forMicroform Integration.
25.01.01
- Microform Integration
- Updated the JWT examples for encrypting the accept card information capture context. See Capture Context API.
- Updated the JWT examples for validating server-side capture contexts for accepting card andeCheckinformation. See these topics:
- Clarified the first step for creating the server-side capture context and updated encrypted JWT examples. See these topics:
- Updated the steps for client-side setup. See these topics:
- Updated the card detection event example. See Events.
- Removed the Node.js REST code snippet. See Getting Started Examples.
- Updated the Class: Microform examples and added the aria-label and aria-required properties. See Class: Microform.
- Unified Checkout
- Added steps for enrolling in Apple Pay. See Preparing a Device for Testing Apple Pay on Unified Checkout.Updated the Important note about China UnionPay cards that do not have CVNs. See Capture Context.
24.12.02
- Microform Integration
- Added capture context requests for accepting card andeCheckinformation. See Capture Context API.
24.12.01
- Microform Integration
- Added information about dual-branded card support. See theSupport for Dual-Branded Cardssection in Events.
- Added support for acceptingeCheckinformation. See Accept eCheck Information.
- Added information on theclientLibraryandclientLibraryIntegrityfield and values. See Client-Side Setup for Accepting Card Information and Client-Side Setup for AcceptingeCheckInformation.
- Unified Checkout
- Updated the capture context request sections to include the most recent client version and allowed payment types. See Capture Context and Capture Context API.
- Click to Pay Drop-In UI
- Updated the capture context request sections to include the most recent client version and allowed payment types. See Capture Context and Capture Context API.
24.11.01
- Microform Integration
- Added information on server-side setup and the capture context. See Server-Side Setup and Capture Context.
- Unified Checkout
- Added information about China UnionPay cards that do not have a card verification number (CVN) and expiration date. See the Important note in Capture Context.
24.09.01
- Microform Integration
- Removed information about Microform version numbering.
- Updated supported browser versions. See Microform Integration v2.
- Updated the supported event types. See Class: Field.
- Unified Checkout
- Added a note about transient token expiration. See Authorizations with a Transient Token.
- Added theUnified CheckoutJavaScript Reference. See JavaScript API Reference.
24.08.01
This revision contains only editorial changes and no technical updates.