← IBANgen

US routing number checker

Check the nine-digit checksum and available registry observations.

Coverage is source-specific and incomplete. Unknown does not mean invalid. A listed routing number does not establish account existence, ownership or payment acceptance.

Review your routing list. Keep evidence. Test the result.

For developers maintaining payroll, ERP and payment integrations: find input errors, review source observations, save a baseline and compare your next check.

US beta: try three rows before upgrading. Payment does not unlock missing bank names or unloaded ACH/Fedwire sources. Source coverage is included in each report.

Pro supports 50 rows per run; Business supports 250. Both include saved reports and manual comparison. Generated accounts use a generic synthetic format, not bank-specific account rules.

Pro list workflow · Business volume · API documentation

GET /api/v1/us/routing/021000021
X-API-Key: YOUR_SERVER_SIDE_API_KEY

One API credit per lookup. Free API evaluation uses your existing allowance. All US plans include basic observations, source and date; Business includes full provenance.

Check a routing-number list

Pro: up to 50 rows. Business: up to 250. Paste routing numbers only, one per line — no account or customer data.

Cost: one API credit per unique valid RTN, plus three per valid row if test cases are selected. Invalid rows cost zero. JSON download is included.

Rechecking an unchanged saved list against identical source data is free when test generation is off.

When you open checkout, a routing-number-only draft stays in this tab for your return. Restoring it never starts a paid check automatically.






Saved lists and comparisons
Load a list, run another check, then save it to compare. The same source file is not a new banking event. Comparisons are manual; no automatic bank alerts are sent.