What can I do to make my merchant website compatible with 3D Secure v2?

It depends on your implementation:

Type of integration Impact Detail of the impact
1 Payment via form API Minor

Without any changes, your current implementation is compatible with v2 3D Secure, even if you display the payment page in an iframe.

A field has been added to the response and to the IPN: vads_threeds_auth_type.

It allows to know the type of the authentication that was made (Challenge or Frictionless).

2 Payment via iframe
3 Payment by embedded fields (JavaScript client) Minor

Without any changes, your current implementation is compatible with v2 3D Secure.

A field has been added to the response and to the IPN:

transactionDetails.cardDetails.authenticationResponse.value.authenticationType

It allows to know the type of the authentication that was made (Challenge or Frictionless).

4 CMS Minor

Our payment modules use solutions 1, 2 or 3.

Without any changes, your current implementation is compatible with v2 3D Secure.

5 REST Web Services High

The implementation of 3D Secure authentication is the responsibility of the merchant. In order to display the authentication pop-in and to process the different events (instructions or 3D Secure result), you have to have a solid understanding of JavaScript.

See the PCI payment service documentation for more information.

6 SOAP Web Services Major

Scheduled shutdown of the solution.

Migration to solutions 1 to 3 is required. Migration to solution 5 is possible but much more complex.