A supplier file checked once drifts. Between the 1 July, 1 August and 1 September 2026 editions of the registers behind IBANforge, BICs appeared and disappeared, institutions were renamed, Swiss clearing numbers moved. The counts, register by register, and what they mean for a creditor file.
Every German IBAN carries an eight-digit Bankleitzahl. The Deutsche Bundesbank publishes the register that allocates them, monthly, with the institution and its BIC, and it is the only national register that also publishes the end of a code. What each answer means at payout time, and what it cannot tell you.
A vendor master with thousands of IBANs, some without a BIC, some pointing at bank codes that no longer exist, and a new system that refuses incomplete records. How to triage it in batches of 100, what each field decides, what it costs, and where an IBAN check has to hand over to the supplier.
Verification of Payee has been mandatory for euro-area payment service providers since 9 October 2025, and version 1.1 of the EPC scheme rulebook takes effect on 20 September 2026. What an IBAN check does before the name match, what it cannot do, and the data work worth finishing before the date.
Since 9 October 2025, banks in the euro area must check that a payee's name and IBAN belong together before every credit transfer. Swiss banks do not have to, Liechtenstein banks not yet. What that means for a Swiss company that pays or receives euros, with the document and the sentence behind every statement, as of 2 September 2026.
Four dates circulate for the end of unstructured postal addresses in payments. On 27 August 2026 Swift suspended its own. SIX, the Eurosystem and the EPC have not moved. Fedwire and the Bank of England point at 2027. Here is the state of each rail, with the document and the sentence behind every date.
November 2026 is real: SPS 2026 takes effect on the 14th, Fedwire follows on the 16th, and the last SIC release accepting unstructured addresses closes on the 20th. What the rules actually require is smaller than the panic suggests — and the specs themselves name the escape hatch. We shipped two things for it: a structured postal_address block on BIC answers, and a free conformity checker.
A lookup that returns a bank name has done a quarter of the job. What a serious BIC/SWIFT lookup answers — the legal entity behind the name, the address with its filing date, the shared BIC8 counted rather than guessed, the regulatory authorisation where one exists — with real captured responses.
The mod-97 checksum is the same few lines of code in every product on the market, so it cannot be the thing you buy. Six criteria that genuinely separate IBAN validation APIs, what IBANforge answers on each, and the two where our answer is deliberately narrower than it could be.
The ABA check digit takes ten lines of code and we give you the algorithm with a worked example. The honest part comes after: most non-IBAN bank code systems have no check digit at all, so real validation means a register — and every register in this space has licence terms that decide what a data product may ship.
UK PRA authorisation status is now part of every GB lookup — joined by LEI, bounded to the UK, and served with the attribution the Bank asked for. Also new: a Swiss QR-IBAN reference page, and a 402 that finally shows the way in.
IBANforge sat in the API Evangelist catalog since May with close to the worst score the instrument can produce, bulk-imported and never fetched. Then we submitted ourselves, Kin Lane re-read everything by hand, two of his findings shipped as fixes the same day — and the third cut the other way.
BE68 5390 0754 7034 and CH93 0076 2011 6238 5295 7 pass every checksum and appear in thousands of tutorials. The Belgian national register marks code 539 as unavailable, and the Swiss BankMaster has no institution 762 at all. What checksum validation actually proves — verified against both registers, reproducible with two public files.
The QR-IID in a Swiss QR-IBAN sits in the 30000–31999 range and is not the bank's regular clearing number. How to resolve a QR-IID into the issuing institution, its BIC and its payment-rail participation, with real examples and one API call.
Verification of Payee (VoP) is the EU's mandatory pre-payment name check for SEPA credit transfers. What it is, the dates that matter under Regulation (EU) 2024/886, what payment service providers must do, and where IBAN validation fits.
ibanforge.com is now served by a single Next.js codebase built for AI agents (70%) and developers (30%). New /agents page, OpenAPI reference, and a critical fix that lets agents auto-fall-back to x402 when their free quota runs out.
GET /v1/iban/format — a new free endpoint that runs the mod-97 + structure check without touching the BIC, SEPA, VoP, sanctions, or Swiss BC-Nummer databases. Use it to pre-filter malformed IBANs before paying for the full enrichment.
pip install ibanforge — sync + async Python clients for the IBANforge API, with typed exceptions, automatic x402 fallback when the free quota runs out, and one-line API key generation. Built for fintech and AI agents.
IBANforge gets a redesigned dev-first landing page with structured data, OG images, interactive compliance demo, dual pricing paths, and persistent storage for API keys.
IBANforge now returns SEPA membership, issuer classification, risk indicators, and VoP data with every IBAN validation — plus full French and German language support.