ACH payments form the backbone of electronic money movement in the United States, handling everything from payroll disbursements to recurring subscription billing. Understanding how the ACH network operates is essential for any merchant or developer building payment flows on US bank rails.
How ACH Payment Works
An ACH payment moves money between two US bank accounts by routing the transaction through the Automated Clearing House network, a batch-processing system governed by Nacha. Unlike card networks that authorize transactions in real time, ACH collects entries into batches and forwards them to receiving banks in scheduled settlement windows throughout the business day.
Origination
The originator — a business or individual — submits a payment entry to their bank, called the Originating Depository Financial Institution (ODFI). The entry contains the receiver's routing number, account number, transaction amount, and an SEC code specifying the payment type (PPD, CCD, WEB, etc.).
Batch Formation
The ODFI aggregates ACH entries into a batch file formatted to Nacha standards and submits it to an ACH operator — either the Federal Reserve's FedACH system or the Clearing House's EPN (Electronic Payments Network).
Routing and Sorting
The ACH operator sorts each transaction by destination and forwards the entries to the appropriate Receiving Depository Financial Institution (RDFI) — the bank that holds the receiver's account.
Posting and Settlement
The RDFI posts the transaction to the receiver's account. Interbank settlement occurs between the Federal Reserve accounts of the ODFI and RDFI. For standard ACH, this takes 1–3 business days; Same-Day ACH completes within the same business day if submitted before the operator cutoff.
Return Window
After posting, a return window remains open. The RDFI can return a transaction — for insufficient funds, a closed account, or an unauthorized debit — within 2 business days for most return codes. Consumers disputing unauthorized debits have up to 60 days from the statement date.
Why ACH Payment Matters
The ACH network is one of the largest payment systems in the world by volume, and its cost advantage over card networks makes it a first-choice rail for high-value and recurring transactions. For payment professionals designing checkout and disbursement flows, ACH often delivers the highest margin per transaction available on US bank rails.
According to Nacha, the ACH network processed 30 billion transactions totaling $77.8 trillion in 2023 — a 4.8% increase in volume from the prior year. Same-Day ACH alone accounted for over 1.1 billion transactions that year, reflecting the network's ongoing shift toward faster settlement options.
The cost difference is material: ACH transactions typically cost merchants $0.20–$1.50 per transfer, compared to card interchange fees of 1.5–3.5% of transaction value. On a $10,000 B2B invoice, the difference between a $0.50 ACH fee and a 2.5% card fee is $249.50 per transaction — savings that compound quickly at volume.
Same-Day ACH growth
Same-Day ACH volume grew approximately 30% year-over-year in 2023, driven by adoption in payroll, gig economy disbursements, and B2B payments, according to Nacha's annual report. This growth trend has continued into 2024 and 2025 as more financial institutions enable same-day origination for their business customers.
ACH Payment vs. Wire Transfer
ACH and wire transfers both move money between bank accounts, but they operate on different rails with distinct trade-offs. Choosing between them depends on speed requirements, transaction size, cost sensitivity, and reversibility needs.
| Feature | ACH Payment | Wire Transfer |
|---|---|---|
| Settlement speed | 1–3 business days (Same-Day available) | Same day domestic; 1–5 days international |
| Cost per transaction | $0.20–$1.50 | $15–$50 domestic; $25–$75 international |
| Reversibility | Returnable within 2 days; consumer disputes up to 60 days | Generally irrevocable once sent |
| Transaction limit | Up to $1M (Same-Day ACH) | Typically no ceiling |
| Best use case | Payroll, subscriptions, B2B invoices | Urgent large payments, real estate, international |
| Fraud risk | Moderate — return window provides some protection | High — irrevocable nature increases exposure |
| Geographic scope | US only | Global |
For most recurring and high-volume use cases, ACH debit is preferable to wire due to lower cost and the built-in return mechanism. Wire transfers suit large, time-critical, or international payments where speed and finality outweigh the price premium.
Types of ACH Payment
The ACH network supports two primary payment directions, each serving distinct use cases in merchant and enterprise payment flows. Understanding the difference is necessary for designing correct authorization, settlement, and reconciliation logic.
ACH Credit is a push payment — the account holder or business initiates an outbound transfer of funds. The most common example is payroll: an employer pushes wages into employee bank accounts on payday. Other examples include government benefits disbursements, vendor payments, and insurance claim payouts. ACH credit transactions are always originated by the payer.
ACH Debit is a pull payment — the merchant or business pulls funds from a customer's account with prior authorization. Examples include monthly SaaS subscription billing, mortgage payments, and utility bill collection. ACH debit requires the payer to provide a signed or verifiable electronic authorization before any funds can be collected; this requirement is mandated by Nacha operating rules.
Same-Day ACH applies to both credits and debits and enables same-business-day settlement for transactions submitted before the operator's cutoff windows. It carries a Nacha-mandated per-entry fee (currently $0.052, passed through by the ODFI) and supports transactions up to $1 million per item.
International ACH Transaction (IAT) is a specific SEC code required when one party holds an account at a financial institution outside the United States. IAT entries are subject to OFAC screening and additional compliance and reporting obligations beyond standard domestic ACH rules.
Best Practices
Consistent ACH performance depends on clean data collection, proper authorization, and proactive return rate management. Nacha monitors originator return rates and can fine or restrict originators whose unauthorized debit returns exceed 0.5% of total ACH debit volume.
For Merchants
Collect bank account details through a tokenized verification service — micro-deposit confirmation, instant verification via open banking APIs, or real-time account validation — before originating any debit. Store routing and account numbers encrypted at rest and never in plain text or logs. Obtain explicit written or verifiable electronic authorization from the account holder before initiating any ACH debit; retain that authorization with timestamp, IP address, and agreement text. Notify customers of upcoming debits at least 10 days in advance unless a shorter notice period is specified in the authorization agreement. Monitor return code dashboards daily — elevated R01 (insufficient funds) rates are a signal to implement balance verification before large debits; elevated R10 (not authorized) rates indicate an authorization capture problem requiring immediate remediation.
For Developers
Use the correct SEC code for each transaction type: PPD for consumer accounts with pre-authorized agreements, CCD for business-to-business transactions, WEB for internet-initiated consumer debits, and TEL for telephone-authorized debits. Implement idempotency keys on ACH submission endpoints to prevent duplicate entries when requests are retried after network timeouts. Handle return codes programmatically — map R01 (insufficient funds), R02 (account closed), R03/R04 (no account or invalid account), and R10 (customer advises not authorized) to distinct downstream workflows rather than treating all returns identically. Subscribe to electronic funds transfer event webhooks from your payment provider to receive real-time return notifications rather than polling transaction status endpoints.
Common Mistakes
Even experienced payment teams make ACH implementation errors that lead to elevated return rates, compliance exposure, or missed settlement windows.
1. Skipping or storing authorization improperly. Nacha requires a valid authorization for all ACH debits. Failing to retain it — or using an authorization that does not meet Nacha standards for the SEC code — exposes you to R10 returns and potential fines. WEB entries specifically require evidence of the internet channel, including IP address and timestamp.
2. Using the wrong SEC code. Sending a consumer debit under CCD instead of PPD, or processing an internet-initiated debit without the WEB SEC code, violates Nacha rules and can trigger returns and compliance audits. Always match the SEC code to the initiation channel and account type.
3. Treating ACH as settled before the return window closes. ACH transactions that appear posted can still be returned for up to 60 days for unauthorized consumer debits. Releasing goods, paying out balances, or finalizing reconciliation before the return window closes creates cash flow and fraud risk, particularly for marketplace and lending platforms.
4. Not validating bank accounts before first origination. Submitting ACH entries to closed or incorrect accounts generates R02 and R03/R04 returns that count against your return rate metrics. Use instant account verification or micro-deposit confirmation before the first debit or credit to any new bank account.
5. Missing Same-Day ACH submission cutoffs. Same-Day ACH has strict submission windows — typically 2:45 PM ET and 4:45 PM ET for FedACH. Entries submitted after the final window fall to next-day processing, breaking SLA commitments to employees, vendors, or customers who expected same-day funds.
ACH Payment and Tagada
Tagada's payment orchestration layer supports ACH payment routing as part of its multi-rail strategy, enabling merchants to automatically route transactions to ACH when card rails are more expensive or operationally unnecessary. For subscription businesses and B2B platforms, this means Tagada can select ACH for high-value or recurring charges based on configurable routing rules, capturing interchange savings without manual intervention.
Use Tagada's routing rules to automatically fall back from ACH to card when a direct debit returns R01 (insufficient funds), preventing failed-payment churn without requiring your team to build custom retry logic per processor.
Tagada also normalizes ACH return code handling across multiple bank and processor integrations, so engineering teams implement return workflows once rather than per-ODFI. This is particularly valuable for platforms managing ACH origination through multiple financial institution partners at scale.