Recent Revisions to This Document

About This Guide

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

Introduction to Payer Authentication
- Why Payer Authentication Is Needed
- EMV 3-D Secure 2.0
- Payer Authentication Customer Workflow
- Payer Authentication Merchant Workflow
- Acquirer Information
- Enable Merchant Account for EMV 3-D Secure
- Payer Authentication Configuration Testing
- Request Endpoints
- Payer Authentication Integrations

Implementing Direct API for Payer Authentication
- Prerequisites
- After Implementation and Before Go Live

Step 1: Setup Service
- Request Fields
- Important Response Fields

Step 2: Device Data Collection
- Which Device Data is Collected
- Building the Iframe
- Initiating the Device Data Collection Iframe
- Submitting the Device Data Collection Iframe
- Receiving the Device Data Collection URL Response

Step 3: Payer Authentication Check Enrollment Service
- Request Fields
- Interpreting the Check Enrollment Response
- Important Response Fields

Step 4: Step-Up Iframe
- Building the Iframe Parameters
- Creating the Iframe
- Invoking the Iframe
- Receiving the Step-Up Results

Step 5: Payer Authentication Validation Service
- Request Fields
- Interpreting the Validation Response
- Redirecting Customers to Pass or Fail Message Page

Combining the Authentication and the Authorization Services
- Combining Check Enrollment and the Authorization Services
  - Check Enrollment Response Fields and Their Equivalent Authorization Request Fields
- Combining the Validation and the Authorization Services
  - Validation Fields and their Equivalent Authorization Fields

Testing Payer Authentication
- Testing Process
  - Enrollment Check Response Fields
  - Authentication Validation Response Fields
- Test Cases for 3-D Secure 2.x
  - Test Case 2.1: Successful Frictionless Authentication
  - Test Case 2.2: Unsuccessful Frictionless Authentication
  - Test Case 2.3: Attempts Processing Frictionless Authentication
  - Test Case 2.4: Unavailable Frictionless Authentication
  - Test Case 2.5: Rejected Frictionless Authentication
  - Test Case 2.6: Authentication not Available on Lookup
  - Test Case 2.7: Enrollment Check Error
  - Test Case 2.8: Time-Out
  - Test Case 2.9: Bypassed Authentication
  - Test Case 2.10a: Successful Step-Up Authentication
  - Test Case 2.11a: Unsuccessful Step-Up Authentication
  - Test Case 2.12a: Unavailable Step-Up Authentication
  - Test Case 2.14: Require Method URL
- Payer Authentication Exemption Test Cases
  - Test Case 1a: Initial/First Recurring Transaction: Fixed Amount
  - Test Case 2a: Card Authentication Failed
  - Test Case 2b: Suspected Fraud
  - Test Case 2c: Cardholder Not Enrolled in Service
  - Test Case 2d: Transaction Timed Out at the ACS
  - Test Case 2e: Non-Payment Transaction Not Supported
  - Test Case 2f: 3RI Transaction Not Supported
  - Test Case 3a: Transaction Risk Analysis Exemption: Low Value: Mastercard EMV 3-D Secure 2.1 and 2.2
  - Test Case 3b: Transaction Risk Analysis: Low Value: Visa
  - Test Case 3c: Transaction Risk Analysis: Low Value: Discover
  - Test Case 3d: Acquirer Transaction Risk Analysis: Cartes Bancaires
  - Test Case 4a: Trusted Beneficiary Prompt for Trustlist
  - Test Case 4b: Utilize Trusted Beneficiary Exemption
  - Test Case 5a-1: Identity Check Insights (ScoreRequest = N)
  - Test Case 5a-2: Identity Check Insights (ScoreRequest = Y)

Payer Authentication Use Cases
- Use Case: Setting Up Payer Authentication
  - Required Fields for Setting Up Payer Authentication
  - Optional Fields for Setting Up Payer Authentication
  - Simple Order Example: Setting Up with Payer Authentication
- Use Case: Setting Up Payer Authentication with Google Pay
  - Required Fields for Setting Up Payer Authentication
  - Optional Fields for Setting Up Payer Authentication
  - Simple Order Example: Setting Up Payer Authentication Using Google Pay
- Use Case: Checking Enrollment in Payer Authentication
  - Required Fields for Checking Enrollment in Payer Authentication
  - Optional Fields for Checking Enrollment in Payer Authentication
  - Simple Order Example: Check Enrollment
- Use Case: Checking Enrollment in Payer Authentication Using Google Pay
  - Required Fields for Checking Enrollment in Payer Authentication
  - Optional Fields for Checking Enrollment in Payer Authentication
  - Simple Order Example: Checking Enrollment in Payer Authentication Using Google Pay
- Use Case: Validating Payer Authentication
  - Required Fields for Validating Payer Authentication
  - Optional Fields for Validating Payer Authentication
  - REST Example: Validating the Challenge
  - Simple Order Example: Validating the Challenge
- Use Case: Validating Payer Authentication Using Google Pay
  - Required Fields for Validating Payer Authentication
  - Optional Fields for Validating Payer Authentication
  - Simple Order Example: Validating the Challenge When Using Google Pay
- Use Case: Validating and Authorizing a Transaction
  - Required Fields for Processing an Authorization Using Visa Secure
  - Optional Fields for Validating Payer Authentication
  - Simple Order Example: Processing an Authorization Using Visa Secure

Website Modification Reference
- Website Modification Checklist
- EMV 3-D Secure Services Logos
- Informational Message Examples

Alternate Methods for Device Data Collection
- Device Data Collection Overview
  - Prerequisites
  - Endpoints
- Collecting Device Data
  - Card BIN in JWT
  - Card BIN as a POST Parameter Plus JWT

Upgrading Your Payer Authentication Implementation
- Benefits
- PSD2 Impact
  - Mandates
- Recommended Integration
- Migrating from EMV 3-D Secure 1.x to 2.x FAQ

Payer Authentication Transaction Details in the Business Center
- Payer Authentication Search
- Storing Payer Authentication Data
- Searching for Payer Authentication Details
  - Enrolled Card
    - Enrollment Check
    - Authentication Validation
  - Card Not Enrolled
    - Transaction Details

Payer Authentication Reports
- Payer Authentication Summary Report
  - Downloading the Report
  - Matching the Report to the Transaction Search Results
  - Interpreting the Report
  - Comparing Payer Authentication and Payment Reports
- Payer Authentication Detail Report
  - Report Element
  - PayerAuthDetail Element
  - ProofXML Element
  - VEReq Element
  - VERes Element
  - PAReq Element
  - PARes Element
  - AuthInfo Element
  - Report Examples

Reason Codes

Glossary

On This Page

Simple Order API

Maestro Test Cases for 3-D Secure 1.0

Possible Values for Maestro Response Fields
Result and Interpretation		Validate Authentication Response
		Authentication Result	ECI	Commerce Indicator	Reason Code
Success	Successful authentication.	0	2	spa	100
	Recorded attempt to authenticate.	1	1	spa	100
	Authentication not completed.	1	0	spa	100
Failure (Customer not responsible)	System error (Issuer unable to perform authentication): you cannot authorize this card; no liability shift.	6	0	internet	100
Failure (Customer not responsible)	Invalid PARes.	-1	0		476
Failure (Customer responsible)	Authentication failed or cardholder did not complete authentication.	9	0	–	476

Test Case 30: Maestro Card Enrolled: Successful Authentication
Card Number	675941 11 0000 0008 675941 00 0000 6404	Without authentication window With authentication window
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	475	Reason Code	100
Summary	The cardholder is enrolled in payer authentication. Please authenticate before proceeding with authorization.		ics_pa_validate service was successful.
Details	ACS URL	URL	Authentication result	0
	PAReq	PAReq value	AAV	AAV value
	proofXML	proofXML value	Collection indicator	2
	VERes enrolled	Y	E-commerce indicator	spa
	XID	XID value	PARes status	Y
			XID	XID value
Action	Add the signed PARes to the validation request. In the response, ensure that the XID from the enrollment check matches that from the validation. Add the required payer authentication values to your authorization request.

Test Case 31: Maestro Card Enrolled: Successful Authentication but Invalid PARes
Card Number	633110 12 3456 7892	Without authentication window
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	475	Reason Code	476
Summary	The cardholder is enrolled in payer authentication. Please authenticate before proceeding with authorization.		Payer authentication problem: PARes signature digest value mismatch. PARes message has been modified.
Details	ACS URL	URL	Authentication result	-1
	PAReq	PAReq value	XID	XID value
	proofXML	proofXML value
	VERes enrolled	Y
	XID	XID value
Action	Do not process the authorization request. Instead ask the customer for another form of payment.

Test Case 32: Maestro Card Enrolled: Attempts Processing - *Deprecated This test case is no longer used.*
Card Number	560000 00 0000 00 0193	Card enrollment option during purchase process
Auth. Type	Maestro stand in attempts service
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	475	Reason Code	100
Summary	The cardholder is enrolled in payer authentication. Please authenticate before proceeding with authorization.		ics_pa_validate service was successful.
Details	ACS URL	URL	Authentication result	1
	PAReq	PAReq value	AAV	AAV value
	proofXML	proofXML value	E-commerce indicator	spa
	VERes enrolled	Y	PARes status	A
	XID	XID value	XID	XID value
Action	This test card enables you to reproduce the process by which the customer enrolls the card during the purchase. If the card is not enrolled, a card enrollment option windows appears in the customer’s browser after the enrollment check. The customer can activate the card at that time or later. In both cases, the card is authenticated, and validation is successful. Add the signed PARes to the Validate Authentication request. Ensure that the XID from the enrollment check matches that from the authentication validation. Add the required payer authentication values to your authorization request.

Test Case 33: Maestro Card Enrolled: Incomplete Authentication
Card Number	633110 12 5035 3227	Without authentication window
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	475	Reason Code	100
Summary	The cardholder is enrolled in payer authentication. Please authenticate before proceeding with authorization.		Issuer unable to perform authentication.
Details	ACS URL	URL value	Authentication result	6
	PAReq	PAReq value	Collection indicator	0
	proofXML	proofXML value	E-commerce indicator	spa
	VERes enrolled	Y	PARes status	U
	XID	XID value	XID	XID value
Action	Ask the customer for another form of payment, or submit the transaction. No liability shift.

Test Case 34: Maestro Card Enrolled: Unsuccessful Authentication
Card Number	633110 06 1019 4313	Without authentication window
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	475	Reason Code	476
Summary	The cardholder is enrolled in payer authentication. Please authenticate before proceeding with authorization.		User failed authentication
Details	ACS URL	URL value	Authentication result	9
	PAReq	PAReq value	PARes status	N
	proofXML	proofXML value	XID	XID value
	VERes enrolled	Y	Collection Indicator	0
	XID	XID value
Action	You are not permitted to submit this transaction for authorization. Instead ask the customer for another form of payment.

Test Case 35: Maestro Card Enrolled: Unavailable Authentication
Card Number	633110 02 6697 7839
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	100
Summary	ics_pa_enroll service was successful.
Details	Collection indicator	0
	E-commerce indicator	spa
	proofXML	proofXML value
Action	Submit the transaction. No liability shift.

Test Case 36: Maestro Card Enrolled: Authentication Error
Card Number	560000 51 1607 57 7094	Without authentication window
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	475	Reason Code	476
Summary	The cardholder is enrolled in payer authentication. Please authenticate before proceeding with authorization.		We encountered a payer authentication problem: Error Processing PARes.
Details	ACS URL	URL value	Collection indicator	0
	PAReq	PAReq value	E-commerce indicator	internet
	proofXML	proofXML value
	VERes enrolled	Y
	XID	XID value
Action	Do not request authorization. Instead ask the customer for another form of payment. No liability shift.

Test Case 37: Maestro Enrollment Check Error
Card Number	560000 84 1211 09 2515
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	100
Summary	ics_pa_enroll service was successful.
Details	Collection indicator	0
	E-commerce indicator	internet
	proofXML	proofXML value
	VERes enrolled	U
Action	Proceed with the authorization request, and contact your support representative to resolve the issue. No liability shift. If you requested payer authentication and authorization together, the authorization is processed automatically.