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.
Generate synthetic US routing and account numbers, check ABA checksums and build test profiles in one workspace. US accounts use routing numbers instead of domestic IBANs.
No signup for free generation. Synthetic examples are not verified bank accounts.
Bank-targeted examples · source-backed routing references
Browse the US banks in our bank directory · Source dates and coverage. Logos identify referenced institutions; no affiliation implied.
Choose a bank to see available routing instructions and the cost for your batch.
Use through the APIReuse 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
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.
Free preview checks up to 3 routing numbers. No signup required.
Checksum 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.
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.
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.
Use the US routing number generator for fresh synthetic routing and account data. Free generation is generic; reviewed bank targeting is paid when available.
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.
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.
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.
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.
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.
USA bank testing tools · US bank and credit-union directory · bank-published routing instructions · US ACH test fixtures · server-side API documentation
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.
No. Domestic US bank payments normally use an ABA routing number and an account number instead of an IBAN.
No. Free web generation samples dated bank routing references and creates synthetic account numbers. It does not establish account existence or payment-rail eligibility.
It checks the nine-digit format and ABA checksum, then reports available source observations separately. A checksum-valid result is not account validation.
Yes, when reviewed targeting coverage is available. Bank targeting uses paid Pro or Business access and reports the source scope and limitations.
US bank fields pair a nine-digit ABA routing number with an account number. Use the random routing number generator to create synthetic test data, or the routing number checker to check an existing test value. The generator also supplies fake US account numbers for form tests and staging datasets.
The United States does not use domestic IBANs. An American IBAN generator cannot supply a US IBAN; use routing and account fields for US tests, and our IBAN generator for countries that use IBAN.
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.
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.
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
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.
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.
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.
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.
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.