No momento, esta página não está disponível em português
Payment-method icon

iDEAL iOS Component

Add iDEAL to your existing iOS Components integration.

iDEAL is moving to a more centralized infrastructure to process payments.

Adyen merchants currently using iDEAL have a deadline of 01 April 2025 to complete the following:

  • Remove the list of banks from their checkout pages.
  • Redirect shoppers to the central iDEAL payment page.

On this page, you can find additional configuration for adding iDEAL to your Components integration.

Before you begin

This page assumes you have already:

API reference

You don't need to send additional fields for iDEAL. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:

Component configuration

v5.0.0 or later

If your integration uses iOS Components v5.0.0 or later, configure and create an instance of the iDEAL Component:


If your integration uses an earlier version of iOS Components:

There are no configuration steps specific to iDEAL required for Components.

Recurring payments

Adyen supports recurring payments for iDEAL through SEPA Direct Debit. To make recurring payments, you need to:

  1. Create a shopper token.
  2. Use the token to make future payments for the shopper.

1. Create a token

We strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.

To create a token, include in your /payments request:

  • amount: The transaction must have a minimum value of EUR 0.01.
  • storePaymentMethod: true
  • shopperReference: your unique identifier for the shopper (minimum length three characters). Do not include personally identifiable information (PII), such as name or email address.
  • recurringProcessingModel: Subscription or UnscheduledCardOnFile

    From Checkout v70, recurringProcessingModel is a required parameter when creating or using a token.

When the payment is settled, you receive a RECURRING_CONTRACT webhook containing:

  • originalReference: The pspReference of the initial payment.
  • pspReference: This is the token that you need to make recurring payments for this shopper.

Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks. You can enable the RECURRING_CONTRACT event code in the webhook settings page.

2. Make a payment with a token

For each recurring payment for this shopper, make a SEPA payment to the /payments endpoint, specifying:

For more information about the shopperInteraction and recurringProcessingModel fields, refer to Tokenization.

If the payment was successfully received, the response contains:

  • resultCode: Received
  • pspReference: a unique identifier for this transaction.

You can track whether the payment was successful using webhooks.

BICs for iDEAL partner banks

Bank name BIC
Nationale-Nederlanden NNBANL2G
Rabobank RABONL2U
Regiobank RBRBNL21
Revolut REVOLT21
Triodos Bank TRIONL2U
Van Lanschot Kempen FVLBNL22
Yoursafe BITSNL2A

iDEAL may update its list of banking partners at any time. Be prepared to adjust your integration if these banking partners change.

Test and go live

We provide different test issuers for testing iDEAL payments, including testing for payments with Cancelled, Pending, or Refused result codes. Select the corresponding test issuer name, for example, Test Issuer Cancelled to simulate a cancelled payment scenario.

We recommend that you test each scenario before you go live.

Check the status of test payments in your Customer Area > Transactions > Payments.

Before you can accept live payments, you need to add iDEAL in your live Customer Area.

If you have an existing test account, please note that iDEAL 2.0 is currently not set up for your test merchant account. Please reach out to Support to configure your test account. LIVE accounts are not affected.

See also