IBAN Validator: Verify & Bulk-Check Bank IBANs logo

IBAN Validator: Verify & Bulk-Check Bank IBANs

by Fred JonesGitHubWebsiteUpdated Jul 23, 2026

IBAN validator for developers & fintech teams — verify checksums, bulk-check SEPA IBANs offline via ISO 13616, no bank API needed.

iban
iban-validation
iban-checker
+7
|

How to pay

Pick whichever fits your workflow — you can switch any time.

Subscribe

Monthly billing

$19/month

Predictable monthly cost with included usage. Best for steady, high-volume traffic.

  • Unlimited tools within plan limits
  • One API key, billed once a month
  • Cancel any time

Pay-per-call

Agent-native

$0.01 per call

Charge agents in USDC the moment they call a tool. No subscriptions, no signup — pay only for what you use.

  • 1 priced tool available
  • Settled in USDC on Base
  • No account or API key required

IBAN Validator: Verify & Bulk-Check Bank IBANs

Validate any IBAN offline against the official ISO 13616 algorithm — the mod-97 checksum plus each country's own length and BBAN structure — and get back a clear, typed reason the moment one fails. No bank API, no data ever leaves the request.

What it does

Every IBAN encodes a country-specific length and structure, plus a 2-digit checksum computed from the rest of the number. This tool checks both, entirely offline and instantly, against a bundled public reference table covering ~76 countries.

Who it's for

  • Finance and ops teams cleaning a payment or supplier IBAN list before a payment run.
  • Payment platforms validating an account before a payout.
  • Onboarding / KYB teams checking a counterparty's bank details as part of know-your-business checks.
  • Developers and AI agents who need an IBAN check as one step in a larger workflow.

Tools

  1. validate_iban — Validates one IBAN against the ISO 13616 checksum and its country's BBAN structure. Example input: iban = GB29NWBK60161331926819
  2. bulk_check_iban — Validates up to 1,000 IBANs in one call, returning one typed result per IBAN plus a summary.

Every result carries a status — VALID, INVALID_CHECKSUM, INVALID_STRUCTURE, INVALID_LENGTH, INVALID_COUNTRY, or INVALID_INPUT — so you know exactly what's wrong, never just that something failed.

FAQ

Is this IBAN valid? Call validate_iban. valid: true (status: "VALID") means it passed every check: recognized country, correct length, correct structure, and a passing checksum. Can I do bulk IBAN validation? Yes — bulk_check_iban accepts up to 1,000 IBANs per call, always in the same order, with a summary tally. A single bad entry never fails the batch. What is an IBAN check digit? The 2 digits after the country code (e.g. the 29 in GB29...), computed via the ISO 7064 MOD 97-10 algorithm. A single mistyped character almost always breaks it — exactly what a failed check catches, offline. Does it cover SEPA? Yes — every result flags whether the country is one of the 36 official SEPA scheme participants (the EU plus the UK, Switzerland, Norway, Iceland, Liechtenstein, Monaco, San Marino, Andorra, and Vatican City).

Trust & limits

Every check runs offline against a bundled public reference table — nothing stored beyond the response. Validation only: it confirms structure and checksum, not that the account exists or is open, and does not look up bank names or BICs.