Skip to main content

Enable 3DS2 for Chase Orbital gateway integration


Enable 3DS2 for Chase Orbital gateway integration

3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. Zuora's Chase Paymentech Orbital Gateway provides support for 3DS2 through the embedded iFrame of Payment Pages 2.0. 

To comply with PSD2 using 3DS2, the following updates are required:

  1. Enable 3DS2 for your Chase merchant profile.
  2. Configure the gateway instance.
  3. Configure 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.

The integration flow is identical to the Payment Pages without 3DS2, whereas the processing flow from the perspective of end customers is different from before. If 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 created payment method ID is also 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.

Enable 3DS2 for your Chase merchant profile

Before configuring your Zuora tenant, you must enable 3D Secure 2.0 for your Chase merchant profile. Contact Chase Merchant Services to get 3DS2 enabled for your merchant profile.

Configure the gateway instance

Only the Chase Paymentech Orbital Gateway version supports 3DS2. If you are using an earlier version of Chase Orbital payment gateway integration, upgrade your gateway to this version. Contact Zuora Global Support to get access to Chase Paymentech Orbital Gateway.

When configuring the gateway instance, you must enter the value for the following fields on the gateway configuration page in addition to the required fields:

  • JPMPP Merchant ID
  • JPMPP Merchant Password

These are the credentials specific to strong customer authentication (SCA). Contact Chase Merchant Services to get this information for your merchant account.

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.

To enable CAPTCHA challenge, you should set a positive integer for both the Limit the number of submission before CAPTCHA Challenge and Limit the number of submission before blocking Submission fields when configuring the Payment Page.

Note: If you select a gateway integration that does not support 3DS2, the following error message is displayed when saving the Payment Page:

Gateway not support 3DS2 message


Currently, 0 authorization amount is not supported in 3DS2 implementation of the Chase Orbital gateway.