Enable 3DS2 for your merchant account
Learn how to enable 3DS2 for your Worldline Global Collect merchant account and configure the necessary settings in Zuora.
Before configuring your Zuora tenant, you must enable 3DS2 for your Worldline Global Collect merchant account. Contact Worldline Global Collect Support to get 3DS2 enabled.
If you are using the Worldline Global Collect Legacy gateway integration in Zuora, you can migrate to Worldline Global Collect to enable 3DS2. Contact Worldline Global Collect Support to correctly set up your merchant account so that payments can be collected via Worldline Global Collect. Later, you can configure a Worldline Global Collect gateway instance . The API Key ID and Secret API Key can be found in your Worldline Global Collect merchant console.
Enable 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")
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
The following limitations apply to the Worldline Global Collect gateway:
-
Do not enable both 3D Secure and 3D Secure 2.0 in the Payment Page.
-
As of September 5, 2019, the Worldline Global Collect gateway is not ready with
schemaTransactionIdthat is related to the grandfathering approach. Therefore, theschemaTransactionIdorinitialSchemaTransactionIdfield is not included in the payment response. This is a known issue and Worldline Global Collect is working on it.