An eCheck is an electronic payment drawn on a checking account using the routing and account numbers printed on a check, processed as an ACH debit rather than as a paper item. The customer authorizes it online, by phone or on a form, and it typically settles in one banking day. Nacha, which governs the ACH Network, lists eCheck as another name for ACH payments.
An eCheck (electronic check) is an ACH debit that pulls a payment from the payer's bank account using its routing number and account number, with the payer's authorization. Despite the name, it doesn't go through the check collection system at all. It runs on the ACH Network under the Nacha Operating Rules.
The name is a holdover from the paper days: the customer reads the numbers off the bottom of a check and types them into a form. What happens after that is ordinary ACH. So "pay by eCheck" on a checkout page and "pay by bank transfer" on an invoice usually describe the same payment.
eCheck vs paper check
| Paper check | eCheck | |
|---|---|---|
| What the customer hands over | A signed paper check | Bank account details and an authorization |
| How it clears | Through the check collection system, after you deposit it | Through the ACH Network, as a debit you originate |
| Who starts the collection | You, by depositing it | You, by sending the debit (usually through a processor) |
| Timing | Depends on the mail, your deposit and your bank's hold policy | Settles the same day or next banking day under Nacha's rules for debits |
| If the money isn't there | A returned check | An ACH return, coded R01 (insufficient funds) or R09 (uncollected funds) |
| Who sees the account number | Everyone who handles the check | You and your payment provider |
The last row is a quiet advantage. A paper check carries the payer's account number in plain sight through every mailroom and office it passes through, which is part of why check fraud persists. An eCheck keeps that number inside the payment system.
The payments that get called eCheck
Behind the label, Nacha's rules classify every ACH entry by a Standard Entry Class (SEC) code, and several codes fit the everyday meaning of eCheck. These are summarized from Nacha's developer guide:
| Code | What happens | What Nacha requires before the debit |
|---|---|---|
| WEB | The customer enters bank details online and authorizes a debit | An online authorization, with the customer authenticated, and account validation on first use |
| TEL | A consumer gives bank details and authorizes the debit by phone | A recorded oral authorization or written confirmation for a single debit; a recorded oral authorization and a written copy for recurring ones |
| ARC | A check mailed to you, or to your lockbox, is converted into a single ACH debit | Notice to the customer before the check is accepted |
| BOC | A check handed over at the point of purchase is converted later, in the back office | Notice before the check is accepted |
| POP | A check is converted at the point of purchase, while the customer is present | Notice before the check is accepted, and a written authorization |
| RCK | A paper check that was returned unpaid is presented again as an ACH debit | Notice before the check is accepted |
Check conversion has a ceiling. Nacha's return code list treats an ARC, BOC or POP entry over $25,000 as an amount error (R19), so larger checks stay on paper. Business customers paying online from a business account would normally be debited under the corporate code, CCD, rather than WEB.
How an eCheck payment works, step by step
Say a homeowner owes a roofing contractor a $3,850 deposit, and the contractor sends a link to a hosted payment page on Monday 7 December 2026.
- The customer enters bank details. The account holder's name and the account type, plus the routing and account numbers read off a check or the banking app.
- The customer authorizes the debit. They tick a box agreeing to a one-time debit of $3,850, which makes this a WEB entry.
- The account is validated. Because it's the first debit to this account, Nacha requires the contractor's fraud screening to include account validation. The payment provider usually runs this step.
- The debit goes out. The provider sends it that afternoon, dated for Tuesday 8 December.
- The payment settles. On Tuesday 8 December, $3,850 leaves the homeowner's account.
- The return window runs. For most reasons, including insufficient funds, the homeowner's bank has until the opening of business on Thursday 10 December to send it back. A claim that the debit was unauthorized can come much later: up to 60 days for a consumer, which here runs to the banking day after Saturday 6 February 2027, Monday 8 February.
The contractor can reasonably order materials once Thursday has passed without a return. The 60-day window is the reason to keep the customer's online authorization on file: if the homeowner later claims the debit wasn't authorized, that record is the contractor's evidence when it takes the matter up with the homeowner.
What you need to accept eChecks
Accepting eChecks means accepting ACH debits, so the setup is the same as for any ACH debit. You need a provider that can originate ACH for you and an authorization flow for each channel you use, and you need to validate accounts and handle returns. Our step-by-step guide to how to accept ACH payments walks through each part, including the fees to ask about.
The customer-facing part is mostly about where the option appears. A hosted payment page that offers both card and bank payment lets each customer choose, and keeps the bank details off your own systems. If you still receive paper checks in the mail, ask your bank or processor whether converting them to ARC entries makes sense for your volume.
Frequently asked questions
Is an eCheck the same as depositing a check with my phone?
No. A mobile deposit sends a picture of a paper check to your bank, and the check is collected as a check. An eCheck never involves a check image. The customer gives you the account details and an authorization, and the payment runs through the ACH Network as a debit. The two follow different rules and come back for different reasons.
Can an eCheck bounce?
Yes. If the customer's account doesn't have enough available money, its bank returns the debit with code R01 or R09, normally within two banking days of settlement. If you try again, Nacha caps reinitiation of a returned entry at two attempts, and each retry must be labelled "RETRY PYMT". The full list of reasons is in ACH return codes.
Are eChecks safe to accept?
They carry less exposure than paper checks in some ways, because the account number isn't printed on a document passing through many hands. The main risks are a debit returned for insufficient funds and, for consumers, a late claim that the debit wasn't authorized. Validating accounts and keeping authorization records reduce both, and so does using a business name customers recognize.
Sources
- Nacha: What Is ACH?, accessed 15 November 2026
- Nacha ACH Guide for Developers: ACH File Details, accessed 15 November 2026
- Nacha: How ACH Payments Work, accessed 15 November 2026
- Nacha: ISO 20022 Guide to Mapping U.S. ACH Return Items and Notifications of Change (PDF, August 2023), accessed 15 November 2026
- Nacha: Supplementing Fraud Detection Standards for WEB Debits, accessed 15 November 2026
- Nacha: RMAG Originator Essentials (PDF, 2024), accessed 15 November 2026
- Nacha: ACH Network Risk and Enforcement Topics, accessed 15 November 2026
- Nacha: Minor Rules Topics, accessed 15 November 2026