ACH is not a card replacement. It's a tool for the right transaction types. B2B payments, high-ticket professional services, and recurring billing on large invoices are where ACH delivers the most value. Consumer ecommerce under $100 per transaction is usually better served by card. The question is where in your payment mix ACH changes the economics.
What ACH actually is
ACH stands for Automated Clearing House; the network that processes bank-to-bank electronic transfers in the United States. When you pay a vendor by bank transfer, receive a direct deposit payroll, or autopay a utility bill, that transaction runs on the ACH network. It is governed by NACHA (the National Automated Clearing House Association), which sets the rules for transaction types, authorization requirements, return handling, and return rate thresholds.
An eCheck is essentially ACH payment initiated from a check account, processed electronically rather than as a paper instrument. For practical purposes, ACH and eCheck refer to the same underlying payment rail when used in a merchant context.
ACH transactions are categorized by entry class code. The most common for merchant use are WEB (internet-initiated, consumer), CCD (corporate credit or debit, B2B), and PPD (prearranged payment, consumer recurring). Each has different authorization requirements and return handling rules.
Where ACH makes sense vs. where cards are better
| Transaction type | ACH | Card |
|---|---|---|
| B2B invoices, high-ticket | ✓ Strong fit; significant cost savings | ~ 2–3% on large amounts adds up fast |
| Professional services retainers | ✓ Recurring ACH is cost-effective and reliable | ~ Works, but card fees erode margin on fixed amounts |
| Consumer ecommerce, low ticket | ~ ACH adds friction; not ideal under $100 | ✓ Card is expected; minimal friction |
| Large recurring subscriptions | ✓ Lower cost, fewer card expiration issues | ~ Card Updater helps; still higher cost |
| Government and nonprofit payments | ✓ Often preferred; cards sometimes not accepted | ~ Card surcharge programs add complexity |
| Impulse or time-sensitive purchases | ~ Settlement delay creates friction | ✓ Immediate authorization; customer expects it |
What we set up and what you need to know
ACH setup and integration
We identify the right ACH processor for your transaction profile, handle the application, and coordinate integration with your existing payment stack. ACH can typically run alongside your card processing without requiring a separate merchant account.
NACHA compliance
NACHA requires specific authorization language, record retention, and return rate management depending on your entry class. We make sure your ACH program meets the requirements before you process a single transaction.
Return rate management
NACHA's unauthorized return rate threshold is 0.5% of transactions. Exceeding it triggers a compliance review and potential processor action. We monitor your return rates and advise on authorization practices that keep you below threshold.
Same-day ACH
Same-day ACH is available for eligible transactions and significantly reduces the settlement delay that makes ACH less appealing for time-sensitive payments. We advise on where same-day ACH fits in your payment flow and what it costs relative to the benefit.
Authorization and verification
ACH authorization must be documented and retained. For WEB transactions, bank account verification (micro-deposit or real-time verification) is required before the first transaction. We build the verification workflow into your setup correctly from the start.
Recurring ACH billing
Recurring ACH requires a specific authorization that covers the recurring nature, the amount, and the frequency. The authorization must be provided to the customer and retained by the merchant. We set up recurring ACH programs that meet NACHA requirements and keep return rates low.
ACH return rates matter more than most merchants realize. NACHA monitors unauthorized return rates (R10 and R29 return codes) and overall return rates separately. The unauthorized return rate threshold is 0.5%; the administrative return rate threshold is 3%. Exceeding these thresholds can result in a NACHA compliance review and processor termination from the ACH network. Getting authorization right on the front end is the only reliable way to stay below threshold.