Bank Debits

Learn how to accept bank debits with Stripe.

With bank debits, you can pull funds directly from your customer’s bank account for both one-time and recurring purchases. Bank debits are often used by:

Businesses collecting recurring payments from other businesses.
Retail and services businesses that want a low-cost alternative to cards for large consumer payments, like rent or tuition.

Bank debits might not be a good fit for your business if:

You deliver goods immediately after checkout because payment confirmation takes several business days.
Your business is sensitive to disputes—consider other payment methods because some bank debit methods favor the customer during disputes.

Payment flow

To initiate a bank debit, a customer enters their bank account details during checkout and gives you permission to debit the account. This permission is called a mandate.

Flow chart of the three step process the customer experiences. First, they select bank debit at checkout. Next the customer provides banking details and authorizes mandate. Finally, the customer gets notification that the payment is complete.

To reduce fraud with some bank debits, verify the bank account before the payment by confirming microdeposits or bank login. Verifying bank login can improve the user experience because customers pay by logging into their bank rather than entering bank account details.

Product support

You can use a single integration for all bank debits that works across Stripe products. With Stripe Checkout, Payment Element, and Payment Links, you can enable bank debits directly from the Dashboard with no integration work.

Payment method	Checkout	Payment Element	Subscriptions
Instant Bank Payments or ACH Direct Debit
Bacs Direct Debit			¹
Australia BECS Direct Debit
New Zealand BECS Direct Debit
Pre-authorized debit in Canada	²	^3,4
SEPA Direct Debit

¹ You can’t use the Payment Element to create SetupIntents for Bacs Direct Debit. Use Checkout in setup mode instead.
² Not supported when using Checkout in subscription mode.
³ Supports ACSS debit if you create a PaymentIntent before rendering the Payment Element.
⁴ Not supported when using Elements with the Checkout Sessions API.

API support

Payment method	API enum	PaymentIntents	SetupIntents	Requires redirect²
ACH Direct Debit	`us_bank_account`			No
Bacs Direct debit	`bacs_debit`	³	⁴	No
Australia BECS Direct Debit	`au_becs_debit`			No
New Zealand BECS Direct Debit	`nz_bank_account`			No
Pre-authorized debit in Canada⁵	`acss_debit`			No
SEPA debit	`sepa_debit`			No

¹ Cards and bank debit methods including SEPA debit, AU BECS direct debit, and ACSS 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.
² Payment methods might require confirmation with return_url to indicate where Stripe should redirect your customer after they complete the payment.
³ PaymentIntents support confirmation with Bacs Direct Debit payment methods when the Mandate has been collected by a Stripe-owned flow such as Checkout, Payment Element, and Payment Links.
⁴ You can create SetupIntents for Bacs Direct Debit through Checkout using setup mode.
⁵ Pre-authorized debit in Canada doesn’t support the deferred intent creation integration path.

Migrating from the Sources, Tokens, or Charges APIs

If your current bank debit integration uses the Sources, Tokens, or Bank Accounts API, we recommend following the appropriate migration guide to transition to Payment Intents API:

ACH migration guide
For all other bank debit payment methods, follow the general migration guide