IBAN Validator

No, and this is the important limitation. The check is arithmetic: it proves the number is internally consistent, not that any bank holds such an account or that it belongs to the person you think. Only the receiving bank can confirm existence and ownership.

Mistyped digits, transposed pairs, missing or extra characters, and a country code that does not match the length. The MOD 97-10 scheme catches essentially all single-digit errors and the overwhelming majority of two-digit transpositions — the two mistakes people make when retyping an IBAN from a PDF.

22 characters: RS, two check digits, a 3-digit bank code, a 13-digit account number and 2 control digits. Written for print it appears in groups of four — RS35 2600 0560 1001 6113 79 — but the spaces are cosmetic and can be dropped when entering it in a form.

Yes, for Serbia. The 18 digits of the domestic number are the IBAN’s account part, so only the check digits need computing. That is exactly what the build tab does. Your bank prints the same result in its e-banking app, which is a good way to double-check.

Because banks print the domestic number without leading zeros. The IBAN always uses the full 13-digit account field, so 930987654321 becomes 0930987654321 inside the IBAN. The tool shows both forms so you can match them up.

No. The tool uppercases the input and strips spaces, dots and dashes before validating, which is the same normalisation banks apply. IBANs are stored without separators and printed with them.

The IBAN identifies the account; the BIC identifies the bank. For payments inside the SEPA area the IBAN is usually enough, while transfers involving Serbia typically ask for both. This tool checks only the IBAN — a BIC has no check digits to verify.

Because it is not in the IBAN registry. Not every country uses IBAN — the United States and Canada do not, for instance — so a number that begins US or CA is not an IBAN at all, however plausible it looks.

Yes: XK (20 characters), ME (22) and BA (20) are in the registry, along with the rest of the region. The same arithmetic applies; only the expected length differs.

Not in one go — the tool takes one number at a time so the breakdown stays readable. Paste them one after another; each check is instant, and nothing is stored between them.

No. The validation is pure arithmetic in your browser: no server call, no bank lookup, nothing in analytics. That is deliberate — an account number is exactly the kind of data that should not travel to check a checksum.

Common reasons: the account was closed, the name does not match the account, the currency is not accepted, or the payment needed a BIC or a payment code that was missing. Check digits only prove the number was typed correctly.