3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. The Opayo Direct gateway integration provides support for 3DS2 through the embedded iFrame of Payment Pages 2.0. With 3DS2 enabled and implemented, end users may receive a challenge window presented by issuing banks who are seeking confirmation that the end user is the card owner. The callback page is displayed only when they are authenticated.
To comply with PSD2 by using 3DS2, the following configurations are required:
- In the Opayo console, enable 3DS2 for your Opayo merchant account.
- In Zuora, enable the 3DS2 setting in Payment Pages.
Enable 3DS2 for your merchant account
Before configuring your Zuora tenant, you must enable 3DS2 for your Opayo merchant account. Follow the instructions on Activating and adding a 3d Secure rule in Opayo’s documentation or contact support@Opayo.com.
Configure 3DS2 settings in Payment Pages
When setting up a Payment Page, select the Enable 3D Secure 2.0 checkbox and select the gateway instance from the Default Payment Gateway dropdown list.
Currently, the 3D Secure 2.0 feature for Opayo Direct can only work with the following card brands:
- American Express
Implement Payment Pages 2.0 to support 3DS2
After completing the preceding configurations, you can then implement and use Payment Pages 2.0 as usual. See Payment Pages 2.0 implementation overview for more information. Ensure that you adopt the Stored Credential Transaction framework by adding a way for customers to give consent for their payment credentials to be stored on file. Configure your Payment Pages to call the
Z.setAgreement function. See Integrate Payment Pages 2.0 for details.
If your customers failed the strong customer authentication, the
ThreeDs2_Authentication_Exception error code and error message are returned. The error code is common across all gateways, while the error message is gateway specific.
The "Best practices" section in Zuora’s implementation of 3D Secure 2.0 provides best practices for reducing the possibility of failed transactions due to 3DS2 authentication errors.