How to Catch a Typo in an IBAN Before You Pay

Someone sent you their IBAN over email or a chat message, you’re about to enter it into a payment form, and a single transposed digit or mistyped letter could mean the payment goes somewhere else entirely, or simply bounces back after a delay. IBANs are long — often 20 or more characters mixing letters and numbers — which makes them exactly the kind of string a person is likely to mistype when copying by hand, and unlike a lot of everyday typos, an IBAN error isn’t always obviously wrong just from looking at it.

The format was actually designed with error-catching built in — every valid IBAN includes a checksum specifically meant to catch this kind of transcription mistake — but that only helps if something actually checks it before the payment goes out.

What IBAN validation actually checks

An IBAN’s structure includes a two-character checksum, calculated using the mod-97 algorithm across the rest of the number, specifically designed to catch common transcription errors like transposed digits or a single mistyped character. Validation means recalculating that checksum from the entered IBAN and confirming it matches, alongside checking that the overall length matches what’s expected for that IBAN’s specific country code, since different countries use different fixed lengths.

This is a meaningfully different level of protection than just checking that an IBAN “looks like” the right format — the checksum specifically catches the kind of small transcription error that’s otherwise invisible until a payment fails or, worse, succeeds by landing in the wrong account.

Why people get stuck here

• IBANs are long and easy to mistype when copying by hand. Twenty-plus characters mixing letters and numbers gives plenty of surface area for a single character to get transposed or mistyped.
• A malformed IBAN doesn’t always look obviously wrong. Unlike an email address missing an @ symbol, an IBAN with one wrong digit still looks like a plausible IBAN at a glance.
• Country-specific length isn’t common knowledge. Different countries’ IBANs have different fixed lengths, so knowing whether a specific IBAN “looks the right length” isn’t something most people can judge without a reference.
• The consequence of a payment error can be serious. International payments can be slow to reverse, or in rare unfortunate cases go to an account you can’t easily recover funds from, which raises the stakes of catching an error before sending, not after.

What a good IBAN validator looks like

Checks the mod-97 checksum, not just the format

The checksum is specifically what catches transcription errors — a validator that only checks superficial formatting (letters and numbers in roughly the right places) misses the protection the checksum is actually designed to provide.

Verifies country-specific length

Since IBAN length varies by country, the validator needs to know the correct expected length for the specific country code at the start of the IBAN, not just check for “a reasonable length.”

Gives a clear pass or fail result

For a task this consequential, an unambiguous result — valid or not — is more useful than a vague indication that leaves room for misinterpretation.

Common mistakes to avoid

• Assuming an IBAN that “looks right” (correct-ish length, plausible characters) is actually valid without running the checksum check.
• Copying an IBAN from a source that might have already introduced an error (a scanned document, a garbled email) without independently verifying it before use.
• Not double-checking the country code specifically, since a wrong country code changes what length and structure the rest of the IBAN should have.
• Sending a payment based on an IBAN that failed validation, hoping it’ll work anyway rather than going back to confirm the correct number with the recipient.
• Confusing IBAN validation with full payment verification — a valid checksum confirms the IBAN is well-formed, not that the account actually exists or belongs to the intended recipient.

How to do it with IBAN Validator

Online Tool Store’s IBAN Validator checks country-specific length and mod-97 checksum validity, entirely in your browser.

1. Paste the IBAN you want to verify.
2. Get an instant check of its length and checksum validity.
3. If it fails, go back to the source and confirm the correct number before proceeding.
4. Use it as a quick check before entering an IBAN into any payment form.

Because it checks the actual checksum, not just superficial formatting, it catches the specific kind of transcription error that’s otherwise easy to miss until a payment already fails or misroutes.

Frequently asked questions

Does a valid IBAN checksum guarantee the account is real?

No — checksum validation confirms the IBAN is internally consistent and well-formed, not that it corresponds to an actual existing account. A validator catches transcription errors; it can’t confirm the account exists or belongs to who you think it does.

Why do IBANs have different lengths for different countries?

Each country’s central banking authority defines its own basic bank account number (BBAN) structure within the overall IBAN standard, which is why total length varies — a German IBAN and a UK IBAN, for instance, have different fixed lengths.

What should I do if an IBAN fails validation?

Go back to the source and re-confirm the correct number, ideally through a channel separate from wherever you originally received it, especially for a payment of any significant value — don’t proceed with a number that failed the checksum check.

Final thought

The IBAN format has built-in error detection specifically for this scenario — a mistyped digit during manual copying — but only if something actually runs the check before the payment goes out. Validate before you pay, not after something goes wrong.

Try the free IBAN Validator