Payer Authentication Developer Guide
- Recent Revisions to This Document
- 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)
  - HTTP Status Codes

Payer Authentication Use Cases
- Use Case: Collecting Device Data
  - Required Fields for Collecting Device Data
  - Optional Fields for Collecting Device Data
  - Simple Order Example: Setting Up with Payer Authentication
- Use Case: Collecting Device Data Using Digital Payment (Google Pay)
  - Required Fields for Collecting Device Data
  - Optional Fields for Collecting Device Data
  - Simple Order Example: Collecting Device Data While Using Digital Payment (Google Pay)
- Use Case: Collecting Device Data Using a Stored Payment Credential (TMS Token)
  - Required Fields for Collecting Device Data Using a Stored Payment Credential (TMS Token)
  - Optional Fields for Collecting Device Data
  - Simple Order Example: Setting Up with Payer Authentication Using a Token
- 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: Checking Enrollment
- Use Case: Checking Enrollment in Payer Authentication While Using a Stored Payment Credential (TMS Token)
  - Required Fields for Checking Enrollment in Payer Authentication While Using a Stored Payment Credential (TMS Token)
  - Optional Fields for Checking Enrollment in Payer Authentication
- Use Case: Checking Enrollment in Payer Authentication Using Digital Payment (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 Step-Up
  - Required Fields for Validating Step-Up
  - Optional Fields for Validating Step-Up
  - REST Example: Validating the Challenge
  - Simple Order Example: Validating the Challenge
- Use Case: Validating Step Up Using Digital Payment (Google Pay)
  - Required Fields for Validating Step-Up
  - Optional Fields for Validating Step-Up
  - 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 Step-Up
  - 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

PayerAuthDetail Element

The

PayerAuthDetail

element contains information about a single transaction.

<PayerAuthDetail>
  (RequestID)
  (MerchantID)
  (RequestDate)
  (TransactionType)
  (ProofXML)?
  (VEReq)?
  (VERes)?
  (PAReq)?
  (PARes)?
  (AuthInfo)?
</PayerAuthDetail>

Child Elements of PayerAuthDetail
Element Name	Description	Type & Length
RequestID	Unique identifier generated for the transaction. This field corresponds to the requestID API field.	Numeric (26)
MerchantID	Merchant ID used for the transaction.	String (30)
RequestDate	Date on which the transaction was processed.	DateTime (25)
ProofXML	Data that includes the date and time of the enrollment check and the VEReq and VERes elements. This field corresponds to the AuthEnrollReply_proofXML API field. For a list of child elements, see <ProofXML>.	String (1024)
VEReq	Verify Enrollment Request (VEReq) is sent by the merchant’s server to the directory server. The directory server also sends it to the ACS to determine whether authentication is available for the customer’s card number. For a list of child elements, see <VEReq>.
VERes	Verify Enrollment Response (VERes) is sent by the directory server. For a list of child elements, see <VERes>.
PAReq	Payer Authentication Request message that you send to the ACS through the payment card company. Corresponds to the payerAuthEnrollReply_paReq API field. For a list of child elements, see <PAReq>.
PARes	Payer Authentication Response message sent by the ACS. For a list of child elements, see <PARes>.
AuthInfo	Address and card verification data. For a list of child elements, see AuthInfo Element.

PayerAuthDetail Element

<PayerAuthDetail>
  <RequestID>0004223530000167905139</RequestID>
  <MerchantID>example_merchant</MerchantID>
  <RequestDate>2020-02-09T08:00:09-08:00</RequestDate>
  <TransactionType>ics_pa_enroll</TransactionType>
  <ProofXML>
    ...
  </ProofXML>
  <VEReq>
    ...
  </VEReq>
  <VERes>
    ...
  </VERes>
  <PAReq>
    ...
  </PAReq>
  <PARes>
    ...
  </PARes>
</PayerAuthDetail>