# IBAN & BIC Validator (`accountable_eel/iban-bic-validator`) Actor

Validate IBANs and BIC/SWIFT codes offline: ISO 13616 mod-97 checksum and per-country BBAN structure for IBANs, format parsing for BICs. Checksum-valid IBANs are enriched with bank name, BIC, and address from openiban.com when available. Charged only on success — never for malformed input.

- **URL**: https://apify.com/accountable\_eel/iban-bic-validator.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 successful lookups

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## IBAN & BIC Validator

Validate IBANs and BIC/SWIFT codes for real — an ISO 13616 mod-97 checksum and
per-country BBAN structure check for IBANs, format/structure parsing for BICs, all
done **locally and offline**. Checksum-valid IBANs are additionally enriched with the
issuing bank's name, BIC, city, and zip from [openiban.com](https://openiban.com) when
available. No API key needed, and validation never depends on a third party being up.

### Features

- **Local, offline validation.** IBAN checksum and BBAN structure, plus BIC format and
  structure parsing, run entirely in-actor — no dependency on any third-party service
  being up or correct.
- **Auto-detection.** Each input item is automatically classified as an IBAN or a bare
  BIC — no need to say which is which.
- **Bank enrichment.** Checksum-valid IBANs are additionally looked up against
  openiban.com for the issuing bank's name, BIC, city, and zip — this only ever adds
  detail, it never overrides a locally-confirmed valid result.
- **Granular status codes.** `VALID`, `VALID_BANK_UNCONFIRMED`,
  `ENRICHMENT_UNAVAILABLE`, `BAD_FORMAT`, or `CHECKSUM_INVALID` — so you always know
  exactly why an item passed or failed.

### How validation works

Validation is done **locally and offline** first — it does not depend on any
third-party API being up or correct:

- **IBAN**: ISO 13616 mod-97 checksum plus per-country BBAN length/structure,
  via the `ibantools` library. A checksum-valid IBAN is then, additionally,
  looked up against **openiban.com** to enrich the result with the issuing
  bank's name, BIC, city, and zip — but that lookup only ever *adds* detail.
  If openiban.com is slow, down, or doesn't recognize the bank code, the IBAN
  is still correctly reported as valid (checksum and structure are objective
  facts, not something a third party can override), just without the bank
  name filled in.
- **BIC/SWIFT**: format and structure validation and parsing (bank code,
  country code, location code, branch code, test/production indicator), also
  via `ibantools` — fully local, no network call.

Each input item is auto-detected as an IBAN or a bare BIC — no need to say
which is which.

### How to use IBAN & BIC Validator

1. **In the Apify Console.** Open the actor page and click **Start** — the `items` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~iban-bic-validator/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["DE89370400440532013000"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "items": ["DE89370400440532013000", "DEUTDEFF500"],
  "maxConcurrency": 5
}
```

`items` is a list of IBANs and/or BIC/SWIFT codes. One dataset row is
returned per item; rows with `"found": false` are never charged.

### Output

IBAN item:

```json
{
  "query": "DE89370400440532013000",
  "found": true,
  "status": "VALID",
  "data": {
    "type": "iban",
    "iban": "DE89370400440532013000",
    "valid": true,
    "countryCode": "DE",
    "bban": "370400440532013000",
    "bankName": "Commerzbank",
    "bic": "COBADEFFXXX",
    "city": "Köln",
    "zip": "50656"
  }
}
```

BIC item:

```json
{
  "query": "DEUTDEFF500",
  "found": true,
  "status": "VALID",
  "data": {
    "type": "bic",
    "bic": "DEUTDEFF500",
    "valid": true,
    "bankCode": "DEUT",
    "countryCode": "DE",
    "locationCode": "FF",
    "branchCode": "500",
    "testBic": false
  }
}
```

`status` is one of `VALID`, `VALID_BANK_UNCONFIRMED` (checksum-valid IBAN,
bank code not found in openiban.com's registry), `ENRICHMENT_UNAVAILABLE`
(checksum-valid IBAN, openiban.com unreachable), `BAD_FORMAT`, or
`CHECKSUM_INVALID`.

### Use cases

- **Invoicing & payments verification** — catch a malformed or mistyped IBAN before it
  causes a failed or misdirected payment.
- **Vendor/customer onboarding** — validate bank details submitted through a signup or
  KYC form in bulk before they hit your payments system.
- **Data quality cleanup** — sweep an existing customer or vendor database for
  IBANs/BICs that fail checksum or structure validation.
- **Bank enrichment** — resolve a checksum-valid IBAN to its issuing bank's name and
  location for reconciliation or display purposes.

### Pricing

$4 per 1,000 results, plus a $0.00005 start fee. Misses (`found:false`) are never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~iban-bic-validator/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["DE89370400440532013000"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~iban-bic-validator/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"items":["DE89370400440532013000"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~iban-bic-validator/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"items":["{{value}}"]}`, mapping the row's value into the `items` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "IBAN & BIC Validator | Apify" — the agent will find and run this actor.

# Actor input Schema

## `items` (type: `array`):

List of IBANs (e.g. DE89370400440532013000) and/or bare BIC/SWIFT codes (e.g. DEUTDEFF or DEUTDEFF500) to validate. Each item is detected automatically — no need to say which is which. Only items that pass local validation are charged — never per run, and never for malformed or checksum-invalid input.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## `proxyConfiguration` (type: `object`):

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "items": [
    "DE89370400440532013000"
  ],
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "items": [
        "DE89370400440532013000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/iban-bic-validator").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "items": ["DE89370400440532013000"] }

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/iban-bic-validator").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "items": [
    "DE89370400440532013000"
  ]
}' |
apify call accountable_eel/iban-bic-validator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/iban-bic-validator"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/c8NxneFVkXxulka4W/builds/qnp8U8skTCgQrgBv0/openapi.json