What does a valid result mean?
Checksum valid means the digits satisfy the ABA checksum. Observed means a matching source record was available. An unknown checksum-valid number is not automatically invalid, active or usable.
Free US bank data for payment testing
US Bank Account & Routing Number GeneratorRandom test datafor payment QA
Generate up to 10 random checksum-valid routing numbers and synthetic account numbers free. Choose a bank for reviewed, source-backed targeting with Pro or Business.
Free synthetic generation ABA checksum checks Paid bank targeting
No signup for free generation. Synthetic examples are not verified bank accounts.
synthetic-us-data.json
051000017Bank of AmericaAch Checksum
021000021ChaseDomestic Wire Checksum
121000248Wells FargoDomestic Wire Checksum
Bank-targeted examples · source-backed routing references
ABA9-digit routing format
Freeup to 10 rows per run
AIsynthetic test profiles
4,219FDIC banks in active snapshot
4,299NCUA credit unions in snapshot
8,496primary ABA references for QA
9,756distinct routing numbers in registry
Browse the US banks in our bank directory · Source dates and coverage. Logos identify referenced institutions; no affiliation implied.
Generated dataset
No rows yetNeed an exact bank?
Choose a bank to see available routing instructions and the cost for your batch.
Use through the APITest assertions and source details — first 3 rows
Saving uses no additional credits. A new run shows its cost before using credits.
Saved US bank QA sets
Reuse a bank, routing instruction, quantity and seed. Review the current source and credit quote before every new run.
Sign in with Pro or Business to save and reuse targeted sets.
Open standalone US Routing Validator
Check ABA routing numbers
US Routing Validator
Validate routing numbers for QA, staging and payment-form testing. Check the nine-digit ABA checksum, then review available ACH, wire, FedNow and bank-published observations separately.
9-digit format
ABA 3-7-1 checksum
Source-scoped evidence
Free preview checks up to 3 routing numbers. No signup required.
Validation results
ReadyChecksum validation is free. To unlock available bank metadata or check more rows, review the full-list quote. Existing Pro or Business access is reused; payment issues go to account recovery. Upgrading does not add missing source coverage.
US routing number validator and ABA checksum checker
This online routing number checker validates the nine-digit format and ABA 3-7-1 checksum used by US routing transit numbers. It then reports available directory or bank-published observations without confusing checksum validity with assignment to a bank.
Need random test values?
Use the US routing number generator for fresh synthetic routing and account data. Free generation is generic; reviewed bank targeting is paid when available.
ABA, ACH and wire routing number checks
An ABA routing number identifies a US financial-institution routing endpoint, but the appropriate number can depend on payment type and region. ACH, domestic wire, check and FedNow observations are shown independently when a source supports them. Confirm production payment instructions with the bank or an authorized routing directory.
- Validate one routing number or preview three rows free.
- Check bulk payroll, ERP or payment-integration lists with an exact credit quote.
- Download JSON reports and save comparison baselines when access allows.
- Review routing data coverage and source dates before relying on an observation.
Routing number vs account number: which value should I check?
A routing number has nine digits and identifies the bank routing destination. An account number identifies an account within that institution and has a bank-specific format. Enter only the routing number in this checker; keep leading zeros. Passing the ABA checksum does not validate the accompanying account number.
Routing number validation is not bank-account validation
This tool does not verify account existence, ownership, balance or payment acceptance. It also does not replace the additional account-validation controls that may apply to a live payment workflow. Do not paste customer account numbers or personal data into the routing list.
Need a test routing number for Stripe ACH?
Stripe documents 110000000 for its manually entered ACH sandbox accounts. Use the documented account number or token for the payment outcome you want. The Stripe ACH test account guide includes success and failure examples plus an offline webhook QA Pack; these are not live payment instructions.
Validate routing and account columns together
For supplier or ERP spreadsheets, use the US routing and account CSV validator. It flags ABA checksum errors, missing values, duplicate pairs and Excel damage without claiming account ownership or ACH-file certification.
US routing number resources
USA bank testing tools · US bank and credit-union directory · bank-published routing instructions · US ACH test fixtures · server-side API documentation
Saved routing lists and comparisons
Load a saved list, check it again, then save the new report to compare source observations. Identical source data is not presented as a new banking event.
Fake routing number generator for US testing
Free web generation samples routing numbers from dated bank references and pairs them with synthetic US account numbers. Bank names are locked until you confirm a metadata-credit reveal; selecting a specific bank requires Pro. These are QA fixtures, not real customer accounts. Primary ABA references do not establish ACH or Fedwire eligibility. The API also retains checksum-only synthetic generation.
How do I generate a dummy bank account number?
For a dummy bank account number or random account-number example, generate a row above and copy its Account Number field. The accompanying Routing Number is a separate nine-digit field. Keep both as strings in your test code so leading zeros are preserved. Generated account values are for form and software tests and do not open or identify an account.
Can I use fake bank account numbers in an ACH sandbox?
Use the payment provider's documented sandbox values when testing payment outcomes. Random account numbers and checksum-valid routing numbers do not guarantee sandbox acceptance. For Stripe ACH, review our source-linked US ACH test scenarios; those documented sandbox values are separate from the random generator above.
How do I check a generated routing number?
Paste it into the ABA routing number validator. A passing checksum checks the nine-digit number's structure. Available directory observations are reported separately; an unknown match is not proof that the number is invalid.
US routing number API
Use your existing API key for generation, bank targeting, routing checks and synthetic profiles. Paid targeting uses the same bank metadata quota as the website, with a quote before execution and safe request retries. See US API examples and credit costs.
Which test routing number works with Stripe ACH?
Stripe documents 110000000 for its manually entered ACH sandbox test accounts. Pair it with the documented account number or token for success or failure; do not substitute a random generated account. See the Stripe ACH test account numbers and webhook QA guide for source-linked examples and the offline QA Pack.
Bank targeting, not a bank-account lookup
A targeted batch keeps the selected routing number fixed. A bank may publish different numbers for ACH, paper and wire, and for where an account was opened. We keep those distinctions; a wire instruction is not silently substituted for ACH.
All account numbers are synthetic generic 12-digit test values, not verified bank-specific formats. Generated values may coincidentally match real records. Never use them for live payments, identity verification or accessing accounts.
Checksum-valid synthetic generation stays free. Exact bank targeting requires Pro and uses one existing bank metadata credit per generated row; Business raises the per-request limit from 150 to 750. Full AI profiles use one profile credit and downloads use one export credit—the same quota economy as the IBAN workflow. Every paid action shows its exact cost before it runs.
Existing plans · Validate routing numbers and compare saved lists · Coverage and source dates
Bank routing sources for targeted test data
Search Advanced options for banks and credit unions. Bank-published instructions preserve their payment use and region. Primary ABA references link a routing number to an institution on the stated source date; they do not confirm ACH or Fedwire eligibility.
Primary ABA references are available for dated QA fixtures for up to 180 days from the source date. A new download does not reset that date. Review coverage and source dates before using a target.
- Ally Bank — bank-published routing instructions
- Bank of America — bank-published routing instructions
- Chase — bank-published routing instructions
- Wells Fargo — bank-published routing instructions
Regulatory reference subset adapted from Nelson Anievas / fi-lookup-mcp, using FFIEC NIC, FDIC and NCUA sources, under CC BY 4.0. We normalize primary ABA values and exclude inferred website signals.
Checking a supplier CSV instead?
Use the US payment CSV audit to find missing routing/account fields, ABA checksum errors, duplicate pairs and spreadsheet damage. Try a free five-row structure preview before ordering a full-file report. Supplier files are not sent to AI providers.
What does “valid” mean here?
It means the ABA checksum and our generic account-field shape pass the stated test assertions. It does not mean ACH/Fedwire membership, sandbox acceptance or an existing account. These are bank-field fixtures, not executable NACHA or wire-transfer files.
Can I repeat the same test data?
Yes: use the same mode, exact target, quantity and seed with the same generator version. Source changes require a refreshed selection. Paid retries with the same request key do not debit twice; making a new paid generation is a new task.