Starting August 12th, Visa has updated its 3DS payer authentication requirements. The following additional data fields must now be included in Payer Authentication Enrollment Requests for both browser and in-app transactions.
Mandatory Data Fields
|
Priority Data Fields |
Requirement Status |
|
Browser IP Address |
Mandatory (Browser) |
|
Cardholder Name |
Mandatory (Browser / In-App) |
|
Cardholder Email Address |
Mandatory (Browser / In-App) |
|
Cardholder Phone Number (Work / Home / Mobile) |
Mandatory (Browser / In-App) |
|
Common Device Identification Parameters (Device IP Address) |
Mandatory (In-App) |
For more information, refer to the official Visa source here. In practice, this means Cardholder name, email or phone and browser IP/device data are required.
Piano has collaborated with various payment providers to ensure our system meets the new requirements. Below are the instructions for each provider on how to enable the required parameters.
Braintree
-
Automatic Fields: Browser IP, email address, and phone number (based on primary user authentication) are automatically collected and passed in payer authentication requests. No action is required on your part as Piano has implemented these fields.
-
Cardholder Name Collection: To collect and pass the Cardholder Name, follow these steps:
-
Update your system templates.
-
Enable the Cardholder Name in the configuration settings.
-
System Template Updates | Configuration Setup
Datatrans
-
Automatic Fields: Browser IP, email address, and phone number are automatically collected and passed in payer authentication requests. No additional actions are needed for these fields.
-
Cardholder Name Collection: To enable Cardholder Name collection:
-
Update your system templates.
-
Enable the Cardholder Name in the configuration settings.
-
System Template Updates | Configuration Setup
Stripe (Card Integration)
-
Automatic Fields: Browser IP, email address are automatically passed in payer authentication requests without any additional configuration.
-
Cardholder Name Collection: To enable Cardholder Name collection:
-
Update your system templates.
-
Enable the Cardholder Name in the configuration settings.
-
System Template Updates | Configuration Setup
Stripe Elements (Cards)
-
Automatic Fields: Browser IP, email address are automatically passed in payer authentication requests without any additional configuration. For further reference visit this article.
-
Cardholder Name Collection: For Stripe Elements, there is no dedicated Cardholder Name field in the payment element. Stripe recommends using the First and Last name fields for 3DS payer authentication. To pass the First and Last name:
-
Enable the Address Element with Billing Address collection – This will automatically collect First and Last names during checkout and pass them to Stripe.
For more details, refer to the Address Element documentation.
-
Cybersource
-
Automatic Fields: Browser IP, email address are automatically passed in payer authentication requests without any additional configuration.
-
Cardholder Name Collection: To enable Cardholder Name collection:
-
Update your system templates.
-
Enable the Cardholder Name in the configuration settings.
-
System Template Updates | Configuration Setup
GMO
-
Automatic Fields: Browser IP, email address are automatically passed in payer authentication requests without any additional configuration.
-
Cardholder Name Collection: To enable Cardholder Name collection:
-
Update your system templates.
-
System Template Updates | Configuration Setup