Enable 3DS2 for Stripe gateway integration
The 3D Secure 2.0 feature is in Limited Availability. If you want to enable this feature for your Zuora tenant, contact Zuora Global Support.
3D Secure 2.0 (3DS2) is a widely recommended solution for strong customer authentication (SCA) under PSD2. The Stripe v2 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:
- Enable 3DS2 for your Stripe merchant account.
- Configure the gateway instance.
- 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.
Enable 3DS2 for merchant account
Before configuring your Zuora tenant, you must enable several settings related to 3DS2 for your Stripe merchant account. Contact Stripe Support to enable these required settings.
Configure the gateway instance
Only the Stripe v2 version supports 3DS2. If you are using an earlier version of Stripe gateway integration, upgrade your gateway to this version. Contact Zuora Global Support to get access to Stripe v2.
Follow Configure the Stripe payment gateway to learn how to configure Stripe v2 gateway instances.
Credit Card Reference Transactions
If you are using the Credit Card Reference Transactions (Tokenization) payment methods through the existing Stripe v1 gateway, you must upgrade to Stripe v2. Otherwise, the payments using tokenized payment methods through Stripe might fail after September, 14.
Contact Zuora Global Support to get access to Stripe v2.
Direct POST
After completing the authentication and authorization outside Zuora, you need to pass through the credit card data along with several required fields for merchant initiated transactions (MITs) to Zuora through Direct POST. See Direct POST Form Fields for Payment Pages 2.0 for a full list of fields for 3DS2.
Specific to the Stripe gateway:
- The
field_mitNetworkTransactionId
field corresponds tonetwork_transaction_id
you get from Stripe. - The
field_mitGatewayToken1
corresponds tods_transaction_id
you get from Stripe. Ifds_transaction_id
is null, you can skip including this field.