IntelliPay is a PCI DSS Level 1 payment processor serving government agencies, healthcare providers, and businesses across the United States. This guide explains how eCheck processing works, where it can lower acceptance costs, what affects settlement and returns, and what to review before launching an ACH debit program in 2026. Learn more about ACH payment options and government payment solutions.
Quick Read
An eCheck is an ACH debit used to collect a payment directly from a customer’s checking or savings account. It can be a lower-cost alternative to cards for larger invoices, recurring billing, and account-based payments.
- ACH pricing is commonly flat, capped, or negotiated rather than entirely percentage-based. Published market examples often place ACH in the $0.20 to $1.50 per-transaction range against 1.5% to 3.5% for card acceptance, which makes a meaningful difference on higher-dollar payments.
- Plan for settlement and funding to take several business days; an ACH debit submitted today is not necessarily final today. Most returns surface within two banking days of settlement, while consumer error-resolution rights under Regulation E can extend the dispute window to roughly 60 calendar days.
- Customer authorization, recognizable payment descriptors, account validation, return procedures, and reconciliation are core parts of a durable eCheck program.
- Nacha fraud-monitoring requirements became effective March 20, 2026 for larger originators and third-party senders, with additional non-consumer participants phasing in during June 2026.
- Offer eChecks alongside cards when possible: customers retain choice, while your organization has a lower-cost pay-by-bank option.
Cards are fast, familiar, and often the customer’s first choice. But on larger invoices, recurring charges, and account billing, percentage-based card costs can add up quickly. A $500 payment processed at 2.5% costs about $12.50 in card fees. A comparable ACH debit may be priced as a flat transaction fee or under a capped arrangement, depending on the provider and program. At scale the gap widens: $50,000 in monthly card volume at an average 2.5% represents roughly $1,250 in fees, while the same volume moved to ACH at a flat per-transaction price represents a fraction of that amount.
eChecks do not replace cards in every situation. They give customers another way to pay, and that option can be particularly useful for invoices, scheduled payments, utility bills, tuition, dues, and other payments tied to an ongoing account.
eCheck vs. ACH: the difference in plain terms
People often use “eCheck” and “ACH” as though they mean the same thing. They are closely related, but they describe different things.
ACH is the bank-transfer network. It carries direct deposits, bill payments, tax refunds, insurance payouts, account-to-account transfers, and customer debits. An eCheck is a payment use case that runs on that network: a business debits a customer’s bank account with the customer’s authorization, rather than receiving a paper check.
Put simply, every eCheck is an ACH transaction, but ACH supports many transactions that are not eChecks. In this guide, “ACH” refers to the network, settlement process, and return rules. “eCheck” refers to the collection method your organization offers to customers.
How eCheck processing works
An eCheck payment generally follows this sequence:
- Customer authorization. The customer authorizes a one-time debit or a recurring payment schedule from a checking or savings account.
- Payment entry. The payment is submitted through a hosted payment page, payment link, customer portal, virtual terminal, or connected billing system.
- Processor review. Your processor may perform routing, account, and risk checks before transmitting the transaction.
- ACH submission. The debit enters the ACH Network and is routed to the customer’s financial institution.
- Posting or return. The receiving institution posts the debit or returns it for a reason such as insufficient funds, a closed account, invalid account information, a duplicate entry, or an unauthorized claim.
- Reconciliation. Your team matches transactions, deposits, returns, and exceptions to the correct customer, invoice, or account.
Operational note: An ACH debit is not final simply because it was submitted. Before launch, decide who reviews returns, when a returned payment may be retried, when staff should request another payment method, and how customers will be notified.
How long eChecks take to settle
For many programs, plan on roughly three to four business days from submission to final funding, although the exact timing depends on your processor, transaction type, bank cutoffs, risk review, and funding policy. Weekends and federal holidays do not count, so a payment entered late Friday may not complete until the following week.
That delay is part of the risk model. It gives returns time to surface before an organization treats funds as fully available. Return timing varies by return reason and transaction type: many standard returns are transmitted within about two banking days of the settlement date, while consumer claims involving unauthorized electronic fund transfers can carry windows extending to roughly 60 calendar days under Regulation E error-resolution procedures. Retain authorization records and payment history in a format your team can retrieve quickly.
Same Day ACH can compress that schedule for eligible payments through three daily processing windows, subject to a per-payment dollar cap and to whether your processor and financial institution support it. Treat it as a separate service to ask about rather than the default behavior of an eCheck program.
Settlement takeaway
A posted payment and a final payment are not the same thing.
Build your funding policy, refund rules, and service-release decisions around the return window, not around the submission date.
eChecks vs. card payments
| Consideration | eCheck (ACH debit) | Card payment |
|---|---|---|
| Payment source | Customer checking or savings account | Credit, debit, or prepaid card account |
| Network | ACH Network | Card networks such as Visa and Mastercard |
| Common uses | Invoices, recurring bills, utility payments, tuition, dues, and account balances | Retail, e-commerce, phone payments, and fast checkout |
| Pricing model | Often flat, capped, or negotiated | Usually percentage-based, plus network and processor costs |
| Timing | Generally several business days, subject to cutoffs and funding policy | Authorization is usually near-instant; merchant funding varies by provider |
| Primary post-payment risk | Returns and unauthorized-debit claims | Chargebacks and card disputes |
A practical payment-choice strategy
Offer cards for speed and flexibility. Offer eChecks for a lower-cost pay-by-bank option.
Customers can choose the method that fits their situation, while you avoid making percentage-based card costs the only option for larger or recurring payments.
When eChecks make sense
eChecks are most useful when customers already pay from a bank account, payment amounts are larger, or billing occurs on a predictable schedule.
- Larger invoices: B2B billing, professional services, project milestones, wholesale purchases, and account balances
- Recurring billing: utilities, memberships, subscriptions, property management, insurance, dues, and installment plans
- Account-based payments: government agencies, schools, healthcare providers, and organizations that bill against a standing customer account
Consider a municipal utility bill as a simple example. A resident paying a $160 balance may prefer a card for convenience or rewards, while another may choose an ACH debit to avoid a card-related fee where permitted and properly disclosed. Supporting both paths makes the payment experience more flexible without treating every customer the same.
What eCheck processing costs
Providers can price eCheck acceptance as a flat fee per transaction, a percentage, a percentage with a cap, a monthly account fee, or a blended arrangement. Published market examples commonly show ACH fees in the $0.20 to $1.50 range per transaction, while card acceptance is more often priced at roughly 1.5% to 3.5% of the payment. Treat those figures as illustrative rather than quoted pricing. Your actual cost depends on volume, risk profile, payment channels, and the features included in the account, and any provider quoting eCheck acceptance at card-like percentages deserves a closer look.
Do not compare only the advertised transaction rate. A low ACH rate can look attractive on a sales sheet and still cost more in practice if return fees, account verification, recurring billing tools, reporting limitations, funding delays, integration work, or staff time are not included in the comparison.
Questions to ask before signing: Is the price fixed, percentage-based, capped, or blended? Which monthly, platform, gateway, account, or minimum fees apply? What are the return and account-verification fees? Does pricing change for recurring billing, virtual-terminal use, or API integration? Can funding be delayed by reserves, underwriting, or volume requirements?
Authorization and compliance
Because an eCheck is an ACH debit, the transaction is subject to the applicable Nacha Operating Rules. Customer authorization is essential, and the required authorization method and recordkeeping depend on the transaction type and how the authorization is collected, whether online, by phone, in writing, or as part of a recurring arrangement.
For consumer debits, authorization records should clearly identify the party collecting the payment, state whether the debit is one-time or recurring, explain the amount or how it will be determined, and describe the timing or schedule. Provide the customer with a copy or confirmation as required for the authorization method, and retain records that can be produced if the payment is questioned.
Nacha has introduced phased fraud-monitoring requirements for ACH participants. Obligations became effective March 20, 2026 for larger originators and third-party senders, with additional non-consumer participants phasing in during June 2026. These rules call for risk-based fraud detection, account validation, and mitigation practices sized to the organization’s role, volume, and risk profile, and they do not mandate a specific technology. Confirm effective dates, applicability, and responsibilities with your processor, sponsoring financial institution, legal counsel, and compliance team rather than assuming that a technology platform carries the entire obligation.
Account validation is especially important for internet-initiated debits and newly provided banking details. Nacha’s WEB debit account validation requirement asks originators to validate an account before the first use of new banking information. IntelliPay offers ACH web validation capabilities designed to check new consumer and business account data before the first transaction is submitted. Ask which validation methods, authorization-record features, reporting tools, and compliance-support functions are included in your specific IntelliPay configuration.
Compliance note: Rule applicability depends on your organization’s role in the ACH Network, your transaction volume, and your agreement with your sponsoring financial institution. Confirm your obligations with your bank, processor, and counsel rather than relying on a general summary.
Security, returns, and payment risk
Moving away from paper checks can reduce exposure to physical check theft, alteration, and mail-related fraud, a category the American Bankers Association Deposit Account Fraud Survey has repeatedly identified as a leading source of deposit-account losses. Electronic debits bring a different set of risks: incorrect bank-account information, insufficient funds, duplicate entries, unauthorized claims, and payment instructions altered through fraud.
A sound eCheck program protects bank-account data, restricts staff access, reviews unusual activity, and gives employees a documented way to handle exceptions. Verification and screening tools can reduce avoidable failures, but they cannot guarantee that funds will be available or that every debit will settle without a return.
- Keep authorization records, payment confirmations, and customer communications organized and easy to retrieve
- Use a payment descriptor customers can recognize on their bank statement
- Review return reasons for recurring patterns involving data quality, customer confusion, or potential fraud. Nacha applies an unauthorized-return-rate threshold in the range of 0.5%, and exceeding an applicable threshold can prompt a compliance review, so monitor return codes as both a compliance duty and an early warning signal
- Set a documented policy for retries, alternative payment requests, refunds, and dispute escalation
- Independently verify every request to change vendor or customer banking details, especially when the request arrives by email
Also ask your bank and processor about controls for your own outgoing ACH activity, such as ACH positive pay, ACH debit blocks, and dual authorization for larger payment batches. These measures address a separate risk: unauthorized or fraudulent withdrawals from your organization’s operating accounts.
Ways to accept eChecks
The right setup depends on where customers pay and where payment data needs to go afterward. Some organizations need a payment link; others need a customer portal, a virtual terminal, or an integration with billing and accounting systems.
Hosted payment pages
A branded online page lets customers pay without your organization building a bank-account-entry form from scratch. It works well for invoice links, account balances, utility bills, dues, permits, and one-time payments.
Virtual terminal
Authorized staff enter payment details through a secure browser-based screen. This can support phone payments, assisted payments, and valid mailed authorizations, but it requires deliberate access controls and staff training because employees are handling sensitive payment information.
Customer portal or billing system
A portal can support recurring payments, payment history, receipts, saved preferences, and account management. It is often a strong fit for utilities, government agencies, property managers, schools, membership organizations, and other billers with ongoing customer accounts.
API or custom integration
Complex workflows may connect eCheck acceptance to an ERP, billing platform, accounting system, or CRM. Before committing, establish whether the connection is native, partner-built, or custom; who supports it after launch; and how payment status, settlement records, returns, and refunds will remain synchronized.
Choosing an eCheck processing provider
The lowest advertised rate is not automatically the lowest total cost. Look for a provider that fits the channels your customers use, the authorization process your program requires, the funding schedule you can accommodate, and the way your staff reconciles payments day to day.
Provider review checklist
- Payment channels: Can customers pay online, through an invoice link, by phone, in a portal, or with staff assistance?
- Funding: What is the standard funding schedule, and what circumstances can delay it or trigger a reserve?
- Authorization support: Does the platform support the authorization methods and recordkeeping your use case requires?
- Risk controls: Which account-validation, monitoring, and return-management features are included?
- Validation and rule changes: Does the platform verify new bank-account data before the first debit, and how are Nacha rule updates absorbed without a project on your end?
- Reporting: Can staff reconcile transactions, deposits, returns, and exceptions without manual workarounds?
- Integration: Is the connection native, prebuilt, or custom, and who owns ongoing support?
- Support: Who handles onboarding, technical issues, and day-to-day account questions?
- Payment stack: Can cards, eChecks, and digital wallets be managed and reconciled in one environment, or will your team be stitching separate systems together each month?
Getting started with eCheck processing
Begin with your payment workflow, not the technology. Identify what customers are paying for, how often they pay, the payment channels they expect, and where transaction data must land after a payment is made.
- Identify the use case: one-time invoices, recurring billing, account payments, phone payments, or self-service online payments.
- Document your payment profile: average payment amount, monthly volume, customer type, payment channels, return history, and seasonal patterns.
- Map the customer experience from authorization and confirmation through receipts, customer support, cancellation, and recurring-payment management.
- Confirm authorization, recordkeeping, and compliance requirements with your provider and appropriate legal or compliance advisors.
- Plan reconciliation: decide how transactions, deposits, returns, and refunds will appear in the billing or accounting system.
- Test before launch. Run routine payments and exception scenarios, then monitor return patterns, funding, and staff workload after go-live.
A note on dual pricing and fee recovery
If card fees are the main reason you are evaluating ACH, fee-recovery approaches may also be worth reviewing. Depending on your business type, jurisdiction, and card-brand requirements, programs such as dual pricing, service fees, and convenience fees may disclose and allocate some or all of the card-acceptance cost to the customer who chooses to pay by card. ACH can remain the lower-cost pay-by-bank option.
These programs must be designed and administered carefully. Disclosure, calculation, transaction flow, and applicable network rules matter. IntelliPay can apply certain fee logic at the gateway, but organizations should confirm the program structure and their obligations with the processor and qualified legal or compliance advisors before implementation.
Frequently asked questions
Are eChecks less expensive than credit cards?
Often, particularly as transaction amounts increase. ACH pricing is frequently flat, capped, or negotiated, while card costs are usually percentage-based. Compare the total cost of acceptance, including return fees, verification tools, platform fees, funding terms, integration costs, and staff reconciliation time.
Can an eCheck be returned?
Yes. Common return reasons include insufficient funds, a closed account, invalid bank-account information, duplicate entries, and customer disputes or unauthorized claims. Maintain authorization records and give staff a defined process for reviewing and resolving returns.
Do eChecks settle immediately?
No. Settlement and funding depend on the transaction type, financial institutions involved, processing cutoffs, weekends and holidays, risk controls, and your provider’s funding policy. Same Day ACH can accelerate eligible payments, but it is a separate service and may not be available for every eCheck program.
Do customers need to authorize eCheck payments?
Yes. The authorization requirements depend on whether the payment is one-time or recurring and whether the customer authorizes it online, by phone, in writing, or through another permitted method. Your processor can help identify the appropriate workflow, but your organization should retain the needed records.
Can eChecks be used for recurring payments?
Yes, when the recurring authorization, payment schedule, customer notices, and cancellation process are set up correctly. Make the terms clear before enrollment and provide customers with a workable way to manage or cancel future debits.
The bottom line
Electronic check processing gives organizations a practical, lower-cost pay-by-bank option for invoices, recurring payments, and account-based billing.
The programs that hold up over time combine clear customer authorization, realistic settlement expectations, disciplined return handling, sensible fraud controls, and reporting that staff can reconcile without unnecessary workarounds.
To review ACH, eCheck, card, and payment acceptance options for your organization, visit IntelliPay Government.
Sources and further reading
- Nacha, Credit-Push Fraud Monitoring Resource Center.
- Nacha, Supplementing Fraud Detection Standards for WEB Debits.
- Nacha, Account Validation Resource Center.
- Nacha, ACH Network Risk and Enforcement Topics.
- Nacha, Same Day ACH.
- Consumer Financial Protection Bureau, Regulation E § 1005.11, Procedures for Resolving Errors.
- American Bankers Association, Deposit Account Fraud Survey Report.
- IntelliPay, Why ACH Is Right for Your Business.
Disclaimer: This content is provided for general informational purposes only and does not constitute legal, accounting, banking, regulatory, tax, or compliance advice. ACH rules, authorization requirements, provider terms, settlement schedules, return rights, return thresholds, fraud-monitoring obligations, data-security requirements, and fee-recovery rules vary by transaction type, financial institution, processor, industry, and jurisdiction, and they change over time. Pricing figures, settlement timeframes, return windows, regulatory dates, and cost comparisons appearing in this guide are illustrative examples drawn from publicly available sources as of the date of publication. They are not quoted pricing, a service-level commitment, or a guarantee of processing, settlement, or funding times, and they may not reflect current rules or the terms of any specific IntelliPay configuration. Product capabilities described here depend on your account setup, underwriting, sponsoring financial institution, and applicable agreements. Verify all current requirements and confirm your program with your payment processor, financial institution, and qualified legal, accounting, or compliance advisors before implementation or material changes. IntelliPay assumes no liability for actions taken in reliance on this content.
