Recent Revisions to This Document

About This Guide

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Apple Pay
- Requirements for Using Apple Pay
- Supported Card Types and Optional Features
- Apple Pay Integrations and Payload Decryption Methods
  - Flow of Apple Pay In-App Transactions Processed Using Cybersource Decryption
  - Flow of Apple Pay In-App Transactions Processed Using Merchant Decryption
  - Flow of Apple Pay Web Transactions Using Cybersource Decryption
  - Flow of Apple Pay Web Transactions Using Merchant Decryption

Configuring Apple Pay Processing
- Generating and Loading a New Certificate Signing Request
- Configuring Apple Pay Response Handling

Processing Apple Pay Transactions
- Authorization Service
- Authorizations Using Cybersource Decryption for JCB
  - Required Fields for Authorizing a Payment Using Cybersource Decryption for JCB
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - REST Example: Cybersource Decryption and JCB
- Authorizations Using Cybersource Decryption for mada
  - Required Fields for Authorizing a Payment Using Cybersource Decryption for mada
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - REST Example: Cybersource Decryption for mada
- Authorizations Using Cybersource Decryption for Mastercard
  - Required Fields for Authorizing a Payment Using Cybersource Decryption for Mastercard
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - Example: Cybersource Decryption and Mastercard
- Authorizations Using Cybersource Decryption for Visa
  - Required Fields for Authorizing a Payment Using Cybersource Decryption for Visa
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - REST Example: Cybersource Decryption for Visa
- Authorizations Using Merchant Decryption for JCB
  - Required Fields for Authorizing a Payment Using Merchant Decryption for JCB
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - REST Example: Merchant Decryption and JCB
- Authorizations Using Merchant Decryption for mada
  - Required Fields for Authorizing a Payment Using Merchant Decryption for mada
  - REST Example: Merchant Decryption and mada
- Authorizations Using Merchant Decryption for Mastercard
  - Required Fields for Authorizing a Payment Using Merchant Decryption for Mastercard
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - REST Example: Merchant Decryption and Mastercard
- Authorizations Using Merchant Decryption for Visa
  - Required Fields for Authorizing a Payment Using Merchant Decryption for Visa
  - Optional Fields for Authorizing a Payment for Apple Pay Transactions
  - REST Example: Merchant Decryption and Visa
- Authorization Reversals
  - Required Fields for Processing an Authorization Reversal
  - REST Example: Processing an Authorization Reversal
- Captures
  - Required Fields for Capturing an Authorization
  - REST Example: Capturing an Authorization
- Sale
  - Required Fields for Processing a Sale
  - REST Example: Processing a Sale

Searching for Apple Pay Transactions

On This Page

REST API | Visa Platform Connect

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.