IBAN Validator: Check an IBAN Before You Send Money
One mistyped character can bounce a payment. Check the country, length and mod-97 checksum of an IBAN before you send it.
IBAN Validator: Check an IBAN Before You Send Money
A payment that bounces because of one wrong digit costs time, and sometimes a fee. An IBAN contains a built-in checksum, which means most typing mistakes can be caught before the money leaves your account. The IBAN Validator performs that check in seconds.
What an IBAN actually contains
An International Bank Account Number is not random. It is built from a few identifiable parts:
- Country code — two letters, such as
DEfor Germany orNLfor the Netherlands. - Check digits — two digits calculated from the rest of the number.
- Bank code — identifies the bank, and its length depends on the country.
- Account number — the customer's account at that bank.
The total length is fixed per country, which is why an IBAN that is valid in one country can be the wrong length in another.
How the validator checks an IBAN
The tool performs three checks:
- Country code and length — the input must match a known country format.
- Checksum — the mod-97 calculation that catches transposed or mistyped digits.
- Formatting — spaces and lowercase letters are accepted and normalised.
If any check fails, the tool tells you what is wrong rather than simply rejecting the input.
What a valid IBAN does not tell you
This is the important limitation. A valid IBAN is correctly formed, not necessarily open and owned by the person you think. The checksum cannot tell you:
- whether the account exists,
- whether it is still active,
- who owns it,
- whether the name matches.
For a large or first-time payment, confirm the account name with the recipient through a channel you already trust, and use your bank's own verification where available.
Common IBAN mistakes
- Dropped or added characters while copying from an email.
- Transposed digits — the checksum catches most of these.
- Spaces in the wrong place — harmless for validation, but some forms reject them.
- Using a BIC/SWIFT code as an IBAN — they are different things.
- Mixing up two countries — a valid-looking number may still be the wrong length for its country.
A sensible payment checklist
- Paste the IBAN into the IBAN Validator and confirm it passes.
- Read the formatted result back against the source, character by character, for a large payment.
- Confirm the account holder's name with the recipient.
- Keep the confirmation with your payment records.
Frequently asked questions
Is a valid IBAN guaranteed to work? No. It is correctly formed, but the account may be closed or the details may belong to someone else.
Does the tool store the IBAN? The value is used only to run the check.
Can I check a BIC or SWIFT code? No, this tool validates IBANs. BIC/SWIFT codes use a different format.
Are spaces and lowercase allowed? Yes. They are normalised before validation.
Can I use it for SEPA payments? Yes. SEPA uses IBANs, and a checksum failure is a strong sign the details are wrong.
Related posts
View allBase64 Encode and Decode: A Practical Guide
Encode text to Base64 or decode it free in your browser. UTF-8 safe, line breaks tolerated, size and character counts shown, with errors on invalid input.
Convert CSV to JSON: Keep Types and Headers Right
Convert CSV to JSON free with auto delimiter detection, typed numbers and booleans, duplicate-header handling and 2/4-space or tab output. Runs in browser.
Decode a JWT Online: Header, Payload and Expiry
Decode a JWT online free. See the header algorithm, payload claims, expiry status in UTC and a readable claim summary. Decoding happens in your browser.
Comments (0)
Be the first to share feedback on this post.