Skip to main content

Enable 3DS2 for gateway integration


Enable 3DS2 for gateway integration

3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. The gateway integration in Zuora provides support for 3DS2 using hosted solution through Zuora's 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.

Configure 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.

Configure the gateway instance

When configuring a gateway instance, you can select the indicator of requesting a cardholder challenge that will be passed to the gateway. In the 3DS Challenge Indicator field on the gateway settings page, select one of the indicator options to indicate your preference for whether or not a 3DS challenge should be performed. Ultimately, it is the issuing bank that determines whether a card needs to be authenticated through a challenge.

See Payment Gateway for more information.

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.


Currently, the 3D Secure 2.0 feature for can work with only the following credit card brands:

  • Visa
  • Mastercard
  • American Express