Sources

Sources and Updates

BankCodeKit uses local reference data and browser-local checks for payment-code formats. This page explains which public references are used and what the tools do not verify.

Independent Reference Website

BankCodeKit is not affiliated with, endorsed by, or certified by Swift, ISO, the European Payments Council, or any bank. Links identify the sources used for review. A source review date records a factual comparison; it is not a certification or a grant of reuse rights. Source documents and trademarks remain subject to their owners' terms.

Swift is a trademark of S.W.I.F.T. SC.

Software And Font Licences

The website uses open-source software and self-hosted fonts. Read the third-party software notices, IBM Plex font licence, and Space Grotesk font licence. These software licences do not grant rights to the external reference documents or datasets discussed on this page.

Reference Scope

BankCodeKit uses public reference information for IBAN structure, visible BIC/SWIFT code format, and country-level SEPA context. The tools use local data in the browser and do not query banks, Swift, payment networks, account directories, sanctions services, or payment providers while checking a value.

IBAN structure and country formats

The Swift IBAN Registry is used for national IBAN length, BBAN composition, bank and branch identifier positions where published, and example/test formatting. It supports the local country reference data and the structure tables on the IBAN format by country pages. It is not queried while a user checks a value.

Swift IBAN Registry - Reviewed 2026-10-01 against Swift IBAN Registry Release 103 - Sep 2026: 89 country prefixes and lengths; the 15 published national patterns and their example IBANs. This does not extend national-pattern coverage beyond those 15 countries.

Release 103 review: what changed here

The Swift registry PDF was published in 2026-09; this is a publication month, not an effective date for every country. BankCodeKit compared the local data on 2026-10-01.

Reviewed scope: 89 country prefixes and lengths; the 15 published national patterns and their example IBANs.

All country lengths and published examples matched. Spain's two national check-digit positions are now represented separately, as in the registry.

The registry's history identifies a Brazil update. BankCodeKit's Brazilian entry still checks the 29-character length and international checksum; a Brazilian national-pattern check is not implemented. This review does not describe a complete field-by-field comparison with Release 102.

Domestic check-digit algorithms, account existence and bank assignment are not checked. Countries without a published national pattern still receive incomplete structure checks.

BIC visible structure

Swift's BIC information is used to document the visible ISO 9362 structure: an eight-character BIC and its optional three-character branch segment. BankCodeKit does not use a licensed BIC directory, so it cannot confirm assignment, active status, institution existence, network connectivity, or branch reachability.

Swift BIC / ISO 9362 information - Reference information for visible Business Identifier Code structure and usage context.

What the ISO standard pages do and do not provide

ISO's public pages identify the current standards and describe their subject: ISO 13616 for IBAN elements and ISO 9362 for BIC elements. National IBAN lengths and BBAN fields still come from the Swift IBAN Registry and the cited national authorities. The public ISO pages are not licensed account or institution directories, and they do not provide assignment, connectivity, ownership, or payment-status results.

  • ISO 13616-1:2020 IBAN structure standard - Verified 2026-08-15. Scope: ISO's current published standard page for the elements and structure of an IBAN; national lengths and BBAN fields remain sourced from the Swift registry and cited national authorities.
  • ISO 9362:2022 BIC standard - Verified 2026-08-15. Scope: ISO's current published standard page for BIC elements and structure; it is not a licensed institution directory or connectivity check.

National IBAN and bank-code references

Each published country page adds a national central-bank, standards-body, or payments-industry source to the shared Swift and EPC references. These links were checked for access and page-specific relevance on 2026-08-15.

SEPA geographical scope

The European Payments Council list is used for country and territory scope in the local SEPA reference. A listing is geographical context, not proof that a specific bank participates in a particular scheme or that an account can receive the proposed payment.

European Payments Council SEPA scheme countries list - Reference information for countries and territories in SEPA scheme scope. Local data reviewed 2026-10-01 against EPC List of SEPA Scheme Countries v8.0, issued 2025-12-24.

Editorial and source review policy

Primary sources are the basis for published rule fields: Swift registry and BIC materials, European Payments Council scope documents, ISO standard pages, and cited national central-bank, standards-body, or payment-industry authorities. A numeric length, structure field, scheme status, or review label is not changed from a search snippet or an uncited summary.

Secondary sources may help locate terminology or a newer official document, but they are not used as the sole basis for local validation rules or country data. The corresponding primary source must be checked before publication.

Unverified fields are not published. Candidate country data remains outside public routes and the sitemap until its structure, example, source notes, limitations, and review date are complete. Conflicts remain unpublished until they can be resolved against an official source and the affected tests pass.

Review Dates

  • IBAN reference review: 2026-10-01, against Swift IBAN Registry Release 103 - Sep 2026
  • Next IBAN field review: 2027-01-01
  • BIC visible-format reference review: 2026-07-17; next review: 2026-10-17. This was not refreshed by the IBAN review.
  • ISO and national source-link verification: 2026-08-15
  • SEPA country data review: 2026-10-01, against EPC List of SEPA Scheme Countries v8.0, issued 2025-12-24
  • Next SEPA field review: 2027-01-01

The SEPA review covered all 57 country and territory rows, their displayed currency codes, and the 41-country grouping. No values needed changing. Bank participation and the historical operational notices were not re-reviewed. Page-copy dates, source publication dates and completed data-review dates describe different work; publishing a new build does not refresh them.

Review cadence: monthly source-update checks, quarterly field-by-field reviews, and sooner when Swift or EPC, ISO, or a cited national payment authority publishes a relevant source update. Dates apply only to the stated review scope.

Reference data is reviewed periodically. BankCodeKit does not perform live bank, account, sanctions, or payment-network confirmation.

Public Test Cases and Change Log

BankCodeKit publishes fixed IBAN, BIC/SWIFT, and SEPA examples with expected local results, plus a data review log showing when format rules and source-backed reference data were checked.

Review the validation test cases and data review log to see the examples, expected fields, source references, and the format-only limitations attached to each case.

Format-Only Limitation

Format checks only. This page does not confirm account existence, ownership, bank reachability, or payment success.

A passed result can still be wrong for a real payment. Always verify real payment details with your bank, payment provider, invoice issuer, or recipient before sending money.

How a reference review is performed

  1. Open the current official source and record its release or issue label.
  2. Compare published country length, BBAN pattern, BIC structure, or SEPA scope with the local data used by the site.
  3. Run the fixed passing and intentionally failing cases on the Validation Test Cases page.
  4. Update only the relevant source-review date after its stated fields and public examples have been checked. Preserve dates for other references.
  5. Keep unpublished candidate countries outside public routes and the sitemap until their reference fields are complete.

Readers can reproduce the review by following the source links above, comparing a country structure page, and running the same synthetic values. Corrections should identify the page and public source without including real payment details.

Corrections And Data Feedback

If a page appears outdated or a format explanation needs review, send the page URL and the public source you are comparing it with. Do not send real IBANs, BICs, invoices, CSV files, account numbers, or other sensitive payment details.