Visa 3DS fields

Overview

The Visa 3DS Additional Fields Mandate requires merchants to send a richer set of customer, device, and transaction data in EMV 3-D Secure authentication requests. Visa is aiming to improve issuer risk assessment, increase frictionless authentication approvals, reduce unnecessary challenges, and strengthen fraud detection.

To support the Visa 3DS mandate, two additional parameters will be collected and passed to 3DS:  Cardholder Name and Cardholder Email Address.

This information has to be collected from the cardholder. All other mandatory fields from the Visa 3DS mandate will be collected and sent in the background by Netaxept.

More information on the Visa 3DS may be found here: Knowledge Article Detail Page - CYBS | Visa Acceptance Support Center.

Transactions will be processed, even without the additional 3DS data, but there might be an impact on the 3DS fees for the transaction. Please refer to your acquirer on the details of this.

Zero Disruption Guarantee 

Configuration

Payment Window Version 1 & Version 2

You can manage these fields in your Admin Panel -> Options -> Terminal -> General -> 3DS Settings.

Enable 3DS Fields in Terminal: Displays both fields on the payment window (visible, but not required).

Set 3DS Fields in Terminal as mandatory: Makes both fields required to complete the payment (this can only be selected if the option above is enabled).

Passing Data via the Register Call 

If you already collect this information during your checkout process, you can pass it directly via the Register call.
In this scenario, you do not need to enable the terminal fields in the Admin Panel.

The following data routing rules apply:

• If terminal fields are ON: The values passed in the Register call (customerFirstName + customerLastName, and customerEmail) will pre-populate the payment window fields.
• If terminal fields are OFF: The values will be forwarded directly to 3DS.

• For SDKs and non-UI cases: The values have to be passed in the Register call and will be forwarded directly to 3DS.

Payment Window Version 1.1 (Custom CSS) 

If you are using Version 1 with custom CSS, you must pass these parameters manually in your request.
For example:

• {netaxept:cardholdername /}
• {netaxept:cardholderemail /}