What Is an eCheck? How Electronic Checks Work, Step by Step

An eCheck borrows the name of a paper check, but nothing is written, mailed or scanned. It's an ACH debit. ACH (Automated Clearing House) is the U.S. network banks use to move money between accounts in batches. It also carries direct deposit and many bill payments.

"Debit" means the business pulls the money. The payer gives the business their bank details and permission, and the business's payment system asks the payer's bank for the funds. That's why an eCheck payment shows up in a checkout or invoice as "pay by bank account" or "pay by eCheck."

How an eCheck compares with a paper check:

For a business, the big draw is cost. Authorize.Net's eCheck page says its eCheck fees are "capped at 0.75%," against card fees it puts at "often 2% to 4%." Prices through a provider vary. Our eCheck and ACH processing fees guide breaks down what businesses actually pay.

An eCheck passes through several hands between the payer's bank account and the business's. Here's the path, using Nacha's names for each player. Nacha is the organization that writes the rules for the ACH network.

1. The payer authorizes the payment. They enter their bank details on a checkout page, read them out on a call or sign a form, and agree to the debit. How they authorize decides the payment's SEC code, a three-letter label such as WEB (online) or PPD (signed form). Our ACH SEC codes and authorization guide covers each one.
2. The business submits it through its payment gateway. The gateway is the software that sends payments from your website, virtual terminal or invoices. On Authorize.Net, eCheck goes through the same gateway as cards. Some details get checked here: since March 18, 2022, Authorize.Net verifies the account number as well as the routing number on online (WEB) payments and the first payment in a recurring series.
3. The originating bank sends it into the ACH network. Nacha calls this bank the ODFI (originating depository financial institution). It bundles payments into a batch file and sends the file to an ACH operator.
4. An ACH operator sorts and routes it. There are two: the Federal Reserve and The Clearing House. They send each payment to the right bank.
5. The payer's bank takes the money out. Nacha calls it the RDFI (receiving depository financial institution). It withdraws the funds from the payer's account.
6. The payment settles and the business is funded. Nacha says ACH debits typically settle the same day or the next banking day between banks. Getting the money into your account takes longer: Authorize.Net quotes "three to five business days" on its eCheck page and "up to seven days" in its developer guide. Our guide to how long an eCheck takes to clear explains the gap.
7. Or the payment comes back. If the account is short of money, closed or doesn't exist, or the payer says they never authorized it, their bank returns the payment with a code, such as R01 for insufficient funds. See ACH return codes for what each means and what to do.

The key difference from a card: a card sale is approved or declined in seconds. Authorize.Net's developer guide says eCheck payments "do not receive immediate authorization from the customer bank." The gateway accepts the payment, but the payer's bank has its say later.

Authorize.Net's eCheck page says customers typically supply "a bank routing number, account number, payment amount, and authorization to withdraw the funds." In practice, a checkout or form asks for:

• Routing number: the 9-digit number that identifies the bank.
• Account number: the payer's own account at that bank.
• Account type: checking, savings or business checking.
• Name on the account.
• The amount, and for repeat payments, how often and on what dates.
• Authorization: a checkbox and wording online, a recorded or confirmed phone call, or a signed form.

The authorization is the part businesses most often get wrong. What it must say depends on how the payer agrees and whether the payment repeats. For example, federal Regulation E says a recurring debit from a consumer's account needs a written authorization that is "signed or similarly authenticated," and the consumer gets a copy. Our ACH authorization form templates cover online, phone and paper.

Paying by eCheck? You don't need a checkbook. See how to send an eCheck for where to find your bank numbers, what you're agreeing to and how to stop a payment.

For both sides, an eCheck is about as safe as the business handling it. Rules on each side add protection.

If you're paying

• Federal protection for consumer accounts. Regulation E, enforced by the CFPB, covers ACH transfers from personal bank accounts. If an unauthorized debit shows up, report it to your bank within 60 days of the statement it appears on. Waiting longer can leave you liable for later unauthorized transfers.
• You can stop recurring debits. Reg E lets you stop a preauthorized payment by telling your bank at least three business days before it's scheduled.
• Business accounts are different. Reg E protects consumer accounts. Business accounts get less time to dispute a debit, so check business statements often.
• Common sense still applies. Give your bank details only to businesses you know, on a secure page or a form you can verify. Your account number is printed on every paper check you write, so an eCheck doesn't expose more than a check does.

If you're getting paid

The main risk for a business isn't stolen money. It's a payment that looks paid and then comes back, because the account was short or because someone used bank details that weren't theirs. Rules and tools that help:

• Account validation on online debits. Nacha's WEB debit account validation rule, in effect since March 19, 2021, requires businesses taking online (WEB) debits to validate an account number before its first use and whenever it changes. At minimum, that means checking the account is open and can accept ACH payments. Nacha doesn't prescribe a method and doesn't require proving who owns the account.
• Authorize.Net's account-number check. Since March 18, 2022, Authorize.Net checks the account number, not just the routing number, on WEB payments and the first payment in a recurring series. An invalid or mismatched number is declined at submission. Authorize.Net doesn't say it checks the balance, so a payment can still come back for insufficient funds.
• Fraud monitoring. Under Nacha's 2026 fraud-monitoring rules, businesses that originate ACH payments need risk-based processes to spot fraudulent payments, reviewed at least once a year. The rule reached the largest originators in March 2026 and all other businesses in June 2026.
• Records and timing. Keep every authorization, use a business name customers will recognize on their statements, and for high-value orders consider waiting until funds settle before you ship.

A consumer who tells their bank a debit wasn't authorized can have it returned long after you've been funded. Nacha allows 60 days for those returns, so good authorization records are your best defense. Our guide to returned eChecks covers return deadlines and limits.

Mostly, yes. "eCheck" and "electronic check" are two names for the same payment: an ACH debit the payer authorizes. ACH is the wider network. It also carries credits, where the sender pushes money out, such as payroll direct deposit or a company paying a supplier from its online banking. So every eCheck is an ACH payment, but not every ACH payment is an eCheck. A wire transfer is a different system altogether. For the full side-by-side, read eCheck vs ACH vs wire transfer vs credit card.

An eCheck payment makes the most sense where a lower fee matters more than speed:

• Business-to-business invoices, where customers often prefer paying from a bank account.
• Large payments, where a percentage card fee adds up fast.
• Recurring bills such as rent, HOA dues, memberships, tuition and payment plans.
• Nonprofits and churches collecting regular gifts.

It's a poorer fit when you ship right away on low-margin orders, when customers expect instant confirmation, or when many of them bank outside the U.S. Authorize.Net's eCheck is for U.S.-based businesses and customers with U.S. bank accounts.

Most businesses offer eCheck next to cards, not instead of them. We set up the merchant account and Authorize.Net gateway together, and we've set up over 60,000 Authorize.Net accounts in more than 20 years. Our eCheck processing guide covers costs, timing, the rules and how to add it. Tell us what you sell and how customers pay, and we'll tell you whether eCheck fits.