Guide
What IBAN Validation Can and Cannot Check
Learn how country code, length, characters, and MOD97 checks assess IBAN structure, and why the result cannot establish account existence or ownership.
Who should separate format evidence from account evidence
People reviewing payment forms, invoices, vendor records, and software format-check results before using real payment details.
Passed means and does not mean
| Check | A pass means | A pass does not mean |
|---|---|---|
| Country and length | The prefix is supported and length matches the local reference | The account is open or can receive a transfer |
| Characters | Only permitted letters and digits remain after normalization | The recipient name matches the account |
| MOD97 checksum | The rearranged numeric value produces remainder 1 | The payment is safe, authorized or likely to succeed |
| SEPA context | The country appears in local scheme-scope reference data | A specific bank participates in a specific scheme |
What an IBAN format checker can check
An IBAN format checker can check visible structure. BankCodeKit normalizes spaces and hyphens, reviews the country code, checks the country-specific length, confirms allowed characters, and runs the checksum where the country is supported.
- Country code: the first two letters, such as DE or FR.
- Expected length: each supported country has a defined IBAN length.
- Allowed characters: IBANs should contain letters and digits after normalization.
- Checksum: the MOD97-10 check helps catch many typing mistakes.
Why these checks are still useful
Format validation is a good first pass because it catches many obvious errors before a value is copied into a payment form, invoice, customer record, or test workflow.
What validation cannot check
Format checks do not contact banks, payment providers, account registries, sanctions systems, or live payment networks. They only evaluate the value that is visible in the browser.
Use separate evidence for real-world payment decisions
Format evidence and payment evidence answer different questions. Use the checker to catch incomplete, mistyped or structurally inconsistent values. Keep the original instruction available while reviewing the normalized result. Use a bank, payment provider, verified recipient contact or authenticated invoice workflow to confirm payee identity, routing requirements, account availability, sanctions status, fraud risk and transfer readiness before money moves or a transfer is authorized.
Boundary case: a changed IBAN that still passes
A supplier-change message can contain an IBAN with the correct country length, permitted characters and a valid MOD97 checksum. Those passes show that the replacement is internally consistent, not that the supplier requested it. Compare the instruction with earlier records and confirm the change through a contact route already known to your organization. The independent confirmation, rather than another format check, is the evidence that connects the value to the intended payee.
Practical validation example
A German example IBAN can pass country, length, character, and checksum checks without proving anything about a real recipient.
- Example value: DE89 3704 0044 0532 0130 00
- Country code check: DE is a supported country code.
- Length check: Germany uses 22 characters in digital format.
- Checksum check: the check digits pass the supported MOD97-10 process.
- Account existence and ownership: not confirmed by format checks.
What a passed IBAN result still leaves unresolved
Format checks only. This guide does not confirm account existence, ownership, bank reachability, or payment success. Read the detailed disclaimer for the full limitation list.
- It does not confirm account existence.
- It does not confirm account ownership.
- It does not confirm bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.
- It does not replace confirmation with a bank, payment provider, invoice issuer, or recipient.
FAQ
Does IBAN validation check the country code?
Yes. It can check whether the first two letters are a supported IBAN country code in the local reference data.
Does checksum validation prove an account is real?
No. The checksum is a structural check only and does not contact a bank.
Can an invalid IBAN still look realistic?
Yes. A value can look like an IBAN but fail length, character, country, or checksum rules.
Should I verify payment details after validation?
Yes. Verify real payment details with your bank, payment provider, invoice issuer, or recipient.
Sources for What IBAN Validation Can and Cannot Check
Public references for What IBAN Validation Can and Cannot Check are linked below; detailed standard scope, review methods, and licensing boundaries are documented on the Sources and Updates page.
Matching the cited format and reference data for What IBAN Validation Can and Cannot Check does not confirm account existence, ownership, bank reachability, or payment success. Read the detailed disclaimer.
Reference data reviewed: 2026-07-17 Next scheduled data review: 2026-10-17 Sources: Swift IBAN Registry Reference data is reviewed periodically. BankCodeKit does not perform live bank, account, sanctions, or payment-network confirmation.