OSINT Intel
IBAN

Check an IBAN before you pay

Validate any IBAN and resolve the bank behind it — name, BIC and city — before money changes hands. Fabricated and mistyped account numbers are caught instantly.

Try

  • ISO 7064 checksum & length validation
  • Bank name, BIC / SWIFT & city
  • Bank, branch & account breakdown
  • Remote-onboarding bank flags

What the report tells you

An IBAN report checks the number itself and then the bank behind it. The ISO 7064 checksum and the country's required length catch anything fabricated or mistyped before you send money. The account number is then broken into its bank, branch and account parts, and the bank code is resolved against national registries into a bank name, BIC and city.

Where the bank names come from

Bank names are resolved from official registries bundled into the service rather than a third-party lookup, covering sixteen countries including Germany, France, Spain, Portugal, Greece, Poland, Czechia, Austria, the Netherlands, Ireland and more. Belgium, Switzerland, Liechtenstein and Luxembourg resolve through OpenIBAN. Where a country publishes no machine-readable register, the report says so rather than leaving the field blank.

When to run one

Before paying an invoice from a new supplier, when bank details on an existing invoice change, or when a marketplace seller asks for a direct transfer. A valid checksum does not mean the account is honest, but an account at a bank in a country unrelated to the seller is worth a second look.