Check IBANs when your users enter them.
Add IBAN validation and bank/BIC lookup to supplier onboarding, invoicing and payroll workflows across supported countries. Inspect the API response, then connect your software using the documentation.
Start without an account or sales call. No API key is needed to try IBAN validation in the playground.
From your first response to your integration
See a real response
Run an IBAN check in the playground. Inspect the validation result and the bank, BIC and SEPA information available for that country.
Try the APIConnect your workflow
Follow the first-call guide, then use REST or an available SDK. Odoo 18 requires custom modules; the n8n guide covers self-hosted installations.
Follow the integration guideChoose your key and plan
Get a free key to continue. Credit packs and Pro are available from the pricing page; choose according to your usage.
Compare plans and pricesWhere it sits in your product
Your software
A user enters an IBAN in a supplier record, payroll form or payment screen. Check it before saving it or creating a payment file.
IBANforge pre-check
Check the IBAN structure and checksum, then use the bank, BIC and country information available from the registers. Address and compliance checks have their own endpoints.
At payment time
Show the error to the user and correct the source data. A valid IBAN does not establish who owns the account or guarantee a successful transfer.
What your integration can use
Documented registers, country by country
IBAN validation, bank codes, bank names and BICs where the sources provide them. Check the documented coverage and source dates for your markets. Swiss payments also have SIX clearing data, QR-IIDs and SIC/euroSIC participation.
IBAN validation documentation →Bank-level risk indicators
The compliance endpoint screens the resolved bank BIC against OFAC, EU, UN lists and returns country-risk and SEPA indicators. Use these for an initial check alongside your own controls; they do not verify the account holder.
Compliance docs →A trust pack you can send to procurement
Signable DPA, published terms and privacy policy, live status page, versioned changelog. Validation stores no IBAN: it runs in memory and only country + bank-prefix metadata is logged. The file audit is a separate deliverable: it keeps its report — which reproduces the columns you upload — for 2 hours unpaid, 24 hours after payment, then deletes it (see the Audit page). And when a customer leaves, their telemetry deletes itself: erased by default 30 days after termination, contractually (DPA clause 4.7).
Legal & DPA →Structured addresses: Switzerland, EPC and Swift have separate timetables
Checked on 10 September 2026: SIX publishes 14 November 2026 as the deadline for the Swiss Payment Standards address requirements, for payment orders from the customer to its bank. We no longer print a countdown: the other timetables have moved. On 9 September, the EPC postponed the end of unstructured addresses under all five payment schemes beyond 15 November; it plans to set the new date in October. Swift also deferred its payments changes on 27 August, with an update by December at the latest. The EPC and Swift announcements do not themselves change the Swiss timetable. Continue preparing your supplier data against the rules of the rail you use.
Two things this API does about it, both already live. A free conformity check tells you, rule by rule and with the document each rule comes from, whether an address you have structured passes a given rail. And resolving a clearing code or an IBAN into a BIC often removes the agent-address obligation altogether: hold the BIC, and that branch of the rule does not apply to you.
Holding a QR-bill? Check whether its address is structured or combined, free.
Which date is THE date? The state of every rail, with sources.
curl -X POST https://api.ibanforge.com/v1/address/check \
-H "Content-Type: application/json" \
-d '{"scheme":"sps","address":{"ctry":"ch",
"adr_line":["Bahnhofstrasse 45","8001 Zurich"]}}'
{ "conforms": false,
"findings": [ { "rule": "twn_nm_required", "verdict": "fail" },
{ "rule": "ctry_iso3166", "verdict": "fail" } ] }curl -X POST https://api.ibanforge.com/v1/address/check \
-H "Content-Type: application/json" \
-d '{"scheme":"sps","address":{"strt_nm":"Bahnhofstrasse",
"bldg_nb":"45","pst_cd":"8001","twn_nm":"Zurich","ctry":"CH"}}'
{ "conforms": true, "findings": [ ... all "pass" ... ] }What it does not do: it does not migrate your customers' address book, and it does not parse free text into a structured address. It checks what you have structured, for free, and it names the document behind every verdict.
And Verification of Payee. Since 9 October 2025, euro-area payment service providers must verify payee details before a credit transfer. Version 1.1 of the EPC rulebook takes effect on 20 September 2026; it is a technical milestone, not a new obligation. IBANforge is not a VoP service (the EPC scheme is reserved to regulated PSPs): a pre-check at input time removes what VoP would reject later, and sepa.vop_participant tells you whether the resolved institution is listed as ready.
Need specific service commitments?
From $149 per month
One key at 50,000 requests per month, the right to embed the API in your own product for your end customers, a written SLA (99.5%), EU invoicing, a named support contact. Above 50,000 requests a month, one conversation sets the volume price. Reselling raw bulk extracts of the databases stays out of scope (Terms, article 6).
Ordinary API integration can start on Pro. Discuss OEM if you need to embed the API in your product for your end customers, a written SLA, tailored support or volumes beyond the published plans.
support@ibanforge.comDescribe your product and the commitments you need. Pro, at $29 per month for 10,000 requests, is available directly from the pricing page.
Read the SLA →