Digital Accept Secure Integration Developer Guide
Digital Accept
Secure Integration Developer GuideThis section describes how to use this guide and where to find further information.
- Audience and Purpose
- This document is written for merchants who want to enableUnified Checkout Integrationon their e-commerce page.
- Conventions
- This special statement is used in this document:IMPORTANTAnImportantstatement contains information essential to successfully completing a task or learning a concept.
Recent Revisions to This Document
24.09
- Microform Integration
- Added information on server-side setup and the capture context. See Server-Side Setup and Capture Context.
- Unified Checkout Integration
- 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.08
- 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 Integration
- Added a note about transient token expiration. See Authorizations with a Transient Token.
- Added theUnified Checkout IntegrationJavaScript Reference. See JavaScript Reference.
24.07
This revision contains only editorial changes and no technical updates.
24.06
This revision contains only editorial changes and no technical updates.
24.05
- Unified Checkout Integration
- Added support for Apple Pay inUnified Checkout Integration. See Enrolling in Apple Pay and Apple Pay UI.
24.04
This revision contains only editorial changes and no
technical updates.
24.03
- This revision contains only editorial changes and no technical updates.
24.02
This revision contains only editorial changes and no technical updates.
24.01
- Checkout API
- Removed the Checkout API, as this method is deprecated.
- Unified Checkout Integration
- Added aUnified Checkout Integrationcard entry form diagram. See Unified Checkout Integration Flow.
- Updated the capture context description and request example. See Capture Context API and REST Example: Requesting the Capture Context.
VISA Platform Connect: Specifications and Conditions for Resellers/Partners
The following are specifications and conditions that apply to a Reseller/Partner
enabling its merchants through
Cybersource for Visa Platform Connect
(“VPC”) processing
. Failure to meet any of the specifications and
conditions below is subject to the liability provisions and indemnification
obligations under Reseller/Partner’s contract with Visa/Cybersource.- Before boarding merchants for payment processing on a VPC acquirer’s connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer.
- Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer.
- Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer.
- Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer.
DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS
OR OMISSIONS BY THE VISA PLATFORM CONNECT ACQUIRER IN PROCESSING TRANSACTIONS.
NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER
BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND
CONDITIONS IMPOSED BY THE RELEVANT VISA PLATFORM CONNECT ACQUIRER.