Payer Authentication

This section describes and the audience and purpose of this developer guide as well as conventions and related documentation.
Audience and Purpose
This guide is written for application developers who want to use the
REST
 API to integrate payer authentication services into their system. It describes the tasks you must perform in order to complete this integration.
Implementing payer authentication services requires software development skills. You must write code that uses the API request and response fields to integrate payer authentication services into your existing order management system.
Scope
This guide describes how to use the
REST
 API to integrate payer authentication services with your order management system. It does not describe how to get started using the
REST
 API nor does it explain how to use services other than payer authentication. For that information, see the
Related Documents
 section.
Conventions
These special statements are used in this document:
IMPORTANT
An
Important
 statement contains information essential to successfully completing a task or learning a concept.
WARNING
A
Warning
 contains information or instructions, which, if not followed, can result in a security risk, irreversible loss of data, or significant cost in time or revenue.
Related Documentation
Visit the Technical Documentation Hub on the
Cybersource
 Developer Center for links to further documentation resources.
Customer Support
For support information about any service, visit the Support Center:

Recent Revisions to This Document

24.04

Test cases for Mada are supported.
Updated the test cases for 3-D Secure 2.x section to include test results for the Mada card. For more information, see test cases for 3-D Secure 2.x section.
Highlighted API fields specific to Meeza card usage
Added API fields to the country specific section for the setup and check enrollment use cases that are required when using the Meeza card. For more information, see Use Case: Setting Up Payer Authentication and Use Case: Checking Enrollment in Payer Authentication.

24.03

Updated the test cases for 3-D Secure 2.x section to mention that the Meeza card is supported for payer authentication as card type 067, and should be tested using Mastercard numbers.

24.02

Added a short description of the other products in the risk management portfolio that work with payer authentication.

24.01

Updated the date that a Visa Secure 3-D Secure mandate that changes some conditionally optional fields to required fields occurs. The effective date was pushed back by six months to August 12, 2024.

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.
  1. 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.
  2. 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.
  3. 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.
  4. 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.