What to Do If an IBAN Checksum Fails

Who this guide is useful for

People pasting IBANs from invoices, emails, PDFs, bank letters, spreadsheets, or payment forms and seeing a failed checksum result.

Treat a checksum failure as a review signal

An IBAN checksum failure means the visible value does not pass the supported structural check after normalization. It should be treated as a reason to re-check the source value, not as a prompt to guess a correction.

Common causes to review

Many checksum failures come from copying or typing problems. Compare the value against the original payment instruction before using it anywhere else.

Missing or extra characters.
Wrong country code at the start of the IBAN.
Transposed digits or letters.
Similar-looking characters such as O and 0 or I and 1.
Characters copied from a PDF or email with hidden spacing or punctuation.

What BankCodeKit can check

BankCodeKit can normalize common separators, check allowed characters, check expected length, and run the MOD97-10 checksum for supported IBAN country data.

What BankCodeKit cannot check

BankCodeKit cannot tell which character is correct, cannot confirm the account, and cannot confirm whether the payment details belong to the intended recipient.

What to do next

Re-copy the IBAN from the trusted source, compare it character by character, and ask the invoice issuer or recipient to confirm the payment details through a trusted channel if the failure remains.

Practical checksum-failure example

A failed checksum is useful because it blocks a value from being treated as structurally valid.

A copied invoice value fails the checksum check.
You compare the country code, length, and each character against the original source.
You do not guess which digit should change.
If the issue remains, you request confirmation from the invoice issuer or recipient through a trusted channel.

Important limitations

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

A checksum failure does not identify the correct replacement value.
BankCodeKit does not suggest guessed corrections for real payment details.
A later passed checksum still does not prove account existence, account ownership, or payment safety.
Real payment instructions should be confirmed with a trusted bank, provider, invoice issuer, or recipient channel.

FAQ

Should I guess the correct IBAN if the checksum fails?

No. Do not guess corrections for payment details. Re-check the source value or confirm it through a trusted channel.

Can spaces cause a checksum failure?

BankCodeKit removes common spaces and separators before checking, so a failure usually means the normalized value still does not pass.

Does a checksum failure prove fraud?

No. It is a structural failure signal only. It does not determine intent, fraud risk, or payment safety.

What if the recipient sends a different IBAN?

Treat changed details carefully and confirm them through a trusted channel before using them.

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.