ACH and eCheck processing — bank-to-bank electronic payments that move money directly from a customer's checking or savings account to yours — represent one of the most underutilized payment options in ecommerce. Processing rates are a fraction of credit card rates, the dispute mechanics are structurally different from card chargebacks, and adoption has grown consistently as consumers become more comfortable with direct bank payment methods.

For merchants, particularly those in categories where credit card processing is expensive or difficult to maintain, ACH adds a meaningful alternative payment channel. For developers integrating payment flows, understanding how ACH differs from card processing — technically and operationally — is essential for building it correctly. This guide covers both.

ACH vs. eCheck: What's the Difference?

In common usage, ACH and eCheck are often treated as interchangeable — and in practice they largely are from a merchant perspective. Technically, ACH (Automated Clearing House) is the US payment network that processes electronic bank transfers, while eCheck is a specific payment format that uses ACH rails to process what is essentially a digital version of a paper check. Both move money from a bank account using routing and account numbers; the difference is primarily in how the authorization is captured and presented.

CyoGate's eCheck processing uses the ACH network and supports both web-initiated (WEB) and telephone-initiated (TEL) authorization formats — the two most common for ecommerce and phone order merchants respectively.

Why ACH Rates Are So Much Lower Than Cards

Credit card processing rates reflect the cost of the infrastructure involved: the card network (Visa/Mastercard), the issuing bank, the acquiring bank, the gateway, and fraud liability all get a piece of each transaction. A typical card transaction costs 2–3.5% of the transaction value plus a per-transaction fee.

ACH bypasses the card network entirely. Transactions move directly between banks through the Federal Reserve's ACH network or the Electronic Payments Network. Without card network interchange fees, issuing bank markup, or card fraud liability pricing, ACH transaction costs run significantly lower — typically $0.25–$1.50 per transaction as a flat fee, or a small percentage (0.5–1%) for high-value transactions. On a $500 transaction, the difference between 2.5% card processing ($12.50) and $0.75 ACH processing is substantial at volume.

The ACH Processing Flow

Understanding how an ACH transaction moves helps set correct expectations about timing and reversals:

  1. Authorization capture. The customer provides routing number and account number, and authorizes the debit. For web transactions, this happens through an online form. For phone orders, verbal authorization is recorded.
  2. Submission to ACH network. Your payment processor submits the transaction to the ACH network in a batch, typically once or twice daily.
  3. Settlement. The ACH network processes the batch and initiates the transfer from the customer's bank to yours. Standard ACH settlement takes 1–3 business days. Same-day ACH (available for qualifying transactions submitted before a daily cutoff) settles the same business day.
  4. Funds availability. Funds typically become available in your account 1–3 business days after submission, depending on your processor's funding policy.
  5. Return window. The customer's bank has up to 2 business days to return the transaction for insufficient funds, closed account, or other issues. Return codes arrive within this window.

The key difference from card processing: there is no real-time authorization. When you run a card transaction, you get an immediate approval or decline response. With ACH, you get a confirmation that the transaction was submitted — but you won't know for 1–2 business days whether the account had sufficient funds or whether it exists at all. Plan your fulfillment workflow accordingly: for physical goods, either accept the settlement delay before shipping, or use account verification (see below) to reduce the risk of shipping before an NSF return arrives.

ACH Returns: Not Quite Chargebacks

ACH has its own dispute/return mechanism that differs meaningfully from card chargebacks — both in how it works and in the timeframes involved.

Standard returns (R-codes). The most common ACH returns are administrative: R01 (insufficient funds), R02 (account closed), R03 (no account/unable to locate account), R04 (invalid account number). These arrive within 2 business days and are operationally similar to a card decline — the transaction failed, you don't get paid, you may or may not retry depending on your policy.

Unauthorized transaction returns (R10, R29). A customer can claim a transaction was unauthorized, which initiates a return. Unlike card chargebacks where the dispute window is typically 60–120 days, ACH unauthorized claims have a 60-day window for consumer accounts. This is shorter than many card chargeback windows and the process is more limited — the customer's bank requires a written statement of unauthorized use before initiating the return.

Why ACH returns are structurally different from chargebacks. Card chargebacks flow through Visa/Mastercard rules which create liability for the merchant and count against your chargeback ratio at your card processor. ACH returns are handled between banks through Nacha rules — they don't count against your card processing chargeback ratio, and the dispute process is less automated and harder for customers to initiate than a card dispute. This structural difference is one reason high risk merchants often supplement card processing with ACH: ACH disputes are less likely to threaten your card processing relationship.

Nacha return rate thresholds: Nacha (the ACH network governing body) monitors return rates for ACH originators. An overall return rate above 15%, or an unauthorized return rate (R05, R07, R10, R29) above 0.5%, can result in your ACH processor restricting or terminating your origination privileges. This is a separate metric from your card chargeback ratio — maintain both.

Account Verification Before Debiting

Because ACH has no real-time authorization, pre-transaction account verification reduces the risk of returns and failed payments. Two approaches are available:

Micro-deposit verification. The traditional method: two small deposits (typically $0.01–$0.99) are made to the customer's account, and the customer confirms the amounts. This verifies that the account exists, accepts deposits, and belongs to the customer. The downside is the delay — 1–3 business days for the deposits to arrive before the customer can complete verification. Workable for recurring billing setups where the verification happens once upfront, less practical for one-time purchases where customers won't wait.

Instant bank verification. Newer services (Plaid, Finicity, and similar) allow customers to log in to their bank through a secure portal and verify their account instantly, without the micro-deposit delay. The verification service confirms account ownership, routing and account number accuracy, and in some cases real-time balance. This dramatically improves the echeck checkout experience and reduces NSF returns. CyoGate's echeck processing supports instant verification integration for merchants who need it.

Integration: What's Different from Card Processing

For developers integrating ACH alongside card processing, the key technical differences:

Different fields. Instead of card number, expiration, and CVV, ACH requires routing number (9 digits), account number, account type (checking or savings), and the account holder name. Your checkout form needs to accommodate both payment types or present separate forms.

No real-time approval/decline. Your integration needs to handle the "submitted" state differently from card approvals. The customer should be informed that payment will be processed within 1–3 business days, and your order management system needs to handle the pending-to-confirmed transition when settlement completes.

Return handling. Your integration needs to process return notifications from your processor when ACH returns arrive. Unlike a card decline that happens synchronously, ACH returns arrive asynchronously via webhook or daily report. Build logic to handle R01 (insufficient funds, possibly retryable) differently from R02 (account closed, not retryable).

Authorization records. Nacha rules require that you retain evidence of customer authorization for ACH debits — the IP address, timestamp, and the authorization language the customer agreed to for web transactions; the call recording or written authorization for telephone transactions. Retain these records for at least 2 years.

CyoGate's echeck processing connects through the same gateway API used for card transactions, with ACH-specific transaction types. The developer portal has full API documentation for ACH transaction submission, return handling, and webhook configuration.

When ACH Makes Sense for Your Business

ACH is not a replacement for card processing — it's a complement. The use cases where adding ACH delivers the most value:

High-ticket B2B transactions. A business paying a $5,000 invoice by ACH saves both parties the $125+ in card processing fees that would otherwise apply. B2B customers with purchasing authority often prefer ACH or wire transfer for invoiced amounts, and offering it removes a friction point for large transactions.

Recurring billing for known customers. Monthly subscriptions, membership fees, and installment payments work well via ACH for customers with established relationships. The verification happens once; subsequent debits run without requiring the customer to take any action.

High risk merchants supplementing card processing. For categories where card processing is expensive or restricted, ACH offers a lower-cost channel with different dispute mechanics. A merchant whose card processing costs run 5–6% offshore can offer ACH to customers who prefer direct bank payment at a fraction of that cost.

Markets where ACH preference is high. Certain customer segments — older demographics, B2B buyers, customers in specific industries — have higher ACH preference than the general ecommerce population. If your customer analytics show significant demand for bank payment options, adding ACH captures revenue you're currently losing to payment method unavailability.

Ready to add eCheck processing to your payment mix? Learn more about CyoGate's eCheck processing or contact us to discuss how it integrates with your existing merchant account setup.