Validate a European IBAN and enrich it with bank, compliance and routing data
Validate a European IBAN and enrich it with bank, compliance and routing data. Use whenever the user mentions an IBAN, a bank account, a SEPA payment or asks who the bank is. Returns: valid, country, BIC/SWIFT, bank name, EMI/vIBAN flag, SEPA + VoP reachability, risk score, Swiss bc_nummer for CH/LI. Production · server processing <5ms (network excluded — measure your own round trip on GET /ping) · 121,000+ BICs (39,000+ LEI via GLEIF) + 1,100+ SIX · v1.5.0.
Answers HTTP 200 without x402 payment termsour last check, 2026-09-24
0 of 1checks answered this week
n/amedian answer time
$0.005listed price per call
n/aprice it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
POST https://api.ibanforge.com/v1/iban/validate
| Category | Company and compliance |
|---|---|
| Provider host | api.ibanforge.com |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 2 from 1 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-09-24 | no x402 terms | 200 | 902 ms |
Example input (from the provider)
{
"body": {
"iban": "CH1000230000000012345"
},
"bodyType": "json",
"discoverable": true,
"method": "POST",
"schema": {
"properties": {
"iban": {
"description": "IBAN to validate (spaces and lowercase accepted).",
"maxLength": 34,
"minLength": 15,
"type": "string"
}
},
"required": [
"iban"
],
"type": "object"
},
"type": "http"
}
Promised output schema (from the provider)
{
"properties": {
"input": {
"properties": {
"method": {
"enum": [
"POST"
],
"type": "string"
}
},
"required": [
"method"
]
}
}
}