🇺🇸 US test data · bank targeting
US routing number generator
Generate checksum-valid synthetic routing numbers, or keep a bank's published routing instruction fixed while generating synthetic account fields for your tests.
Generated dataset
No rows yetNeed an exact bank?
Pro fixes a reviewed bank routing instruction for up to 150 rows. Business supports up to 750.
Test assertions and source details — first 3 rows
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
ReadyYour preview is free. To check more rows, run 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.
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.
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 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.
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.
US routing number FAQ
Does the United States use IBAN numbers?
No. Domestic US bank payments normally use an ABA routing number and an account number instead of an IBAN.
Are generated routing and account numbers real bank accounts?
No. Free generation creates checksum-valid synthetic test data. It does not prove assignment to a bank or the existence of an account.
What does the US routing number validator check?
It checks the nine-digit format and ABA checksum, then reports available source observations separately. A checksum-valid result is not account validation.
Can I generate test data for a specific US bank?
Yes, when reviewed targeting coverage is available. Bank targeting uses paid Pro or Business access and reports the source scope and limitations.
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
Available bank instructions
Only reviewed, loaded and fresh sources are selectable. We do not infer routing numbers from the FDIC/NCUA institution name directory.
- Ally Bank — 1 published use/region combinations
- Bank of America — 168 published use/region combinations
- Chase — 1 published use/region combinations
- Wells Fargo — 1 published use/region combinations
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.