All The Validators logoAll The Validators

data validator

Routing Number Validator

Validate US routing numbers (ABA) with checksum math locally to catch typos before payouts.

Results

Processing…
Status
Processing...
Details
Processing...

How to use this validator

  1. Paste or type the 9-digit routing number.
  2. Run validate to compute the ABA checksum.
  3. If invalid, check for missing or transposed digits and re-validate.

Rules & checks

Strips non-digits before validation.

Runs the ABA checksum (weighted sum mod 10) to detect transposed/missing digits.

Client-side/offline—routing numbers are not sent or stored.

Inputs explained

  • Routing number

    Enter 9 digits (US ABA). We strip spaces/dashes automatically. Use test/staging data when possible.

When to use it

  • Pre-validate routing numbers in onboarding or payout flows
  • Clean CSV imports before sending to payment processors
  • QA banking details in support workflows

Common errors

  • Missing or extra digits
  • Transposed adjacent digits
  • Non-digit characters copied from forms

Limitations

  • Format/checksum only; no account ownership or bank status verification.
  • US ABA routing only; international formats require IBAN/SWIFT validators.
  • No bank metadata lookup (e.g., name/address).

Tips

  • Collect routing numbers as digits only; strip formatting before validation.
  • Even if checksum passes, still rely on your PSP/bank for ownership and status checks.
  • Keep production bank data out of local tools; use staging/test data when possible.

Examples

Valid routing

  • 011000015 -> Valid (checksum passes)

Invalid checksum

  • 011000016 -> Invalid (checksum fails)

Invalid length

  • 12345678 -> Invalid (needs 9 digits)

Deep dive

This routing number validator applies the ABA checksum locally to catch typos in 9-digit US routing numbers before payouts.

Use it to clean onboarding forms and imports, then rely on your payment provider for ownership and live status checks.

FAQs

Is my routing number uploaded or stored?
No. Validation runs in your browser only and clears on refresh.
Do you verify account ownership or bank status?
No. This is checksum/format only. Use your PSP/bank for full verification.
Do you support non-US formats?
This tool is for US ABA routing numbers. Use IBAN or SWIFT validators for international routes.

Related validators

data

IBAN Validator

Validate IBAN structure and checksum locally to catch typos before payouts—no data leaves your browser.

security

Credit Card Validator

Run a local Luhn check to confirm card number format before hitting payment APIs—no data leaves your browser.

security

API Key & Token Validator

Check common API key/token formats (Stripe, GitHub, AWS, OpenAI, etc.) locally.

security

JWT Signature Validator (HS256)

Validate HS256 JWT signatures with a shared secret, fully client-side—no tokens or secrets ever leave your browser.

Routing numbers are processed only in your browser. Nothing is sent, logged, or stored.

Checksum/format validation only; does not verify ownership or bank status.