How to Accept ACH Payments With Stripe, Does Stripe Accept it, Know Easily 2026

From the Stripe Dashboard, click the gear icon to reach Settings, which is organized into Personal settings and Account settings sections — Personal details, Communication preferences, and Developers on one row, then Business, Team and security, and Your plans below that. ACH itself isn't configured from this general settings page, but it's the starting point for reaching Payments, where the actual payment methods list lives. If you're working in a sandbox, a blue banner across the top confirms you're testing and that changes here won't touch your live account.

ACH debit is what most businesses mean when they say "accept ACH payments" — you pull funds directly from a customer's bank account once they've authorized it, which works well for one-time purchases, invoices, and recurring subscriptions. ACH credit runs the opposite direction: the customer pushes funds to you from their own bank, which is less common for typical checkout flows and used more for things like payouts or B2B transfers initiated by the payer. Stripe supports both, but ACH Direct Debit under Payment methods is the one you'll set up for a standard storefront or invoicing use case.

Go to Payments in the left sidebar, then Payment methods, where Stripe lists every option available for your account alongside its type and where it's popular — Afterpay/Clearpay and Klarna under buy-now-pay-later, SEPA Direct Debit for Europe, Pix for Brazil, and ACH Direct Debit tagged Bank debit, popular in the United States. Click Finish setup next to ACH Direct Debit; Stripe flags it with a "Webhooks recommended" note, meaning you should have a webhook endpoint ready to catch the asynchronous status updates ACH payments generate, since they don't confirm instantly the way a card charge does.

Finishing ACH setup routes you through Stripe Financial Connections, which handles verifying that a customer's bank account is real and able to receive a debit. You'll choose which data types to request — Tokenized account and routing number is required to move money at all, while Balances, Account ownership details, and Transactions are optional add-ons that help catch fraud and reduce failed payments by confirming the account holder's name matches and funds are actually available. Stripe's own guidance on this screen recommends adding balances and ownership details specifically to cut down on failed transactions, so it's worth enabling them even though they're not mandatory.

ACH payments cost less per transaction than cards, but they settle far slower — typically several business days rather than the near-instant confirmation of a card charge, since the payment has to clear through the banking network. Because of that delay, ACH is a better fit for invoices, subscriptions, and larger purchases where a short wait is acceptable, rather than anything where a customer expects instant access to a digital product immediately after paying.

Stay in the sandbox environment and run a test transaction using Stripe's documented test bank account and routing numbers, which simulate a successful ACH debit without touching a real bank. Confirm your webhook correctly receives and handles the payment_intent status changes, since ACH transactions move through pending, processing, and succeeded (or failed) states over time rather than resolving in a single response the way a card payment does. Only switch to live mode once you've watched a full test payment move through each of those states correctly.