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

Implement iDEAL on Stripe v2

iDEAL on Stripe v2 overview

Learn about integrating iDEAL with Stripe v2 for seamless online bank transfer payments in the Netherlands, including setup and supported features.

iDEAL is the leading online bank transfer payment method in the Netherlands. iDEAL works with all the major Dutch banks. Zuora's Stripe v2 gateway integration supports iDEAL. You can implement a hosted payment page through Payment Pages 2.0 to support iDEAL one-time and recurring payment flows. The created iDEAL payment methods are automatically tokenized. The creation of iDEAL payment methods through Zuora UI or API operations is not supported.

When end customers pay with iDEAL, a list of banks is presented and end customers are redirected to the selected bank's website or application, where end customers confirm the payment with a second factor of authentication. The payment is processed instantly and the end customer is notified of the outcome.

The created iDEAL payment method can be retrieved through the Zuora UI and API operations if you choose to store it in Zuora. You can also retrieve the following token information in the Electronic Payment Methods section of the customer account page. Token ID and Second Token ID will be used in subsequent recurring payments.

Zuora UI field

Value

Token ID

The Stripe Customer Id, such as cus_xxxxxx

Second Token ID

The Stripe Payment Method Id, such as pm_xxxxxx

Third Token ID

The mandate ID

The Reference ID of the payment is populated with the Stripe charge ID, such as py_xxxxxxx .

Recurring payments are processed with the stored Token ID and Second Token ID described in the preceding table through SEPA Direct Debit. To support processing recurring payments, the following requirements must be met:

  • Real-Time Reconciliation for Stripe v2 must be enabled.

  • In your implementation of the one-time payment flow, select to store the payment method when processing the one-time payment.

For implementation instructions, see later sections.

The following table lists the supported and unsupported operations and features for iDEAL on Stripe v2:

Supported

Unsupported

  • Creation of iDEAL payment methods through hosted payment pages

  • One-time payment processing

  • Recurring payment processing

  • Referenced refund through SEPA Direct Debit

  • Real-Time Reconciliation

  • Support idempotency for retrying payment and refund transactions

  • Creation of iDEAL payment method through UI or API operation

  • Standalone payment method validation

  • Payment cancel (void)

  • Non-referenced refund

  • Delayed Capture

  • Stored Credential Transactions framework and the sharing NTI feature

  • Batch Gateway Reconciliation

Overall, complete the following steps to implement iDEAL on Stripe v2:

  1. Prepare for the integration .
  2. Set up a Payment Page 2.0 .
  3. Request a signature from Zuora for the payment page .
  4. Set up your client code to integrate the payment page to your web page .
  5. Implement the callback response .

You can find detailed instructions in the following sections.

Last updated: December 3, 2025