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.
VoP rulebook v1.1 — 20 September 2026
Since October 2025, euro-area banks must verify payee details before a credit transfer (Verification of Payee). Payments carrying mistyped or non-existent IBANs now fail loudly — at the worst possible moment. IBANforge is not a VoP service (the EPC scheme is reserved to regulated PSPs), but a pre-check at input time removes what VoP would reject later: broken structure, unknown bank, unreachable rails.
The honest pitch: pre-check now, so VoP has nothing to reject.
Where it sits in your product
Your software
A user types an IBAN — supplier onboarding, payroll master data, payment entry.
IBANforge pre-check
Structure (89-country registry), bank exists (121k+ BICs), rails (SEPA / SIC / instant), risk flags — one call, p99 under 50 ms.
At payment time
Fewer VoP rejections, fewer manual repairs, fewer support tickets with your name on them.
Three reasons vendors pick IBANforge
Swiss data nobody else exposes
~1,200 SIX BankMaster entries with SIC / euroSIC / instant participation and QR-IID handling, refreshed monthly — plus 121k+ BICs (38k+ 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–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.
Legal & DPA →Licensing that matches how you ship
Embedding IBANforge inside your own product, for your own customers, takes more than a metered key: redistribution rights, a written SLA, EU invoicing, a named support contact. That is the OEM agreement — no public price list, one conversation.
support@ibanforge.comOne email — tell us what you ship and to whom.
Read the SLA →