3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. Zuora's Adyen integration 2.0 provides support for 3DS2 through the embedded iFrame of Payment Pages 2.0.
To comply with PSD2 using 3DS2, you must enable 3DS2 settings in Payment Pages. Then you can implement and use Payment Pages 2.0 as usual. See Payment Pages 2.0 Implementation Overview for more information.
With 3DS2 implemented and enabled, when end customers are challenged while transacting on your Payment Page, they will get held up on the challenge window before passing the validation. The callback page is displayed only when they are authenticated. A payment method ID is also generated and returned.
If your customers failed the strong customer authentication, the
[ThreeDs2_Authentication_Exception] error code and the actual error message are returned. The error code is common across all gateways, while the error message is gateway-specific.
- Several settings related to 3DS2 must be enabled for your Adyen merchant account. Contact your Adyen account manager or send emails to Adyen Support to ensure these settings are enabled for your account.
- If you want to set 3DS2 trigger conditions, refer to Adyen’s Dynamic 3D Secure documentation and make the configuration in Adyen. Zuora follows Adyen’s integration design to pass through the information.
- Zuora provides two Adyen gateway integration versions, Adyen and Adyen Integration v2.0 (the latest). Only the Adyen Integration 2.0 version support 3DS2. If you are using an earlier version of Adyen gateway integration, upgrade it to Adyen Integration 2.0. Contact Zuora Global Support to get access to the latest version.
Note that because the Adyen gateway integration does not support 3DS2 or 3DS1, any 3D Secure responses and challenges returned to the Adyen version are considered as transaction rejected.
Enable 3DS2 settings in Payment Pages
When setting up a Payment Page, select the Enable 3D Secure 2.0 checkbox and select the created gateway instance from the Default Payment Gateway dropdown list. You can complete other settings as usual.
Zuora recommends you to enable the CAPTCHA challenge feature so that you can limit the number of times end customers can attempt to submit the form after they fail the authentication. CAPTCHA challenge can be used with the 3DS2 feature to prevent potential bot attacks and reinforce the transaction security.
For more information about enabling and configuring CAPTCHA, see Security Measures for Payment Pages 2.0.
If you select a gateway integration that does not support 3DS2, an error message is displayed when saving the Payment Page.
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.