Your product touches IBANs. We keep them clean.
ERP, accounting, payroll or banking software: embed registry-grade IBAN validation at input time, so your customers' payments stop failing at payment time. One REST API, machine-readable errors, no bank account data stored.
Structured addresses: 14 and 15 November 2026
On 14 November 2026 the Swiss Payment Standards 2026 come into force, and SIX states that payments which do not meet the structured-address rules can no longer be processed. On 15 November 2026 the EPC schemes (SCT, SCT Inst, SDD) accept structured and hybrid addresses only, and the country element becomes mandatory as soon as one agent sits in a SEPA country outside the EEA, which is Switzerland. Every invoicing, accounting or ERP product that emits a payment file is concerned. Since 27 August 2026 Swift has deferred its own November 2026 date for cross-border messages without setting a new one; SIX and the EPC had not changed anything on 2 September 2026.
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.
Where it sits in your product
Your software
A user types an IBAN or an address: supplier onboarding, payroll master data, payment entry, invoice emission.
IBANforge pre-check
Structure (89-country registry), issuing bank identified (121k+ BICs), rails (SEPA / SIC / instant), risk flags, address conformity: one call, p99 under 50 ms.
At payment time
Fewer rejected files in November, fewer VoP rejections, fewer manual repairs, fewer support tickets with your name on them.
Three reasons vendors pick IBANforge
The deepest Swiss clearing data in a public API
1,100+ SIX BankMaster entries with SIC / euroSIC / instant participation and QR-IID handling, refreshed monthly, plus an ISO 20022 postal_address on every institution we can serve one for, and 121k+ BICs (39k+ LEI-enriched via GLEIF). If your users pay Swiss suppliers, this is the difference.
Swiss clearing docs →Compliance pre-check built in
Sanctions screening (OFAC, EU, UN), FATF lists, SEPA reachability and VoP-requirement data, risk score 0 to 100: one endpoint to triage before a payment leaves your product.
Compliance docs →A trust pack you can send to procurement
Signable DPA, published terms and privacy policy, live status page, versioned changelog. IBANs are never stored: validation runs in memory and only country + bank-prefix metadata is logged. And when a customer leaves, their telemetry deletes itself: erased by default 30 days after termination, contractually (DPA clause 4.7).
Legal & DPA →Licensing that matches how you ship
From $149 per month
One key at 50,000 requests per month, redistribution rights, a written SLA (99.5%), EU invoicing, a named support contact. Above 50,000 requests a month, one conversation sets the volume price.
Embedding IBANforge inside your own product, for your own customers, takes more than a metered key. That is the OEM agreement, and its starting price is public because every other vendor in this market hides theirs.
support@ibanforge.comOne email: tell us what you ship and to whom. Under 10,000 requests a month and no SLA needed? The Pro plan at $29 a month is self-service, on the pricing page.
Read the SLA →