IBAN Validator - Bulk IBAN Checker

IBAN Validator

IBAN Validator checks IBANs in bulk: mod-97 checksum, country length and SEPA membership, then extracts the bank code, branch, UK sort code and account number. It runs entirely offline, so no IBAN leaves the run.

Best for: Supplier and payout onboarding, payment file checks, CRM data cleansing and SEPA payment preparation.

How to validate IBANs in bulk

1. Add IBANs to IBANs (ibans), with or without spaces.
2. Click Start.
3. Filter on valid and read error for any failures.

How it works

Checks are done entirely inside the Actor using the ISO 13616 algorithm and SWIFT IBAN registry lengths. No IBAN leaves the run. A valid checksum shows the IBAN is well-formed, not that the account exists or is open.

Output

input, iban, valid, countryCode, sepa, bankCode, sortCode, accountNumber, formatted, error

Pricing (pay-per-event)

• iban-validated: $0.0005 per result ($0.5 / 1,000). Platform usage is included; you pay only for results.
• Example: 10,000 IBANs cost $5.00.

Example input

{
  "ibans": [
    "GB82WEST12345698765432",
    "FR1420041010050500013M02606",
    "NL91ABNA0417164301"
  ]
}

Example output

Real output for GB82WEST12345698765432 (a run on 15 Oct 2026). Invalid IBANs also include an error message.

{
  "input": "GB82WEST12345698765432",
  "iban": "GB82WEST12345698765432",
  "valid": true,
  "countryCode": "GB",
  "sepa": true,
  "checkDigits": "82",
  "bban": "WEST12345698765432",
  "formatted": "GB82 WEST 1234 5698 7654 32",
  "bankCode": "WEST",
  "branchCode": "123456",
  "sortCode": "12-34-56",
  "accountNumber": "98765432"
}

Use it via API, schedules and integrations

Run it in Apify Console, or call it from your own code with the Apify API or the Python and JavaScript clients. Save an input as a task and add a schedule to run it regularly, and send results to Slack, email, webhooks, Zapier, Make or n8n with Apify integrations. AI agents can find and run it through the Apify MCP server.

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("sterlingverify/iban-validator").call(run_input={"ibans": ["GB82WEST12345698765432"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Use in Clay, Zapier, Make, n8n, Pipedream, Power Automate or Activepieces

All of them connect to Apify through their official Apify integrations, using your own Apify account: an API token from Apify Console > Settings > API & Integrations, or Apify sign-in for Power Automate. Runs bill to your Apify account at this Actor's pay-per-event price.

• Clay: save this Actor's input as an Apify task and copy it as JSON. In your Clay table, add the Run Apify Actor enrichment, choose it and paste the JSON into Input Data, mapping Clay columns into the fields. To pull a finished run into a new table, use the Import data from Apify Actor source.
• Zapier: use the Apify Run Actor action, or the Finished Actor run trigger followed by Fetch dataset items. Synchronous runs in Zapier stop after 30 seconds, so use the trigger for big batches.
• Make: add the Apify Run an Actor module with Run synchronously set to Yes, then Get Dataset Items with the run's dataset ID. For longer runs, use the Watch Actor Runs trigger.
• n8n: install the Apify node (@apify/n8n-nodes-apify, or search "Apify" on n8n Cloud) and use Run an Actor and get dataset.
• Pipedream: add the Apify app's Run Actor action, or Run Task Synchronously on one of this Actor's public example tasks (or your own saved task) to get the dataset items back in one step. For big batches, start from the New Finished Actor Run or New Finished Task Run trigger, then Get Dataset Items.
• Power Automate: add the Apify connector (a premium connector, currently in preview) and sign in with your Apify account. Use Run Actor with Enter custom value set to sterlingverify/iban-validator and paste the input as JSON, then Get dataset items with the run's default dataset ID. For big batches, start the flow from the Actor run finished trigger instead.
• Activepieces: add the Apify piece and use Run Actor, or Run Task on one of this Actor's public example tasks (or your own saved task), then Get Dataset Items. For scheduled or big batches, use the Watch Actor Runs or Watch Task Runs trigger.
• Google Drive / Sheets: add Apify's Upload results to GDrive integration to a scheduled task to drop each run's CSV or XLSX into your team's Drive, or chain the Google Sheets Import & Export actor to append rows to a sheet.
• Slack alerts: add Apify's Slack integration to a scheduled task to post each run's results to your team channel, or start a check from Slack with /apify call and your task ID.
• Any HTTP tool or script: send one request and get the results back as JSON. Runs must finish within 5 minutes.

curl -X POST "https://api.apify.com/v2/acts/sterlingverify~iban-validator/run-sync-get-dataset-items" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json

FAQ

Does a valid IBAN mean the account exists?

No. A valid checksum shows the IBAN is well-formed, not that the account exists, is open or who owns it. Use Confirmation of Payee or your bank for that.

Is my data sent anywhere?

No. All checks run inside the Actor using the ISO 13616 algorithm and SWIFT IBAN registry lengths.

Disclaimer

A valid IBAN format does not confirm that an account exists or who owns it; use Confirmation of Payee or your bank for that. Not financial advice.

Related sterlingVerify tools

Part of the sterlingVerify UK payments, KYB and data toolkit on Apify Store:

• UK Bank Account Validator: UK sort code and account number modulus check
• BIN Lookup: bulk BIN lookup for scheme, type, issuer and country
• EU VAT Number Validator (VIES): bulk EU VAT number checks against VIES
• Payments Region Checker: EEA, SEPA, SCA and interchange classification by country or BIN