Skip to main content

Enable 3DS2 for Worldpay 1.4

Zuora

Enable 3DS2 for Worldpay 1.4

  1. Last updated
  2. Save as PDF

3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. The Worldpay 1.4 gateway integration 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 3DS Flex for your Worldpay merchant account.
  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.

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.

Enable 3DS Flex for merchant account

Worldpay provides support for 3DS2 through the 3DS Flex feature. Before configuring your Zuora tenant, you must enable 3DS Flex for your Worldpay merchant account. Contact Worldpay Merchant Support to get access to this feature.

Configure the gateway instance

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

  • 3D Secure 2.0 Organisational Unit Id
  • 3D Secure 2.0 Issuer
  • 3D Secure 2.0 JWT MAC Key

The values for these fields should be provided by Worldpay. Contact Worldpay Merchant Support 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.

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.