Detect invalid lengths, wrong country formats and failed IBAN check digits before payment data is saved.
IBAN validation API
IBAN validation API for forms and payment workflows
Catch mistyped IBANs before they reach your checkout, customer database or payment files. Check format and check digits, look up available bank and BIC data, and return a JSON result your application can act on.
Start with 10 free API requests every 24 hours. Use your own API token for REST integrations and MCP. Choose a higher-volume plan when your workflow needs more checks.
Built for forms, SaaS products and payment workflows
IBAN validation is most useful before a customer submits a form, before SEPA data is stored and before payment files are generated. The API lets you run the same checks automatically in your own application.
For supported countries, return bank details such as institution, city or BIC when directory data is available.
Integrate IBAN checks into onboarding, checkout, ERP, accounting and back-office processes.
See what one IBAN check returns
Create a free account, sign in and copy your token from the API overview. Replace YOUR_API_TOKEN in this request with your token, then run it from your terminal or backend.
Example request
curl --get 'https://www.iban-test.eu/api/v2/iban/validate' \
--header 'Authorization: Bearer YOUR_API_TOKEN' \
--data-urlencode 'iban=DE89370400440532013000'Example JSON response
{
"error": false,
"code": 2100,
"details": {
"bankName": "Commerzbank",
"bankCity": "Köln",
"bic": "COBADEFFXXX",
"sepa": {
"sddCore": {
"status": "confirmed",
"reason": "matched"
},
"sddB2b": {
"status": "confirmed",
"reason": "matched"
}
}
}
}Abbreviated response for the published German example; omitted fields are documented in the API reference. Available bank details and SEPA statuses depend on the bank and country. Check HTTP status, error and code; code 2100 with error: false confirms a valid IBAN result.
A formally valid IBAN does not automatically prove that an account exists or can receive payments. IBAN-Test helps reduce avoidable input and plausibility errors before submission.
Check bank participation in four SEPA schemes
IBAN validation also returns the bank’s participation in credit transfer, instant credit transfer and direct debit schemes, checked against the EPC participant registers.
sct – credit transfers; sctInst – instant credit transfers; sddCore – Core direct debits; sddB2b – B2B direct debits.
All four schemes are checked independently. confirmed means there is an unambiguous, current register match. unknown means participation could not be confirmed; it does not mean the bank does not support the scheme.
This checks bank participation, not live account reachability. It does not confirm account existence or payment eligibility, a mandate, or the success of a payment.
Start with an integration that fits your workflow
Use a downloadable starter and follow the setup instructions. Each guide explains authentication, request limits and how to distinguish invalid bank details from a failed check.
- IBAN validation in PHP form — Validate customer input on your server.
- IBAN validation in CSV with Python — Check exported IBAN lists and write a result CSV.
- IBAN validation in Google Sheets — Check selected spreadsheet rows without changing the input.
- IBAN validation in n8n workflow — Route validation results into your automation.
