Checkout, registration and customer onboarding

Validate IBANs before your form saves them

Give customers a chance to correct incorrect bank details while they are still in your form. Add server-side IBAN validation to checkout, registration or customer onboarding with the IBAN-Test API.

40 countries

Bank-directory checks where source data is available

115 IBAN formats

Country rules, length and check digits

REST API

Authenticated requests and JSON responses

Why this check matters

Return useful feedback at the point of entry

Catch malformed input

Check the country format, expected length and check digits before accepting the submitted IBAN.

Go beyond a checksum

Use available bank-directory data to identify the institution and distinguish format validation from a bank match.

Keep your API token on the server

Call IBAN-Test from your backend and return the result your form needs without exposing the Bearer token in browser code.

From input to a usable result

How the check fits into your workflow

Step 1: Collect the IBAN in your form

Accept the customer input and submit it to your own backend. Formatted IBANs containing spaces are supported by the validation endpoint.

A customer form sends the IBAN to your backend for validation
Your backend keeps the API token private and evaluates the validation response

Step 2: Validate it from your backend

Send a request with your API token. Evaluate the HTTP response and JSON code; HTTP 200 and error:false alone are not proof of valid bank details.

Step 3: Show an actionable result

Ask the customer to correct invalid input. Handle authentication, quota and temporary service errors separately from an invalid IBAN.

Distinguish valid IBANs, invalid input and service errors in your form feedback

See the API in context

A server-side validation step you can put into production

Use the API from the backend stack you already run. Our integration packs provide downloadable examples for several programming languages and tools, including server-side token handling and separate handling for validation and request failures.

An authenticated validation request

curl -X POST "https://www.iban-test.eu/api/v2/iban/validate" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"iban":"DE89370400440532013000"}'

Published reference IBAN for integration examples.

Validation response excerpt

{
  "error": false,
  "code": 2100,
  "message": "IBAN is valid"
}

Illustrative excerpt. Evaluate the complete response and HTTP status.

Treat input errors and service failures differently

For a single IBAN validation, response code 2100 indicates a valid IBAN. Codes such as 3100 identify invalid input. An authentication or quota problem needs a service message, not a claim that the customer entered an invalid account.

Integration packs: PHP · Python / CSV · Excel / Power Query · Google Sheets / Apps Script · n8n · SEPA participation

All integration guides · API documentation

API plans

Choose an API plan for your form traffic

Compare the current API packages and select the allowance that fits your workflow.

Monthly figures are calculated over 30 days. The limit applies per 24 hours.

* Offers only for commercial use, prices excl. VAT.

Before you integrate

Questions about this use case

Can I call the API directly from browser JavaScript?

Keep the Bearer token on your server. Your form should call your backend, which calls IBAN-Test and returns the information needed by the user interface.

Read the authentication and integration documentation

Does a valid IBAN mean the account exists?

No. Formal validity and available bank-directory matches do not confirm account existence, account ownership, account activity or payment eligibility.

What IBAN validation confirms

What should I do when the request limit is reached?

Handle the quota response as a service condition. Do not label the customer IBAN invalid. Pause further checks until quota is available or select an API package with a suitable allowance.

Compare API plans and request allowances

Is there a working integration example?

Yes. Our integration packs cover PHP, Python/CSV, Excel/Power Query, Google Sheets/Apps Script and n8n, plus a SEPA participation example. Choose the pack that fits your application and follow its setup instructions.

Browse all integration packs and examples

Your next integration

Put a bank-data check behind your next form submission

Choose your API allowance, create your access and connect the validation endpoint to your backend.

Choose your API plan