iDEAL payments with Sources
Use Sources to accept payments using iDEAL, the most popular payment method in the Netherlands.
Warning
We deprecated the Sources API and plan to remove support for local payment methods. If you currently integrate with iDEAL using the Sources API, you must migrate to the Payment Methods API.
For information about integrating iDEAL with the current APIs, see iDEAL payments.
Stripe users in Europe and the United States can accept iDEAL payments from customers in the Netherlands using Sources—a single integration path for creating payments using any supported method.
During the payment process, a Source object is created and your customer is redirected to their bank’s website or mobile application to authorize the payment. After completing this, your integration uses the source to make a charge request and complete the payment.
iDEAL is a push-based, single-use and synchronous method of payment. This means your customer takes action to send the amount to you through a redirect and there is immediate confirmation about the success or failure of a payment.
Create a Source object
To create a Source
object client-side, follow the iDEAL Bank Element Quickstart. The iDEAL Bank Element lets your customers select their bank inline (rather than in an interstitial bank selection page) and check out faster. Once you’ve created a source object, you can proceed to customer authorization in the next step.
Custom client-side source creation
If you choose to collect your customer’s bank yourself or not collect it at all, create your own form and call stripe.
as described in the Stripe.js reference. When doing so, make sure to collect the following information from your customer:
Parameter | Value |
---|---|
type | ideal |
amount | A positive integer in the smallest currency unit representing the amount to charge the customer (for example, 1099 for a 10.99 EUR payment). |
currency | eur (iDEAL must always use Euros) |
ideal[bank] (optional) | The customer’s bank. |
redirect[return_ | The URL the customer should be redirected to after the authorization process. |
statement_ (optional) | A custom statement descriptor for the payment. |
Server-side source creation
A Source
object can also be created server-side using the Source creation endpoint with the above parameters.
Using either method, Stripe returns a Source
object containing the relevant details for the method of payment used. Information specific to iDEAL is provided within the ideal
subhash.
{ "id": "src_16xhynE8WzK49JbAs9M21jaR", "object": "source", "amount": 1099, "client_secret": "src_client_secret_UfwvW2WHpZ0s3QEn9g5x7waU", "created": 1445277809, "currency": "eur", "flow": "redirect", "livemode": true, "owner": {
Source creation in mobile applications
If you’re building an iOS or Android app, you can implement sources using our mobile SDKs. Refer to our sources documentation for iOS or Android to learn more.
Optional: Providing a custom statement descriptor
iDEAL requires a statement descriptor before the customer is redirected to authenticate the payment. By default, your Stripe account’s statement descriptor is used (you can review this in the Dashboard). You can provide a custom descriptor by specifying statement_
when creating a source.
stripe.createSource({ type: 'ideal', amount: 1099, currency: 'eur', statement_descriptor: 'ORDER AT11990', owner: { name: 'Jenny Rosen', }, redirect: { return_url: '__TOKEN_PLACEHOLDER_0__', }, }).then(function(result) { // handle result.error or result.source });
Providing a custom statement descriptor within a subsequent charge request has no effect.
Optional: Specifying the customer’s bank
When your customer is redirected, they are first presented with a page to select which bank they use and complete authentication. If you already know which bank your customer uses for iDEAL payments, or request this during the checkout process, you can optionally provide the ideal[bank]
parameter when creating a source and one of the following values. This allows your customer to be immediately redirected to their bank. The supported values for ideal[bank]
are:
Bank name | Value |
---|---|
ABN AMRO | abn_ |
ASN Bank | asn_ |
Bunq | bunq |
ING | ing |
Knab | knab |
N26 | n26 |
Nationale-Nederlanden | nn |
Rabobank | rabobank |
Revolut | revolut |
RegioBank | regiobank |
SNS Bank (De Volksbank) | sns_ |
Triodos Bank | triodos_ |
Van Lanschot | van_ |
Yoursafe | yoursafe |
Error codes
Source creation for iDEAL payments may return any of the following errors:
Error | Description |
---|---|
payment_ | The payment method is currently not available. You should invite your customer to fallback to another payment method to proceed. |
processing_ | An unexpected error occurred preventing us from creating the source. The source creation should be retried. |
invalid_ | The iDEAL bank parameter is invalid. It must be one of the values provided above. |
Have the customer authorize the payment
When creating a source, its status is initially set to pending
and cannot yet be used to make a charge request. Your customer must authorize an iDEAL payment to make the source chargeable. To allow your customer to authorize the payment, redirect them to the URL provided within theredirect[url]
attribute of the Source
object.
After the authorization process, your customer is redirected back to the URL provided as a value of redirect[return_
. This happens regardless of whether authorization was successful or not. If the customer has authorized the payment, the Source
object’s status will transition to chargeable
when it is ready to be used in a charge request. If your customer declines the payment, the status will transition to failed
.
Stripe populates the redirect[return_
with the following GET parameters when returning your customer to your website:
source
: a string representing the original ID of theSource
objectlivemode
: indicates if this is a live payment, eithertrue
orfalse
client_
: used to confirm that the returning customer is the same one who triggered the creation of the source (source IDs are not considered secret)secret
You may include any other GET parameters you may need when specifying redirect[return_
. Do not use the above as parameter names yourself as these would be overridden with the values we populate.
Mobile applications
To integrate iDEAL within a mobile application, provide your application URI scheme as the redirect[return_
value. By doing so, your customers are returned to your app after completing authorization. Refer to our Sources documentation for iOS or Android to learn more.
If you are integrating without using our mobile SDKs, the redirect URL must be opened using the device’s native browser. The use of in-app web views and containers is prohibited by iDEAL and can prevent your customer from completing authentication—resulting in a lower conversion rate.
Testing the redirect process
When creating a Source
object using your test API keys, you can follow the URL returned in the redirect[url]
field. This leads to a Stripe page that displays information about the API request, and where you can either authorize or cancel the payment. Authorizing the payment redirects you to the URL specified in redirect[return_
.
Alternatively, to accelerate testing, use the following value for owner[email]
, where xxx_
is any prefix of your choice (these patterns are significant only in testmode):
Email Address | Effect |
---|---|
xxx_ | The source will be created as pending , but automatically transition to chargeable within seconds of its creation. |
Charge the Source
Once the customer has authenticated the payment, the source’s status
transitions to chargeable
and it can be used to make a charge request. This transition happens asynchronously and may occur after the customer was redirected back to your website.
Some customers using iDEAL assume that the order process is complete once they have authenticated the payment and received confirmation from their bank. This results in customers who close their browser instead of following the redirect and returning to your app or website.
For these reasons it is essential that your integration rely on webhooks to determine when the source becomes chargeable in order to create a charge. Please refer to our best practices for more details on how to best integrate payment methods using webhooks.
Webhooks
The following webhook events are sent to notify you about changes to the source’s status:
Event | Description |
---|---|
source. | A Source object becomes chargeable after a customer has authenticated and verified a payment. |
source. | A Source object failed to become chargeable as your customer declined to authenticate the payment. |
source. | A Source object expired and cannot be used to create a charge. |
Make a charge request using the source
Once the source is chargeable, from your source.
webhook handler, you can make a charge request using the source ID as the value for the source
parameter to complete the payment.
iDEAL Sources are single-use and cannot be used for recurring or additional payments.
Refer to our Sources & Customers guide for more information on how single-use Sources interact with Customers.
Confirm that the charge has succeeded
Since iDEAL is a synchronous payment method and the customer has already authenticated the payment as part of the redirect, unless there is an unexpected error, the Charge will immediately succeed.
You will also receive the following webhook event as the charge is created:
Event | Description |
---|---|
charge. | The charge succeeded and the payment is complete. |
We recommend that you rely on the charge.
webhook event to notify your customer that the payment process has been completed and their order is confirmed. Please refer to our best practices for more details on how to best integrate payment methods using webhooks.
Disputed payments
The risk of fraud or unrecognized payments is extremely low with iDEAL as the customer must authenticate the payment with their bank. As such, there is no dispute process that can result in a chargeback and funds withdrawn from your Stripe account.
Refunds
Payments made with iDEAL can only be submitted for refund within 180 days from the date of the original charge. After 180 days, it is no longer possible to refund the charge.
Sources expiration
A source must be used within six hours of becoming chargeable
. If it is not, its status is automatically transitioned to canceled
and your integration receives a source.
webhook event. Additionally, pending
sources are canceled after one hour if they are not used to authenticate a payment.
Once a source is canceled, the customer’s authenticated payment is refunded automatically—no money is moved into your account. For this reason, make sure the order is canceled on your end and the customer is notified once you receive the source.
event.