Catch a bad IBAN before it becomes a failed payment.
Structural checks, checksum verification, and bank & branch identification for every IBAN country, all returned in one request.
Every check the payment rail will run, done up front.
Structural validation, checksum verification, and registry lookups, in a single call.
Three checks, not one.
An IBAN can look correct and still fail at the bank. Here's what each layer actually catches.
Structural validation
Every IBAN starts with a two-letter country code and two check digits, followed by a country-specific BBAN. We confirm the length and pattern match what that country defines before anything else runs. This catches typos, wrong country codes, and IBANs that are simply the wrong length for where they claim to be from.
Checksum verification
The check digits exist for a reason: they're the output of a mod-97-10 calculation (ISO 7064) run across the rest of the IBAN. If a single digit gets transposed or mistyped, the checksum fails even though the IBAN still looks plausible at a glance. This is the step that catches human error.
Bank & branch resolution
A structurally valid, checksum-passing IBAN can still point at a bank identifier that doesn't exist. We resolve the embedded bank code against our registry and return the bank name, branch, and BIC where we have them, so you know the account is tied to a real institution, not just a well-formed string.
Run the validation engine on your own infrastructure.
Same checks, same data, no per-request calls to us. If you need to keep validation inside your own network for compliance, latency, or volume reasons, the self-hosted build runs the identical engine behind your firewall.
- Same structural, checksum, and bank-lookup logic as the hosted API
- Bank and country data shipped with the package, kept in sync with our registry
- No outbound calls per validation, so nothing leaves your network
Look up any country or bank.
Start typing a country or bank name and jump straight to its page.
Every validation call uses 1 basic credit. Calls that also resolve bank details, meaning anything other than a basic-only request, use 1 bank lookup credit as well.