The three checks
- Shape
- The IBAN must be two letters, two digits, then up to 30 alphanumeric characters. Ibanly catches a missing country code, an illegal character, or broken grouping before anything else runs.
- Country length
- Each country fixes its own IBAN length — a German IBAN is 22 characters, a Norwegian one is 15. Ibanly holds the table and rejects a UK IBAN with 21 characters where 22 are required.
- Checksum
- The two check digits are computed from the rest with the ISO 13616 mod-97 algorithm. Ibanly recomputes them, so a single mistyped digit or two swapped digits fails the check — the same maths a bank runs.
Trial and account: what you get back
A no-account trial answers the yes-or-no question. An account tells you why, so you can show a useful error on your form.
| Response includes | With an account | No-account trial |
|---|---|---|
| Valid or not | yes | yes |
| Country | yes | yes |
| Failure reason | yes | no |
| Parsed parts | yes | no |
| Formatted IBAN when valid | yes | no |
What Ibanly does not do
Being narrow is the point. Ibanly confirms an IBAN is well formed. It does not:
- confirm the account actually exists at the bank,
- confirm the account holder's name,
- look up the bank, BIC, or branch behind the IBAN.
If you need those, use a full bank-verification provider. If you need to stop malformed IBANs before they cost you a payment, that is exactly and only what Ibanly does — which keeps it fast and cheap.
Where your data goes
Nowhere it does not need to. IBANs are processed in the EU, validated in memory, and discarded. They are never written to a database and never appear in a log. There is nothing to breach later because nothing is kept.
Start with 100 free a month
Get a key in a few seconds. No card.