ACH: United States's bank transfer
The US Automated Clearing House — batch bank-to-bank transfers underlying payroll, bill pay, B2B and pay-by-bank.
How the ACH flow works
ACH is the US batch clearing network operated by Nacha rules on top of the Federal Reserve's FedACH and The Clearing House's EPN. It moves debits (pulls) and credits (pushes) between US bank accounts.
For merchants, ACH debit is the workhorse for pay-by-bank checkout and recurring collection. The consumer provides routing and account numbers (or authorises via an open-banking connector like Plaid/Finicity). The merchant initiates a debit against the account.
Batches settle T+1 or T+2; Same-Day ACH is available at higher cost. Consumers can dispute unauthorised debits under Reg E, which is the main operational risk.
For instant use cases, RTP and FedNow now sit alongside ACH; but ACH still dominates by volume for B2B and recurring.
Typical use cases
- Recurring bill pay, SaaS, insurance, lending repayments — anywhere card interchange erodes margin.
- High-ticket B2B invoicing where ACH is cheaper and expected.
- Payroll and mass payouts.
Consumer reach
Every US bank account holder — hundreds of millions of accounts.
Who should accept ACH
- Any US subscription or B2B business collecting on cards today where ACH would materially cut fees.
- Merchants with high-ticket US invoicing.
- Platforms doing mass payouts to US sellers or contractors.
Operational detail
The operational half of every method profile — settlement, refunds, disputes, PSP coverage and licensing — is reserved for Payment Methods List founding partners. It's the part vendor sites won't publish and the part that actually decides whether ACH works for your stack.
Settlement time
How fast ACH funds land after the payer confirms, behaviour outside scheme hours, whether the rail settles gross or net, and the realistic T+n to sweep to USD/EUR — plus the PSPs where the advertised timeline actually holds in United States.
Book a founding-partner call →Refund mechanics
How ACH refunds are executed end-to-end when the rail has no scheme-level reversal — payer-initiated pulls, credit transfers, or PSP-fronted refunds — plus partial-refund support, time limits, and the API surface each PSP exposes.
Book a founding-partner call →Chargeback exposure
Whether ACH has any dispute construct at all, which recall/return/indemnity vectors actually exist on the rail, how consumer-protection rules in United States route claims back to merchants, and observed loss rates versus cards.
Book a founding-partner call →PSP coverage matrix
Which acquirers and aggregators run direct rail connections to ACH vs. reselling a partner, coverage depth and reliability, effective pricing bands, and who to pick when United States volume is your primary use case.
Book a founding-partner call →KYC & licensing notes
Requirements to accept ACH — local entity vs. cross-border MoR, licensing regime governing the rail in United States, KYC obligations at onboarding and per-transaction, and FX/reporting rules for foreign merchants.
Book a founding-partner call →