Full IBAN compliance check

Swiss clearing enrichment from the SIX BankMaster directory — present for CH and LI IBANs only, and included at no extra cost in the 0.005 USDC validation. Full rail participation, not just a name lookup.

Served inside POST /v1/iban/validate when a reference was supplied. Carries TWO independent verdicts: valid (the reference checksum) and pairing (whether it may legally travel with this account). A reference can be arithmetically valid and still illegal on that IBAN, and the reverse. Each verdict names its own document.

SEPA compliance details. Only present when the IBAN is valid and the country participates in SEPA.

Issuer classification for the institution behind the IBAN. Useful for vIBAN detection and KYC enrichment. Present when the IBAN is valid and either the BIC resolved or an official register names the holder of the bank code (see psd_registration).

The EBA's PSD2 register of payment and electronic money institutions naming the holder of this bank code. Joined on country + national reference code, and served ONLY for countries where that code was measured to be the one the IBAN actually carries — today Spain alone. The register carries no BIC and no LEI, and in 29 of its 30 countries it files authorisations under a company or tax number from an unrelated register (a Polish NIP, a French SIREN, a Dutch DNB reference), so joining those to a bank code would attach a real institution's authorisation to an unrelated bank. Absent on a miss: there is no negative form, because the register's own disclaimer states that an institution omitted from it is authorised all the same.

AML/CFT risk indicators derived from the IBAN structure, issuer type, and country. Designed for compliance pre-screening and fraud prevention workflows. Only present when the IBAN is valid.

Separate verdict on the BBAN bank code. valid answers ISO 13616 (structure + mod-97) and says nothing about whether the bank code identifies an institution; this field answers that, and states how much weight the answer carries. Present only when the IBAN is valid.

The official identity a central bank publishes for the institution behind the code we resolved: legal name, LEI, registered address, and the publisher's own category. Sources: the European Central Bank's daily list of monetary financial institutions (reached by LEI, and by the five-digit French code banque, which is what a French RIAD code contains), and the Banco de España's list of Spanish MFIs (reached by the four-digit supervisory code it publishes bare). PURELY INFORMATIONAL. It never changes valid and never changes bank_code_check — neither publisher allocates bank codes, both relay what national authorities report, and the Banco de España's terms forbid presenting its data as having legal or evidentiary effect. Present only on a match: an institution absent from a list produces no block at all, never a negative one, because absence from these lists is not evidence about the institution. Both publishers permit this reuse on conditions that travel with the data, which is why source, free_of_charge and as_of are always present.

UK modulus check on the sorting code and account number a GB IBAN carries — present for GB only, and included at no extra cost in the 0.005 USDC validation. A second checksum, independent of mod-97: the IBAN check digits prove the string was transcribed correctly, this proves the pair is one the owning institution could have issued. A GB IBAN can pass mod-97 and still name an account no bank could have opened, which is what this catches before a payout. passed false NEVER makes the IBAN invalid — read valid and modulus_check.passed as two separate facts. Checksum only: it does not say the account exists, name its holder, or resolve a bank from a sort code.

Ordered advice derived from THIS result: what blocks a payment first, what merely enriches it after. Branch on code, never on the prose. Absent or empty for an IBAN that failed validation, since the error already says what to do.