What does IBANforge validate?

IBANforge validates IBAN structure (ISO 13616 mod-97 check digits + country-specific BBAN), resolves the associated BIC/SWIFT against 121,000+ BIC entries from public sources (GLEIF, SWIFT directory, Bundesbank, SIX, NBP, EBA Step2 SCT) with LEI enrichment for ~38K rows sourced from GLEIF, looks up Swiss BC-Nummer / IID against 1,190 SIX BankMaster entries, classifies the issuer (bank, EMI, vIBAN provider, neobank), and flags SEPA Instant + VoP (Verification of Payee, EU 2024/886) reachability.

How much does IBANforge cost?

Pay-per-call in USDC via x402: 0.005 USDC for IBAN validation, 0.003 USDC for BIC lookup, 0.003 USDC for Swiss BC-Nummer lookup, 0.002 USDC per IBAN in batch mode, 0.02 USDC for full compliance check. Or use an API key for 200 free requests per month.

Does IBANforge support MCP (Model Context Protocol)?

Yes. IBANforge ships an official MCP server (com.ibanforge/mcp) with 5 tools: validate_iban, batch_validate_iban, lookup_bic, lookup_ch_clearing, check_compliance. Install in Claude Desktop, Cursor, Cline or any MCP-compatible client via npx or streamable-HTTP at https://api.ibanforge.com/mcp.

Does IBANforge support x402 for autonomous AI agents?

Yes. Every paid endpoint accepts x402 micropayments in USDC on Base L2. Agents discover pricing via /.well-known/x402, pay autonomously and call the API without human onboarding. Listed on Coinbase Bazaar discovery.

How many countries does IBANforge cover?

All 84 countries with a standardized IBAN format, including the full SEPA zone, the UK, Switzerland, and most of MENA and Latin America with IBAN coverage.

What is vIBAN detection and why does it matter?

A virtual IBAN (vIBAN) is an IBAN issued by an EMI or fintech (e.g., Wise, Revolut, Mercury, Modulr) that maps to an underlying account at a partner bank. Detecting vIBANs matters for compliance: VoP often fails on vIBANs and EMI exposure changes the risk profile. IBANforge classifies 30+ known issuer prefixes.

Where does the BIC and Swiss clearing data come from?

BIC/SWIFT data: 121,000+ entries from public sources — GLEIF (Global Legal Entity Identifier Foundation, ~38K rows with LEI enrichment), the SWIFT directory, the Deutsche Bundesbank, SIX, the NBP, and EBA Clearing STEP2 SCT. Swiss data: 1,190 BC-Nummern from the official SIX BankMaster CSV — the canonical source used by the Swiss banking industry.

Does IBANforge replace a regulated AML/sanctions screening provider?

No. The /v1/iban/compliance endpoint runs OFAC/EU/UN list checks and produces a risk score (0-100) — useful for triage and pre-flight screening. For regulated AML/CFT obligations use a regulated vendor like Refinitiv World-Check, Acuris or ComplyAdvantage.

How fast is IBANforge?

p99 latency under 50ms for /v1/iban/validate (single IBAN). All databases are SQLite WAL with in-process reads — no external lookups. Batch endpoint scales linearly to 100 IBANs per request.

Is IBANforge open-source?

The MCP server (ibanforge-mcp), the SDK (@ibanforge/sdk) and the OpenAPI spec are open-source on GitHub at github.com/cammac-creator/ibanforge. The hosted API and proprietary issuer classification dataset are commercial.

x402 payments live

IBANforge

Name: IBANforge
Price: 0.005 USDC

The compliance API for AI agents. The only API with Swiss BC-Nummer / QR-IID clearing data — plus IBAN validation, BIC/SWIFT, EMI/vIBAN detection and sanctions risk. Native over MCP and x402, no signup.

Try it free

Everything you need

Swiss clearing — exclusive

BC-Nummer / QR-IID

The only API exposing Swiss SIX BankMaster clearing data: 1,190 BC-Nummern, SIC/euroSIC, QR-IID and institution type. No competitor has this.

MCP-native — agent ready

5 tools, no signup

Native Model Context Protocol server (stdio + HTTP). Claude, Cursor and any MCP agent install in one line: npx -y ibanforge-mcp.

89 countries

IBAN validation

ISO 13616 mod-97 validation with full BBAN structure parsing across 89 countries, including the EU EMI hubs (LT, EE, MT).

121,399 BICs

BIC/SWIFT lookup

121,399 BIC entries (38,761 LEI-enriched via GLEIF) from GLEIF, SWIFT directory, Bundesbank, SIX, NBP and EBA Step2.

EMI / vIBAN

Issuer classification

Detect virtual IBANs and EMIs (Wise, Revolut, N26, Mercury…) — a real compliance signal a mod-97 check can never give you.

Sanctions + FATF

Compliance risk score

Bank-BIC sanctions screening (OFAC/EU/UN/SECO) + FATF + SEPA + VoP reachability, distilled into a 0-100 risk score.

Endpoints & pricing

Pay per request with USDC via x402. Try the /v1/demo endpoint for free.

POST/v1/iban/validate$0.005

Validate a single IBAN

POST/v1/iban/batch$0.002/IBAN

Validate up to 100 IBANs

GET/v1/bic/:code$0.003

Lookup BIC/SWIFT code

POST/v1/iban/compliance$0.02

Full compliance check: sanctions, SEPA Instant, VoP, risk score

GET/v1/ch/clearing/:iid$0.003

Swiss BC-Nummer lookup (1,190 SIX entries)

Quick start

Get 200 free requests/month with an API key, or pay per request with USDC via x402.

bash

curl 'https://api.ibanforge.com/v1/iban/format?iban=CH93+0076+2011+6238+5295+7'

Ready to build?

Integrate in minutes. Pay with USDC — no API key, no subscription.

Start building