Guide
What to Do If an IBAN Checksum Fails
Learn common reasons an IBAN checksum can fail, how to re-check visible characters, and why you should not guess corrections for payment details.
Who should investigate a failed checksum
People pasting IBANs from invoices, emails, PDFs, bank letters, spreadsheets, or payment forms and seeing a failed checksum result.
Checksum failure troubleshooting
| Finding | Check next | Avoid |
|---|---|---|
| Unexpected length | Country code and complete copied groups | Adding zeros or trimming digits |
| Invalid character | PDF line breaks, punctuation and O/0 confusion | Replacing the character by intuition |
| Correct length, remainder not 1 | Transposed or mistyped characters | Trying random edits until one passes |
| Repeated failure from a trusted source | Ask the issuer or bank for confirmed details | Sending a test payment to diagnose it |
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.
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.
Local checks that explain a failure
BankCodeKit can normalize common separators, check allowed characters, check expected length, and run the MOD97-10 checksum for supported IBAN country data.
Why the intended replacement stays unknown
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.
Why a failed checksum should stop the workflow
A failure means the submitted value is not internally consistent with the IBAN checksum rules after normalization. It does not reveal the intended account or the correct replacement characters. Preserve the original input, note the exact error and obtain a complete confirmed IBAN from the recipient, invoice issuer, bank or payment provider before continuing.
Boundary case: O, 0, I and 1 remain ambiguous
A scan or low-resolution invoice can make letters and digits look alike. Trying each alternative until one version passes MOD97 creates a new value without proving that it matches the issuer's record. Record the failed input, avoid saving guessed variants as approved details and ask for the complete IBAN again through a trusted channel. The issuer's confirmed text resolves the ambiguity; the checksum only tests whichever candidate was entered.
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.
What a checksum failure cannot repair
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.
- 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 for What to Do If an IBAN Checksum Fails
Public references for What to Do If an IBAN Checksum Fails 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 to Do If an IBAN Checksum Fails 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.