Nacha Account Validation: What the WEB Debit Rule Requires
Nacha Account Validation: What the WEB Debit Rule Requires

Nacha account validation means checking that a consumer’s bank account is legitimate, open and able to accept ACH entries before you debit it online. If you originate WEB debits, the rule has applied to you since March 19, 2021. You validate the account number before first use and again before you use a changed one.
This guide explains the rule in plain terms, lists the methods that meet it, and shows how to fit validation into an ACH program. It also covers where ownership checks fit and what to document.
TL;DR
- Originators of WEB debits must validate a consumer account number before first use and before any change to it, as part of a commercially reasonable fraud detection system.
- The minimum test is whether the account is open and can accept ACH entries. Proof of ownership is an additional, risk-based control.
- Nacha does not pick one method. Prenotes, micro-entries, third-party validation services and API-based checks can all qualify.
- Validation cuts returns and fraud, so it protects your cash flow as well as your compliance record.
- Our ACH and eCheck processing starts with a Gateway + eCheck plan at $25 per month.
Table of Contents
- What Nacha account validation actually means
- Who has to validate, and when
- Does ACH require verification?
- Methods that meet the rule
- Build a validation routine step by step
- Timing: does validation have to be real time?
- Why validation pays off beyond compliance
- How to document compliance
- Our approach to ACH for small businesses
- Ownership checks and fraud: going beyond the minimum
- Quick checklist before you go live
- Ready to set up ACH?
- FAQ
- Sources
What Nacha account validation actually means
Nacha describes validation as using a commercially reasonable method to determine that the account is legitimate, open and able to accept ACH entries at the receiving bank. That language comes from Nacha’s rule page on supplementing fraud detection standards for WEB debits.
The phrase “commercially reasonable” matters. Nacha sets a standard, not a product. You choose a method that fits your volume, your customers and your risk.
Validation is not the same as format checking
A format check confirms that a routing number has nine digits and passes its checksum. It also confirms that an account number is the right length. That catches typos, but it cannot tell you whether the account exists or accepts ACH.
Validation goes further. It asks the banking system, directly or through a data source, whether the account is real and open. A number can look perfect and still belong to a closed account.
Validity and ownership are two different questions
Nacha’s account validation FAQ draws a clear line. The rule’s minimum is whether the account is open and can accept ACH entries. Ownership checks may be added where your business model and risk profile call for them.

That means a consumer who types someone else’s valid account number can pass a basic validity check. If your business is exposed to that kind of fraud, a stronger ownership check may be the commercially reasonable choice.
Who has to validate, and when
The mandate applies to Originators of WEB debit entries. They must validate account numbers before first use and before using a changed account number, according to Nacha’s rule summary.
The rule is prospective. It covers accounts you add or change going forward, not a retroactive sweep of every account already on file.
What counts as a WEB debit
A WEB debit is a consumer debit payment authorized or initiated over an online channel, as described in Nacha’s Account Validation Resource Center. Typical examples:
- A customer enters bank details on your checkout page to pay an invoice.
- A patient sets up an online payment plan with a bank account.
- A member enrolls in recurring dues through a web form.
- A client pays a retainer through a payment link.
If you collect bank details through a website, app or online form and then debit a consumer’s account, you are in WEB debit territory.
What the rule does not say
The rule makes validation a minimum part of your fraud detection system. It does not say every ACH entry of every type needs the same check. Nacha’s materials also treat validation as useful well beyond WEB debits, which we cover below.
Does ACH require verification?
For WEB debits, yes: validation is an explicit requirement. For other ACH entries, validation is not mandated by that rule, but Nacha encourages it. Its white paper, Account Validation: A Tool for Businesses to Improve ACH, describes it as a way to reduce returned transactions and fraudulent payments.
In August 2026, Nacha published a perspective on why account validation deserves a broader role in ACH risk management. It ties validation to account takeover and unauthorized-transaction risk across ACH payments generally.
For a business owner, the practical reading is simple. Build validation into every online bank-account enrollment, whatever the payment type.
Methods that meet the rule
Nacha is method-neutral. According to its rule guidance, acceptable examples include:
- A prenotification entry
- ACH micro-entries
- A commercially available validation service from your bank or a third party
- API-enabled validation
Each has a different speed, cost and level of assurance.
| Method | What it confirms | Speed | Where it fits |
|---|---|---|---|
| Prenotification | Account is open and can accept ACH, once the return or NOC window passes without a response | Slowest, tied to the return window | Low-volume, low-risk enrollments |
| Micro-entries | Open account, plus the customer confirms small amounts, which suggests access to the account | Short delay while the customer confirms | Recurring billing and higher-risk enrollments |
| Validation service or API | Account status from banking data, sometimes ownership | Near real time | Online checkout and high-volume flows |
Prenotes
A prenote is a zero-dollar entry sent before live debits. It can satisfy the minimum open-and-ACH-capable test when the applicable return or Notification of Change period passes without a response, per Nacha’s guidance.
One warning keeps you out of trouble. A prenote does not establish that the account belongs to the named person, a point made in a corporate user ACH origination guide. Never describe a clean prenote as ownership verification in your policies or customer messages.
Micro-entries
Nacha defines micro-entries as ACH credits of less than $1 plus any offsetting debits, used to verify a Receiver’s account. The Nacha micro-entries rule page also standardizes the company name and entry description, so customers recognize them on their statements.
For the rule’s purposes, the process must be completed before live entries begin. That includes correct confirmation by the customer of the amounts sent.
Validation services and APIs
These check account data at the point of entry. They suit online checkout because the customer gets an answer in seconds rather than days. The trade-off is a per-check cost, and the right provider depends on your volume and risk.
Build a validation routine step by step
Here is a routine you can document and defend. Nacha does not prescribe it, but it follows the rule’s logic.
- Map every place bank details enter your business. Include checkout pages, payment links, patient portals, member sign-ups and phone-to-web handoffs. Each one is a WEB debit entry point if a consumer account is debited.
- Decide your trigger points. The rule requires validation before first use and before a changed account number is used. Add a check whenever a customer edits routing or account details.
- Choose a method per entry point. A quick online checkout may need real-time validation. A slower enrollment can use micro-entries.
- Set a risk tier. Higher-ticket payments, new customers and unusual patterns call for a stronger check, such as an ownership verification layer.
- Define the failure path. Decide what happens when validation fails: ask for a different account, request a card, or route to manual review.
- Record the outcome. Keep the date, method and result for each account. Your written fraud detection policy should say how long you retain records.
- Review the system on a schedule. Check return rates, fraud losses and validation failures every quarter. Adjust the method if returns climb.
Where it goes wrong
Three mistakes show up repeatedly in ACH programs:
- Validating only new accounts. A changed account number triggers the rule again.
- Treating a format check as validation. It catches typos only.
- Calling a prenote proof of ownership. It confirms the account accepts ACH, not who owns it.
Timing: does validation have to be real time?
No. Nacha’s white paper says validation can occur at enrollment, before the first transaction or periodically before payment. Same-day or next-day processing may be preferable operationally, but the rule does not demand instant results.
So pick the timing that suits your flow. A subscription business can validate when the customer enrolls. A service business that bills after the visit can validate at intake.
Why validation pays off beyond compliance
A returned ACH debit costs time, and it often costs a fee. Our published ACH schedule lists a $15 return fee, a $25 reject fee, a $15 Notification of Change fee and a $25 unauthorized return fee. You can see them on our ACH and eCheck page.
Every bad account number you catch before the first debit is one less return to absorb. It also means one less customer chasing a failed payment and one less gap in your receivables.
If you are weighing ACH against cards, our guide on saving money on processing fees by offering ACH payments explains the cost side. Validation is what keeps that savings from leaking away in returns.

Industries where it matters most
Validation earns its keep wherever recurring or high-value debits are common:
- Healthcare and dental practices with payment plans
- Gyms, studios and clubs with monthly dues
- Contractors, HVAC and plumbing firms collecting deposits
- Lawyers and accountants billing retainers
- Online merchants in specialty and high-risk categories
How to document compliance
Nacha enforces its rules through a formal compliance framework. Its ACH Rules Compliance overview outlines how possible violations are evaluated and how rules are enforced. Your best protection is a clear paper trail.
Keep these items on file:
- A written fraud detection policy that names your validation method for each entry point
- Records of the validation result for each account, with the date
- A log of account changes and the re-validation that followed
- Your review notes on returns and fraud losses
If you are unsure whether your system meets the standard for your business, ask your bank or a compliance attorney. The rule’s “commercially reasonable” test turns on your own facts.
Our approach to ACH for small businesses
Our ACH and eCheck processing page lists a Gateway + eCheck plan at $25 per month. It also lists the one-off ACH fees noted above. You see the schedule before you sign.
Each business gets an assigned account manager. That gives you one person to talk to about how bank-account payments fit your operation, from onboarding through daily use.
If you also take cards, we can set up in-person and online payments alongside ACH. Our payment processing resources cover the wider picture, and our ACH processing solutions page shows how bank payments sit next to cards.
Perspective
We talk with owners every week who treat ACH as the cheap, simple option and then get surprised by returns. The surprise is rarely the rail itself. It is the gap between collecting bank details and knowing the account is usable.
Our view is that validation belongs at enrollment, not after the first failed debit. Build it into the form, record the result, and re-run it whenever a customer changes their details.
We also think owners should pair that routine with a payment setup that is clear about cost. That is why we publish our ACH fee schedule and assign an account manager to every merchant. A rule like the WEB debit requirement is easier to meet when your processor relationship is transparent and someone knows your business.
Jonathan
Ownership checks and fraud: going beyond the minimum
The rule’s minimum does not require proof that the consumer owns the account. Whether a stronger check is commercially reasonable depends on your business model and risk profile, per Nacha’s FAQ.
Consider an ownership layer when:
- Ticket sizes are high
- You pay out or refund to bank accounts
- You see repeated disputes or unauthorized returns
- Customers are new and you have no history with them
A tiered approach keeps friction low. Low-risk customers get the fast check. Higher-risk ones get the stronger one.
Quick checklist before you go live
- Every online bank-account entry point is mapped.
- Validation runs before first use and after any account change.
- Your method is documented per entry point.
- Failures have a defined next step.
- Results are logged with dates.
- Return and fraud numbers are reviewed on a schedule.
Ready to set up ACH?
If you collect bank payments online and want a clear fee schedule, start with our Gateway + eCheck plan at $25 per month. Pair it with card acceptance through our payment processing services if your customers want both options.
FAQ
What is the meaning of account validation?
Account validation is a check that a bank account is legitimate, open and able to accept ACH entries. Nacha frames it as a commercially reasonable method that a business chooses. It is different from a simple format check on the routing and account numbers.
What are the Nacha requirements for WEB debits?
Originators of WEB debits must include account validation in their commercially reasonable fraudulent-transaction detection system. They validate before first use of a consumer account number and before using a changed one. The requirement took effect on March 19, 2021, and applies going forward.
Does ACH require verification?
For WEB debits, validation is required by the rule. For other ACH payments there is no identical mandate, but Nacha recommends validation as a risk-management tool. Many businesses apply it to every online enrollment for consistency.
Can I verify a bank account number?
Yes. You can use a prenotification, micro-entries, a bank or third-party validation service, or an API-based check. These confirm that the account is open and can accept ACH. Confirming that the person owns the account takes an added ownership check.
Does validation have to happen in real time?
No. Nacha’s materials say it can happen at enrollment, before the first transaction or periodically before payment. Faster is often better for the customer experience, but the rule does not require instant results.
Sources
- Nacha: Supplementing Fraud Detection Standards for WEB Debits
- Nacha: Account Validation Frequently Asked Questions
- Nacha: Account Validation Resource Center
- Nacha: Account Validation, a Tool for Businesses to Improve ACH
- Nacha: Beyond WEB Debits, Why Account Validation Deserves a Broader Role
- Nacha: Micro-Entries (Phase 1)
- Corporate User ACH Origination Electronic Guide
Recommended
This article provides general educational information and does not constitute legal or regulatory advice. Laws, card-network rules, and processor requirements may change. Businesses should verify the requirements that apply to their location, industry, processor, and payment program before implementing any payment or pricing practice.