> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/payments/supported-payment-methods/ideal.md).

# iDEAL

iDEAL is a bank transfer payment method where the clients receive real-time transaction confirmation. It is restricted for shoppers who have been issued an online bank account that is iDEAL compatible and held at a bank based in the Netherlands. When using this payment method, a customer must provide their bank with transfer information provided by the merchant to complete the payment. The transfer details include the account holder, bank name, city, country description, payment reference, bank account number, additional bank information, and the international bank account number (IBAN).

Digital River supports iDEAL for standalone and recurring with SEPA direct debit transactions.

## How to configure

How you configure iDEAL depends on whether you're using [DigitalRiver.js with Elements](/commerce-api/payments/payments-solutions/digitalriver.js.md) or[ Drop-in payments](/commerce-api/payments/payments-solutions/drop-in.md). &#x20;

| DigitalRiver.js with Elements                                                                                       | Drop-in payments                                                                                                     |
| ------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| [Configuring iDEAL](/commerce-api/payments/payments-solutions/digitalriver.js/payment-methods/configuring-ideal.md) | [Drop-in Payments Integration Guide](/commerce-api/payments/payments-solutions/drop-in/drop-in-integration-guide.md) |

## How it works

iDEAL uses a [redirect then submit (RTS) payment flow](/commerce-api/payments/building-your-workflows/flows-by-payment-type.md#redirect-then-submit-rts-payment-flow).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/commerce-api/payments/supported-payment-methods/ideal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
