Watch it catch a bad digit
Two IBANs, one character apart. The checksum is computed from the rest of the number, so a wrong digit cannot hide — the same maths a bank runs. Check it yourself against the example.
mod-97 check = 1 → accepted
check digits don't match → "checksum failed (mod 97)"
What one call reads
Ibanly runs the same three tests a bank runs when it accepts an IBAN.
- Shape
- Catches a missing country code, an illegal character, the wrong grouping.
- Country length
- Catches a UK IBAN with 21 characters where 22 are required.
- Checksum
- Runs the ISO 13616 mod-97 check that catches a mistyped digit or two swapped digits.
Where a check pays off
Checkout and billing
Validate a customer's IBAN before you set up a SEPA direct debit or store a payout method.
Payroll and payouts
Screen every beneficiary IBAN before you submit the file, so nothing bounces back a week later.
Onboarding
Tell a user their IBAN is wrong while they are still on the form, not after they leave.
Why not a bundled API or a regex
Most IBAN endpoints wrap validation in a broad "verification" product with bank-directory lookups you may not need, and route data through servers outside the EU. A hand-written regex misses the checksum entirely.
| Ibanly | Bundled verification API | A regex you maintain | |
|---|---|---|---|
| Real mod-97 checksum | yes | usually | rarely correct |
| Per-country length table | yes | usually | you keep it current |
| EU-only, nothing stored | yes | often not | yes |
| Priced for validation alone | yes | bundled with lookups | free |
| Time to first call | minutes | account review | days of edge cases |
Catch the bad IBANs before they cost you.
Free plan, 100 validations a month, no card. A key in seconds.
What to know before you rely on it
- Scope
- Ibanly confirms an IBAN is well formed. It does not check that the account exists, or who owns it — use a full bank-verification provider for that.
- Privacy
- IBANs are processed in the EU, validated in memory, and discarded. Never stored, never logged.
- Setup
- A REST endpoint and a bearer key. No SDK, no sales call. First call in minutes.
Simple, honest pricing
One thing metered one way: a validation. Start free.
Create a free account
Sign in, then create a key in the dashboard. 100 validations a month, no card.
Each key is shown once, when you create it. Create one per app and revoke any of them from the dashboard.