Skip to main content
iDEAL is a widely used online payment method in the Netherlands. Customers pay from their Dutch bank account and confirm each payment in their own banking app or online banking. Payrails processes iDEAL through five payment service providers (PSPs). The flow is the same with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How an iDEAL payment works

iDEAL is a bank redirect payment method:
  1. The customer selects iDEAL at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to their bank.
  3. The customer confirms the payment in their banking app or online banking.
  4. The bank sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures iDEAL payments immediately, so a successful payment is final. To return funds, refund the payment. Refunds work with every PSP except Worldpay.

​
Supported currencies and countries

iDEAL supports EUR (euro) as its only presentment currency.

​
Integrate iDEAL

Choose the PSP that processes iDEAL for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Adyen

iDEAL via Adyen

Checkout.com

iDEAL via Checkout.com

Nuvei

iDEAL via Nuvei

Stripe

iDEAL via Stripe

Worldpay

iDEAL via Worldpay

​
Compare PSPs

Save Instruments and merchant-initiated transactions (MIT) work only with Adyen. The first iDEAL payment through Adyen creates a SEPA Direct Debit mandate, and Payrails charges later MIT payments against that mandate.

​
Ways to integrate iDEAL

  • Payrails SDK: the Web SDK shows iDEAL when your workflow returns it as a payment option, and redirects the customer to their bank. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with iDeal as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026