IBAN Validator & Bank Lookup (BIC, Bank Name) – Bulk

IBAN Validator & Bank Lookup (BIC, Bank Name) – Bulk, Offline-Fast

Validate thousands of IBANs in seconds and find out which bank is behind each one. Everything runs offline inside the actor – no third-party IBAN API is ever called, so your account data never leaves the run.

What it does

For every IBAN you supply it:

• Normalises the input (spaces, dashes, lower case and an IBAN prefix are fine) and formats it in groups of 4.
• Checks the country code and the country-specific length for all countries in the SWIFT IBAN registry.
• Checks the BBAN structure (e.g. DE: 8-digit Bankleitzahl + 10-digit account; FR: bank, branch, account, RIB key).
• Verifies the ISO 7064 MOD-97 checksum (the 2 check digits).
• Verifies the national account checksum where an algorithm is known (DE, FR, ES, IT, BE, …) – catches typos the IBAN checksum alone may miss.
• Flags SEPA membership.
• Bank lookup: bank name, BIC and city.
  • Germany: official Deutsche Bundesbank Bankleitzahlendatei, downloaded fresh at build time (dataSourceDate shows the validity date of the file, e.g. 2026-09-07).
  • Other countries: bank name and BIC from official central-bank registries (AT, BE, CH, CZ, ES, FI, FR, IT, NL, PL, SE, SK, … via the open-source schwifty registry). Where no data exists, bankCode is still returned.

Note: a valid IBAN only proves that the number is correctly formed. It does not prove that the account exists, is open, or belongs to a particular person. Use a bank-side check (e.g. Verification of Payee) for that.

Who it's for

Finance and accounting teams cleaning vendor master data, e-commerce and SaaS checkouts collecting SEPA mandates, CRM/ERP imports, fintech onboarding, and AI agents that need a reliable IBAN check tool.

Why it's better

• Bank name + BIC + city, not just "valid / invalid" – with the official Bundesbank file for Germany.
• National checksums on top of MOD-97 for stricter validation.
• Offline & private: no external API calls, no rate limits; 1,000s of IBANs per second.
• Cheap: $0.0005 per IBAN, malformed inputs are free.
• Flat, AI-friendly output with a clear error text per row.

Input

{
  "ibans": [
    "DE89370400440532013000",
    "GB82 WEST 1234 5698 7654 32",
    "NL91ABNA0417164300",
    "FR1420041010050500013M02606",
    "DE89370400440532013001"
  ],
  "includeBankInfo": true
}

Output (real values from a test run)

{
  "input": "DE89370400440532013000",
  "iban": "DE89 3704 0044 0532 0130 00",
  "countryCode": "DE",
  "country": "Germany",
  "valid": true,
  "checksumValid": true,
  "lengthValid": true,
  "formatValid": true,
  "nationalChecksumValid": true,
  "sepa": true,
  "bankCode": "37040044",
  "branchCode": null,
  "accountNumber": "0532013000",
  "bankName": "Commerzbank",
  "bic": "COBADEFFXXX",
  "bankCity": "Köln",
  "bankDataSource": "Deutsche Bundesbank Bankleitzahlendatei",
  "dataSourceDate": "2026-09-07",
  "error": null
}

A wrong check digit (DE89370400440532013001) returns "valid": false, "checksumValid": false, "error": "Invalid IBAN check digits (MOD-97)". NL91ABNA0417164300 returns "bankName": "ABN AMRO BANK N.V.", "bic": "ABNANL2A".

Field	Meaning
valid	Length, BBAN structure, MOD-97 and (where known) national checksum all OK
checksumValid / lengthValid / formatValid / nationalChecksumValid	Individual checks (null = not applicable / not checkable)
sepa	Country is in the SEPA zone
bankCode, branchCode, accountNumber	Parts of the BBAN
bankName, bic, bankCity	Bank lookup (city for DE)
bankDataSource, dataSourceDate	Where the bank data comes from and how fresh it is
error	Human-readable reason when something fails

Pricing

Pay per event: $0.0005 per IBAN (iban event) for every well-formed IBAN of an IBAN country – including the bank lookup. Inputs that are not IBANs at all, or from countries without IBAN, are free. 10,000 IBANs = $5.

Use via API, n8n, Make or MCP

• API: POST https://api.apify.com/v2/acts/fast_data_asap~iban-validator-bank-lookup/run-sync-get-dataset-items?token=<TOKEN> with the input JSON above.
• n8n / Make / Zapier: use the Apify integration, actor fast_data_asap/iban-validator-bank-lookup.
• MCP (Claude, Cursor, other AI agents): https://mcp.apify.com?tools=fast_data_asap/iban-validator-bank-lookup

Data sources

• IBAN formats: SWIFT IBAN registry (bundled).
• Germany: Deutsche Bundesbank, Bankleitzahlendatei (public download, refreshed whenever the actor is rebuilt).
• Other countries: official national bank-code lists as compiled by the open-source schwifty library (MIT).