IBANforge checks the bank behind an IBAN before you pay. It validates IBANs from all 89 IBAN countries and, in all but 8 of them, names the bank and its BIC, with the source of that answer. Where it reads the national register (Germany, Austria, Belgium, Slovakia, Czech Republic, Bulgaria, Switzerland and Liechtenstein), it also tells you whether the bank code is allocated at all; elsewhere it names the bank from a partial register or a composite map, and says that such an answer cannot rule a code out. For a SEPA bank it resolves, it gives the SEPA schemes that reach it (Credit Transfer, Instant, Direct Debit), from the EPC scheme registers when they list the bank and from the country otherwise (the answer says which), and says whether the EPC Verification of Payee (VoP) register lists the bank as ready to answer VoP requests. It does not check who holds the account: that name check belongs to the payee's bank, through VoP. BIC directory, 121,000+ entries (entries, not institutions): GLEIF and national registers, refreshed monthly, plus a public copy of the SWIFT directory frozen in January 2018 that still makes up about two thirds of the rows.

How much does IBANforge cost?

IBANforge offers a free tier: 25 requests a month on an API key you get with one empty POST, no e-mail and no card, and 200 a month once you claim that key. Beyond that, pay $0.002 to $0.02 per call using USDC micropayments via the x402 protocol. No subscription required.

Can AI agents use IBANforge?

Yes. IBANforge is MCP-native with 11 tools: validate_iban, batch_validate_iban, lookup_bic, check_compliance, lookup_ch_clearing, validate_payment_reference, check_postal_address, check_swiss_qr_bill, send_feedback, request_api_key and poll_api_key. Compatible with Claude, GPT, and any MCP client.

What countries does IBANforge support?

IBANforge validates IBANs from 89 countries with full BBAN parsing, SEPA membership, the Verification of Payee (VoP) duty of the country and the VoP readiness of the bank, and country-level risk classification. The bank code is checked against the national register in Germany, Austria, Belgium, Slovakia, Czech Republic, Bulgaria, Switzerland and Liechtenstein.

x402 MICROPAYMENTS MCP NATIVE 121K BICs NATIONAL REGISTERS

IBANforge

Validate IBANs. Lookup BICs. Score risk.

One API for developers & AI agents.

Bank-code verdict from national registers · Bank-level sanctions screening · SEPA & VoP readiness · 89 IBAN countries

Swiss clearing: every IID of the SIX BankMaster with its payment-rail participation (SIC, euroSIC, CHF Instant Payments) and, where SIX allocates one, its QR-IID, refreshed monthly.

Try it free ↓ curl quickstart

Leave it empty and the key is yours right away: 25 requests a month, nothing to confirm. An address raises it to 200 a month.

By requesting a key you agree to the Terms of Service and Privacy Policy.

Your API key (save it now):

25 requests/month — claim this key to raise it to 200 a month. It will not be shown again.

Demo

Try it now

Free, no account required

IBAN Validate

BIC Lookup

★ Compliance Check

Capabilities

Why IBANforge?

Compliance-grade IBAN intelligence for developers and AI agents.

121K

BIC entries, 89 IBAN countries

BIC directory from GLEIF, national registers and a public directory dated January 2018; every validation names its source. Bank codes checked against the national register in Germany, Austria, Belgium, Slovakia, Czech Republic, Bulgaria, Switzerland and Liechtenstein. Full BBAN parsing per country format.

Compliance & Risk Scoring

Bank-level sanctions screening (OFAC, EU, UN on the BIC8, not the payee), FATF status, composite risk score 0–100, 500+ EMI/neobank classifications, Swiss clearing data.

MCP Native

11 tools for AI agents via Model Context Protocol. Works with Claude, GPT, and any MCP client.

x402 Micropayments

Pay per call with USDC on Base L2. No subscription, no signup. Machine-to-machine native.

SEPA & VoP Coverage

SCT, SDD, SCT_INST reachability check. Verification of Payee participant status per BIC.

<30ms

Fast & Developer-friendly

OpenAPI spec. npm SDK. Batch up to 100 IBANs. Free key without an e-mail.

Pricing

Three paths, same API

Choose what fits your workflow. Switch anytime.

FREE TIER

API Key

25 requests/month — no e-mail, no card

✓ All endpoints included
✓ IBAN validate, BIC lookup, compliance
✓ Batch up to 100 IBANs
✓ Bearer token auth
✓ Usage dashboard

CREDIT PACKS

Stripe / Card

From $4 / 1k credits — pay by card

✓ Credits never expire
✓ Bearer token, all endpoints
✓ Larger packs = lower per-call cost
✓ Card, Apple Pay, Google Pay
✓ Receipt + key by email
✓ Or flat: Pro, $29/month for 10,000 requests

1 000 $4 $0.005/call 5 000 $20 $0.004/call 25 000 $80 $0.0032/call

PAY PER CALL

x402 / USDC

From $0.003/call — no account needed

✓ All endpoints included
✓ No signup, no API key
✓ USDC on Base L2
✓ Machine-to-machine native
✓ Unlimited volume

View x402 docs

Per-call pricing (both paths)

Endpoint	Price
POST /v1/iban/validate	$0.005
POST /v1/iban/batch	$0.002/IBAN
GET /v1/bic/:code	$0.003
POST /v1/iban/compliance	$0.020
GET /v1/ch/clearing/:iid	$0.003

Get Started

Up and running in 30 seconds

Choose your integration method.

cURL

JavaScript

Python

npm SDK

# Validate an IBAN (free with API key) curl -X POST https://api.ibanforge.com/v1/iban/validate \ -H "Content-Type: application/json" \ -H "Authorization: Bearer ifk_your_key_here" \ -d '{"iban": "GB29NWBK60161331926819"}' # Or pay per call with x402 — no key needed curl -X POST https://api.ibanforge.com/v1/iban/validate \ -H "Content-Type: application/json" \ -H "PAYMENT-SIGNATURE: <x402-payment-header>" \ -d '{"iban": "DE89370400440532013000"}'

import requests res = requests.post( "https://api.ibanforge.com/v1/iban/validate", headers={ "Content-Type": "application/json", "Authorization": "Bearer ifk_your_key_here", }, json={"iban": "GB29NWBK60161331926819"}, ) print(res.json()) # x402: omit Authorization header, add X-Payment instead

import { IBANforge } from '@ibanforge/sdk'; const client = new IBANforge('ifk_your_key_here'); const result = await client.validate('GB29NWBK60161331926819'); console.log(result); // Batch validation const batch = await client.batchValidate([ 'GB29NWBK60161331926819', 'DE89370400440532013000', ]);

AI Agents? Use MCP

Add IBANforge to your agent with npm run mcp — exposes 11 tools via stdio transport. Compatible with Claude Desktop, Cursor, and any MCP client.