home

Zuora Payments

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora Payments

Enable 3DS2 for Stripe gateway integration

Enable 3DS2 for merchant account

Learn how to enable 3DS2 settings for your Stripe merchant account and configure the necessary gateway instances in Zuora.

Before configuring your Zuora tenant, you must enable settings related to 3DS2 for your Stripe merchant account. ContactStripe Support and provide the following information to enable the required settings:

  • Your Stripe account ID

  • A statement that you are using the Zuora v2 adapter

  • A request for enabling a feature to recognize the mit_exemption parameter to avoid the following error when processing payments: 400 [invalid_request_error/parameter_unknown] Received unknown parameter: payment_method_options[card][mit_exemption]

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.

Follow Configure the Stripe payment gateway to learn how to configure Stripe v2 gateway instances.

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.

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 .

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 to network_transaction_id you get from Stripe.

  • The field_mitGatewayToken1 corresponds to ds_transaction_id you get from Stripe. If ds_transaction_id is null, you can skip including this field.

Last updated: May 29, 2026