What is an eCheck?
An eCheck is a digital version of a traditional paper check that transfers funds electronically from the payer's checking account to the payee's account via the ACH network. It contains the same core information as a paper check: the payer's account number, routing number, and the payment amount. The difference is that it is submitted and processed digitally rather than physically.
eChecks are also referred to as electronic checks, online checks, internet checks, or ACH debits. In fintech and payments infrastructure contexts, they are more commonly called ACH debits. The consumer-facing term "eCheck" is most common in billing, B2B payments, and SMB contexts.
How eChecks work
An eCheck is a pull payment. The payee initiates the transaction by debiting the payer's account, rather than the payer sending the funds directly. This is the same model as a direct debit. The process works as follows:
- The payer authorizes the payment by providing their account number, routing number, and authorization. This can be done via a signed form, an online checkout form, or a recorded verbal agreement
- The payee submits the payment instruction to their bank or payment processor
- The payment processor formats the transaction as an ACH debit entry and submits it to the ACH network via an ODFI
- The ACH network routes the debit to the payer's bank (the RDFI), which verifies the account and processes the debit
- Funds are transferred and credited to the payee's account, typically within 3-5 business days
Authorization is a required step under NACHA rules. A payee cannot initiate an eCheck without explicit consent from the payer. For internet-authorized transactions, NACHA's WEB SEC code applies, which requires additional account validation and fraud prevention measures.
eCheck vs. paper check
eChecks and paper checks carry the same information but differ significantly in how they are processed.
eCheck vs. ACH debit
These two terms describe the same underlying transaction. An eCheck is the consumer-facing name for an ACH debit. When a business says it accepts eChecks, it means it can initiate ACH debits from customer bank accounts.
The distinction matters mainly in context. In consumer billing and SMB settings, "eCheck" is the common term. In payment infrastructure, API documentation, and fintech contexts, the same transaction is called an ACH debit, and the relevant rules, return codes, and compliance obligations are all framed in ACH terms.
Common use cases
eChecks are well suited to high-value or recurring payments where card processing fees would be prohibitive.
- Recurring billing: Rent, utilities, insurance premiums, gym memberships, and subscription services. Customers authorize once and the payee collects on schedule
- B2B payments: Supplier invoices, contractor payments, and intercompany transfers where the flat-fee cost structure of ACH is significantly cheaper than card
- Government and tax payments: Many government agencies accept eChecks for tax remittances, fines, and fee payments
- High-value purchases: Real estate deposits, large equipment purchases, and professional service retainers where the dollar amount makes card fees impractical
eCheck returns
Like any ACH debit, eChecks can be returned by the receiving bank if the transaction cannot be completed. Common reasons include insufficient funds (R01), a closed account (R02), or a claim that the debit was unauthorized (R07 or R10).
Returns can arrive up to 2 banking days after settlement for most reasons, or up to 60 calendar days for unauthorized consumer debits. Businesses processing eChecks should monitor ACH return codes and return rates to stay within NACHA's thresholds. Using account validation before initiating the first eCheck to a new customer reduces the risk of administrative returns from bad account details.
