Supplier onboarding and accounts payable

Check supplier IBANs before your next payment run

Catch incorrect IBANs when a supplier is created or their bank details change. Connect IBAN-Test to your ERP or accounts payable workflow and return validation results with available bank details.

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

Catch avoidable bank-data errors while there is time to correct them

Check new and changed bank details

Validate country format, length and check digits when a supplier record is created or updated.

Add the bank behind the IBAN

Where directory data is available, return the institution, city and BIC alongside the validation result.

Make review decisions explicit

Route invalid input and incomplete bank matches for review before the data moves into a payment workflow.

From input to a usable result

How the check fits into your workflow

Step 1: Capture the supplier IBAN

Run a check at supplier onboarding, when bank details change or when you prepare an exported payment list. Keep your supplier confirmation process in place.

Capture a new or changed supplier IBAN before saving
Your backend sends the IBAN to the API and receives a JSON validation result

Step 2: Call the API from your system

Send the IBAN with your server-side API token. The response combines format validation with available bank-directory information.

Step 3: Return the result to your workflow

Use the response code and available details to request corrections, flag exceptions or continue your internal approval process.

Continue internal review for a valid IBAN or request a correction for invalid input

See the API in context

One validation step for your supplier-data workflow

Use the same API from an ERP integration, a supplier portal or a script that checks exported records. Handle each result in the system your team already uses.

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.

Keep bank identification separate from supplier approval

A bank-directory match helps identify the institution. A valid IBAN does not prove that the account belongs to your supplier or is active. Confirm changed payment instructions through your established supplier verification procedure.

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

All integration guides · API documentation

API plans

Choose API capacity for your supplier checks

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

Does this verify that an account belongs to my supplier?

No. IBAN-Test validates formal IBAN characteristics and available bank data. It does not verify the account holder, account activity or the authenticity of changed payment instructions.

Can I check an exported supplier list?

Yes. Your integration can submit IBANs individually and write the results back to your system. We provide integration packs for several programming languages and tools: PHP, Python/CSV, Excel/Power Query, Google Sheets/Apps Script and n8n, plus a SEPA participation example. Each validation consumes an API request.

Browse all integration packs and examples

Which bank details can the API return?

For 40 countries, bank-directory checks can return an institution, city and BIC where the source data is available. Format and check-digit validation cover the supported IBAN formats.

See all 40 countries with bank-directory checks

How should I handle an incomplete result?

Evaluate the HTTP status, JSON response code and available details separately. A missing bank match or an unknown SEPA status should follow your review policy rather than being treated as account approval.

Your next integration

Add IBAN validation to your supplier workflow

Choose the API allowance that fits your checks and integrate the result into supplier onboarding or payment preparation.

Choose your API plan