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

JCB J/Secure Test Cases for 3-D Secure 1.0

Possible Values for JCB J/Secure Response Fields
Result and Interpretation		Validate Authentication Response_
		Authentication Result	ECI	Commerce Indicator	Reason Code
Success	Successful authentication.	0	05	js	100
Success	Recorded attempt to authenticate	1	06	js_attempted	100
Failure (Customer not responsible)	System error that prevents the completion of authentication: you can proceed with authorization, but no liability shift.	6	¹	—²
	Issuer unable to perform authentication	6	07	internet	100
	Incomplete or unavailable authentication.		07	internet js_failure
	Invalid PARes.	-1	00		476
Failure (Customer responsible)	Authentication failed or cardholder did not complete authentication. If the authentication fails, Visa requires that you do not accept the card. You must ask the customer to use another payment method.	9	—	—	476
1 The ECI value can vary depending on the reason for the failure. 2 A dash (—) indicates that the field is blank or absent.

Test Case 48: JCB J/Secure Card Enrolled: Successful Authentication
Card Number	356999 00 1008 3722	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.		ics_pa_validate service was successful.
Details	ACS URL	URL	Authentication result	0
	PAReq	PAReq value	CAVV	CAVV value
	proofXML	proofXML value	E-commerce indicator	js
	VERes enrolled	Y	ECI	05
	XID	XID value	PARes status	Y
			XID	XID value
Action	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 CAVV and ECI values to your authorization request.

Test Case 49: JCB J/Secure Card Enrolled: Successful Authentication but Invalid PARes
Card Number	356999 00 1008 3748	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
	VERes enrolled	Y
Action	Do not process the authorization request. Instead ask the customer for another form of payment.

Test Case 50: JCB J/Secure Card Enrolled: Attempted Authentication
Card Number	356996 00 1008 3758
Auth. Type	Activation during shopping
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 value	Authentication result	1
	PAReq	PAReq value	CAVV	CAVV value
	proofXML	proofXML value	E-commerce indicator	js_attempted
	VERes enrolled	Y	ECI	06
	XID	XID value	PARes status	A
			XID	XID value
Action	If you request Validate Authentication and authorization services separately, follow these steps: 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 CAVV and ECI values to your authorization request. If you request the Validate Authentication and authorization services together, the process described above occurs automatically.

Test Case 51: JCB J/Secure Card Enrolled: Incomplete Authentication (Unavailable)
Card Number	354159 99 9810 3643	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. ics_pa_validate service was successful.
Details	ACS URL	URL value	Authentication result	6
	PAReq	PAReq value	E-commerce indicator	internet
	proofXML	proofXML value	ECI	07
	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 52: JCB J/Secure Card Enrolled: Failed Authentication
Card Number	356999 01 1008 3721	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. Payer cannot be authenticated.
Details	ACS URL	URL value	Authentication result	9
	PAReq	PAReq value	PARes status	N
	proofXML	proofXML value	XID	XID value
	VERes enrolled	Y	ECI	07
	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 53: JCB J/Secure Card Enrolled: Unavailable Authentication
Card Number	354159 99 9910 3865
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	100
Summary	ics_pa_enroll service was successful.
Details	E-commerce indicator	internet
	proofXML	proofXML value
	VERes enrolled	U
Action	Submit your authorization request. No liability shift.

Test Case 54: JCB J/Secure Card Enrolled: Authentication Error Processing PARes
Card Number	354159 99 9910 3881
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	ECI	07
	PAReq	PAReq value	E-commerce indicator	internet
	proofXML	proofXML value
	VERes enrolled	Y
	XID	XID value
Action	Ask the customer for another form of payment. No liability shift.

Test Case 55: JCB J/Secure Card Not Enrolled
Card Number	356997 00 1008 3724
Auth. Type	Non-participating bank
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	100
Summary	ics_pa_enroll service was successful.
Details	E-commerce indicator	js_attempted
	ECI	06
	proofXML	proofXML value
	VERes enrolled	N
Action	Submit your authorization request.

Test Case 56: JCB J/Secure Enrollment Check: Time-Out
Card Number	356998 00 1008 3723
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	100
Summary	ics_pa_enroll service was successful.
Details	E-commerce indicator	internet
Details	proofXML	proofXML value
Action	After 10-12 seconds, proceed with the authorization request. No liability shift.

Test Case 57: JCB J/Secure Enrollment Check: Lookup Error Processing Message Request
Card Number	354159 99 6910 3614
Auth. Type	Active authentication
Results	Check Enrollment		Validate Authentication
Summary	Reason Code	100
Summary	ics_pa_enroll service was successful.
Details	E-commerce indicator	internet
	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.