Bank redirects
Learn about bank redirects with Stripe.
Bank redirects let customers pay online using their bank account. They drive more than half of online commerce in Germany, the Netherlands, and Malaysia. Bank redirects are often used by:
- Retailers that want to improve conversion and reduce fraud with consumers in Europe and Asia Pacific.
- Software or service businesses collecting one-time payments from other businesses.
Some bank redirects support subscriptions and recurring payments. See the product support table below for details on which payment methods support subscriptions.
Payment flow
At checkout, the customer is redirected to their online banking portal, logs in with their bank credentials, approves the transaction, and then returns to your site. Some bank redirects verify the user through SMS or other two-factor authentication for additional security.
Product support
We’ve created a single integration for all bank redirects that works across Stripe products. With Stripe Checkout, you can add any bank redirect by changing one line of code.
| Payment method | Connect | Checkout | Payment Links | Payment Element | Express Checkout Element | Mobile Payment Element | Subscriptions | Invoicing | Customer Portal |
|---|---|---|---|---|---|---|---|---|---|
| Bancontact | 7 | Invite only | |||||||
| the related setting | 1,2 | 3,4 | |||||||
| EPS | 1,2 | 7 | Invite only | ||||||
| FPX | 1,2 | 7 | |||||||
| iDEAL | Wero | 5,6,7 | 6 | |||||||
| P24 | 1,2 | 7 | Invite only | ||||||
| the related setting | 1,2 |
1 Not supported when using Checkout in subscription mode. 2 Not supported when using Checkout in setup mode. 3 Not supported when collecting payment details before creating a PaymentIntent. 4 Not supported when using Elements with the Checkout Sessions API. 5 Only supported when using Checkout in subscription mode. 6 Not supported when using charge_automatically for subscriptions or invoices. iDEAL is a single use payment method where customers are required to authenticate each payment. 7 Invoices and Subscriptions only support the send_invoice collection method.
Contact us to request a new bank redirect payment method.
API support
| Payment method | API enum | PaymentIntents | SetupIntents | Manual capture | Setup future usage 1 | Requires redirect 2 |
|---|---|---|---|---|---|---|
| Bancontact | bancontact | 3 | Yes | |||
| the related setting 4 | blik | No | ||||
| EPS | eps | Yes | ||||
| FPX | fpx | Yes | ||||
| iDEAL | Wero | ideal | Yes | ||||
| P24 | p24 | Yes | ||||
| Pay by Bank | pay_by_bank | Yes | ||||
| the related setting | twint | Yes |
1 Cards and bank debit methods including the related setting debit, AU the related setting direct debit and the related setting debit support both on_session and off_session with setup future usage. All other payment method types either don’t support setup_future_usage or only support off_session. 2 Payment methods might require confirmation with return_url to indicate where Stripe should redirect your customer after they complete the payment. 3 Bancontact supports setup_future_usage by saving the customer’s bank details as a the related setting Direct Debit payment method. 4 the related setting doesn’t support the deferred intent creation integration path.
Migrating from the Sources or Tokens APIs
If you currently use the Sources or Tokens API, see migrating to PaymentIntents to use the latest integrations.