Understanding Visa's New 3DS Data Requirements

Introduction

As part of our effort to provide our customers with a comprehensive payment orchestration service, we keep in close contact with the card schemes and other providers in order to provide our customers all the information available – and all the tools necessary, to address changes in the payment world. The following changes apply to performing 3D Secure authentication on Visa cards.

Key Changes – What You Need to Know

In a recent announcement, Visa advised merchants and providers of changes in the data that it requires for processing 3D Secure transactions. Visa now requires sending Personally Identifiable Information (PII) data in all 3D Secure authentications. According to Visa, the PII data will help issuers decide whether to challenge an authentication request, leading to lower challenge rates and higher approval rates for 3D Secure authentications.

New Requirements and Deadline

As of 12 August 2024, Visa requires the following parameters be sent in all Visa 3D Secure authentication requests:

General information about the browser and device (IP address, screen width and height).
The card holder’s name.
The card holder’s email address or phone number – at least one of them is required.

Impacts

Since the very beginning of offering 3D Secure authentications in Orchestra, we have provided our 3D Secure processor the general data now required here. This requirement therefore had no impact on us and naturally, on you.

When sending the 3D Secure authentication request, we pass all the card details that we have stored collected in the form – this includes the card holder’s name. This requirement therefore as well, had no impact on us and naturally, on you.

The requirement of providing the card holder’s email address or phone number is new to us as well and we had to amend our system to add several parameters in our requests to allow you to pass these details to us.

Technical Implementation

In order to provide the card holder’s email address or phone number, we have enhanced our 3DS library to include two additional parameters where you can provide these values.

All of our documentation pages have been updated with the relevant information.

Adherence and the Benefits

The new requirements will be strictly enforced as of 12 August 2024. If we do not provide these values to our 3D Secure provider, these authentication requests will be rejected. Therefore, we have implemented a backup process whereby, if the data is not provided in the request to our API, we will provide our own email address as part of the authentication request. We strongly recommend that you collect and send this data when performing 3DS authentication as this data will be used to validate the authentication requests and while accurate data is designed to help reduce the number of challenges and improve successful authentications, incorrect data may cause the exact opposite with a higher number of challenges and an increase in failed authentications.

Please note, at present, these changes are only applied to 3D Secure authentications of Visa cards. 3DS authentication of other card brands are unaffected.

If you have any questions or concerns, please feel free to contact our support team.

Learn More about 3D Secure

With Orchestra’s 3D Secure credit card authentication platform, you can improve fraud protection to keep your customers’ card details secure and your reputation intact. Contact us today to schedule a consultation and learn more about our 3D Secure process.

Visa’s New 3DS Data Requirements

Introduction

Key Changes – What You Need to Know

New Requirements and Deadline

Impacts

Technical Implementation

Adherence and the Benefits

Learn More about 3D Secure

Share This Post

More Like This

The Importance of Achieving High Availability in Your Payment Processing

How to Create a Frictionless Payment Experience

Considerations for International Payment Processing

Challenges of Card-Not-Present Transactions Vs. Card-Present Transactions

Seamlessly Integrate Payment With Multiple Payment Gateways

How Merchants Can Lower Credit Card Processing Fees

5 Challenges of Card-Not-Present Transaction Processing and How To Overcome Them

The Risks of Online Transactions and How E-Commerce Specific PCI Compliance Can Help

What Payment Software Developers & Providers Need to Know About PCI DSS 4.0

What We Do

Industries

Get in Touch