Enable 3DS2 for Checkout.com gateway integration
Learn how to enable 3D Secure 2.0 (3DS2) for Checkout.com gateway integration in Zuora to comply with PSD2 requirements using Payment Pages 2.0.
3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. The checkout.com gateway integration in Zuora provides support for 3DS2 using Checkout.com 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.
wiki.page("z_Source/Configure_3DS2_settings_in_Payment_Pages", "Callback")
Configure 3DS2 settings in Payment Pages
wiki.page("z_Source/Configure_3DS2_settings_in_Payment_Pages", "Configure 3DS2 settings in Payment Pages")
wiki.page("z_Source/Configure_3DS2_settings_in_Payment_Pages", "Enable CAPTCHA")
wiki.page("z_Source/Configure_3DS2_settings_in_Payment_Pages", "Gateway does not support 3DS2")
Configure the gateway instance
When configuring a checkout.com 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 Checkout.com 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.
Limitations
Currently, the 3D Secure 2.0 feature for checkout.com can work with only the following credit card brands:
-
Visa
-
Mastercard
-
American Express