What IBAN Validation Can and Cannot Check

Who this guide is useful for

People reviewing payment forms, invoices, vendor records, and software validation results before using real payment details.

What an IBAN validator can check

An IBAN validator 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.

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 validation.

Important limitations

BankCodeKit validates format and reference data only. It does not confirm account existence, account ownership, bank connectivity, sanctions status, fraud risk, payment readiness, or payment success.

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 verification 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 and update note

BankCodeKit uses local IBAN reference data and browser-local format rules for country, length, character, and checksum checks. The official Swift IBAN information is used as a reference source, but BankCodeKit does not query Swift or any bank while you use the tool. Reference data is reviewed periodically and does not imply live accuracy.

Swift IBAN Registry Reference information for IBAN structure, country support, and format rules.