IBAN Validator: Verify & Bulk-Check Bank IBANs
Validate IBANs offline against ISO 13616 — checksum, structure and SEPA coverage, single or bulk.
In plain language.
Every IBAN encodes a country-specific length and a two-digit checksum computed from the rest of the number. This tool runs the full ISO 13616 check — mod-97 checksum plus each country's own structure — entirely offline, in well under a second.
Instead of one flat true/false, you get the exact reason the moment something's wrong: a bad checksum, a bad structure for that country, an unrecognized country prefix, or bad input — so you know exactly what to fix.
Runs the same whether a person pastes one IBAN or an AI agent bulk-checks a thousand mid-workflow.
Structure and checksum are evaluated independently, so you can tell apart an IBAN that has the right shape for its country but a mistyped digit, from one that was never the right shape at all. Those two failures have entirely different fixes, and collapsing them into a single “invalid” is what makes most validators frustrating to act on.
A failed checksum is the case worth routing to a human: the IBAN looks right, so it is usually one character away from correct. An unrecognised country prefix, by contrast, is nearly always a typo in the first two characters and can be fixed at the form.
SEPA membership is reported separately from IBAN format, because they are different questions. Some countries use IBANs without participating in the SEPA scheme, and a payment run that assumes otherwise will fail at the bank rather than at your validation step.
Nothing is transmitted anywhere. The country registry ships inside the tool, so validation is arithmetic against bundled reference data — there is no bank API to depend on, no rate limit to hit, and no account data leaving your run.
The registry covers roughly seventy-six IBAN-using countries. A country outside it returns an unknown-country result, which means it is not in the bundled registry rather than that it is not a real place.
Who it's for
- For finance teams. Before a month-end SEPA run, paste in the supplier IBAN column and get a per-row pass/fail with the reason, so a transposed digit is caught before the bank rejects the batch.
- For accounts payable and operations. Validate new supplier bank details at onboarding rather than at first payment, while you still have the supplier’s attention.
- For compliance and KYB. Confirm a counterparty’s stated IBAN is structurally genuine and note whether the country is a SEPA participant, as one input to an onboarding file.
- For developers and AI agents. Call it inline in a vendor-onboarding form and return the specific failure — wrong country, wrong length, failed checksum — instead of a generic “invalid”.
Pricing
$0.005 per IBAN checked.
No subscription. Failed or empty inputs are never charged.
Fewer knobs. Better defaults.
Offline & instant
No bank API, no network dependency — a 1,000-IBAN batch finishes in well under a second.
Honest error reasons
Five distinct failure statuses — bad checksum, bad structure, wrong length, unknown country, bad input — instead of one flat true/false.
SEPA-aware
Every result flags whether the country is one of the 36 official SEPA scheme participants.
Same tool, callable as an MCP server.
IBAN Validator runs on Apify, which means it's exposed as a remote MCP tool with no extra setup. Point any MCP-compatible agent (Claude, Cursor, and others) at the endpoint below.
View full API reference on Apify{ "ibans": ["GB29NWBK60161331926819", "DE89370400440532013000"] }