Bank Account Verification
Bank account verification before every ACH payment.
Real-time bank account validation and balance checks before you pull money. Catch typos, closed accounts, fake accounts, and accounts that can't cover the payment before they turn into returns.
Verification result
Account ending ••4421
Checking account
routing •••••0000
Signals checked
Account exists
Routing + account number valid
Account is open
Active and in good standing
Owner match
Customer is an authorized signer
Balance check
Covers this payment (with Plaid)
Payment history
Positive history, no recent NSF or returns
First time WEB rule
Checked before the first online debit
How ACH account verification works
Bank account verification, also called bank account validation, confirms an account is real, open, and belongs to your customer before you pull money from it. Every check runs before the debit goes out, so a bad account never becomes a returned payment and a return fee.
Account status in real time
Confirm the routing and account number are valid and the account is open, active, and in good standing before the payment leaves your system. Catches typos and closed accounts at submission, with nothing for your customer to do.
Balance check and NSF risk
Link accounts with Plaid and check the available balance before you pull, so the payment clears the first time. Every account also gets a payment history check that flags insufficient funds (NSF) status, recent returns, outstanding items, and known bad check writers before you send the debit.
Best case shown. Balance checks require linking accounts through Plaid with Plaid Balance on your own Plaid account.
Account owner match
Confirm your customer is an authorized signer on the account. Fuzzy matching handles nicknames and typos. Add address, phone, tax ID, or date of birth for a tighter match.
Automatic verification rules
Check every new account without writing extra code. Verify the first time an account is used for an online (WEB) payment, the first time it is used for any payment, or on every payment for higher-risk business.
Bring your own Plaid or MX token
Already link bank accounts with Plaid or MX? Pass the processor token to ACHQ and we use it to send the ACH. No second integration on your side and no duplicate Plaid charges.
How bank account verification lowers ACH returns
Verifying before you pull cuts NSF returns by up to 70%. Most returns trace back to an account problem you could have caught first. Here is which check stops which ACH return code.
Closed and invalid accounts
Account status confirms the numbers are valid and the account exists and is open before the first pull.
Insufficient funds
Check the balance before you pull with Plaid, and payment history flags accounts in NSF status or with recent returns, so the payment doesn't bounce.
Unauthorized payments
Owner match confirms your customer is an authorized signer on the account they gave you.
Accounts that can't take debits
Catches accounts that don't allow ACH debits, like some savings, credit card check, and line of credit accounts.
Fewer returns also keeps your business under Nacha's return rate limits.
Best case shown. Balance checks require linking accounts through Plaid with Plaid Balance on your own Plaid account.
Instant verification vs. prenotes and micro-deposits
The old ways to validate a bank account make you, or your customer, wait. Real-time checks answer before the payment is sent.
| Method | How long | Customer effort | Confirms the owner |
|---|---|---|---|
| Prenote | Up to 72 hours | None | No |
| Micro-deposits | Days | Comes back to confirm two small amounts | Indirectly |
| ACHQ account status | Real time | None | No |
| ACHQ account owner match | Real time | None | Yes, authorized signer |
Nacha requires businesses that take online (WEB) debits to validate an account the first time they use it. The ACHQ first time WEB rule runs that check automatically. Look up account validation and other ACH terms in the glossary.
Plaid and MX tokens
Already using Plaid? Send us the token.
If your app already links bank accounts through Plaid or MX, pass the processor token to ACHQ and we use it to send the ACH payment. No second integration and no duplicate Plaid charges. Add Plaid Balance and you can check the available balance before every pull. Plaid pricing, limits, and terms come from your own Plaid account.
No Plaid? You don't need it. ACHQ verification works from the routing and account number alone. Want Plaid anyway? We're a Plaid partner and refer customers directly to Plaid.
ACHQ is a Plaid partner and does not resell Plaid services. Plaid pricing, limits, and terms come directly from Plaid.
Token-based flow
- 1Customer links their bank in your Plaid flow
- 2Plaid issues a processor token and checks the balance
- 3You pass the token to ACHQ
- 4ACHQ sends the ACH against the linked account
Bank account verification FAQ
What is bank account verification?
Bank account verification, also called bank account validation, is checking that a bank account is real, open, and able to take ACH payments before you pull money from it. It catches typos, closed accounts, and fake accounts before they turn into returns.
How do you verify a bank account number for ACH?
Send the routing and account number to the ACHQ account status check and get a real-time answer on whether the account is open, active, and in good standing. No customer action is needed. To also confirm who owns the account, use the account owner match.
How do I check if a routing number is valid?
The ACHQ account check confirms the routing number belongs to a real U.S. bank and that the account number is open at that bank, in one real-time request. A valid routing number alone does not mean the account exists, which is why ACHQ checks both.
Can you verify who owns the bank account?
Yes. The account owner match confirms your customer is an authorized signer on the account. Fuzzy matching handles nicknames and typos, and you can add address, phone, tax ID, or date of birth for a tighter match.
Do I need Plaid to verify bank accounts?
No. ACHQ checks work from the routing and account number alone. If you already link accounts with Plaid or MX in your own app, you can send ACHQ the processor token instead.
Does Nacha require bank account verification?
For online (WEB) debits, yes. Nacha requires a business to validate a bank account the first time it uses it for a WEB debit. The ACHQ first time WEB rule runs that check for you automatically.
What is instant bank account verification?
Instant bank account verification checks an account in real time, while your customer is still on the page, instead of waiting days for a prenote or micro-deposits. ACHQ returns the account status right away, so you know before you send the payment.
Does bank account verification reduce ACH returns?
Yes. Most returns come from an account problem you can catch before the pull: a closed or invalid account, an account in insufficient funds (NSF) status, or a customer who is not on the account. Fewer returns also keeps your return rate under Nacha's limits.
Does bank verification check the account balance?
Yes, when you link accounts with Plaid. The available balance is checked before you pull, so the payment clears the first time. Every account also gets a payment history check that flags insufficient funds (NSF) status, recent returns, and known bad check writers. Balance checks use Plaid Balance on your own Plaid account.
Is instant verification better than micro-deposits?
For most businesses, yes. Micro-deposits take days and make the customer come back to confirm two small amounts. An account status check answers in real time with nothing for the customer to do.
Payments that still come back carry an ACH return code that says why. Building verification into your own software? See the ACH payment gateway and the ACH API.
Move money cheaper, faster, and with fewer headaches.
Apply for an ACH merchant account online. Complete applications often get a decision within hours.