BankCodeKit

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.

Written and maintained by BankCodeKit. Content review: .

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 - Reference information for IBAN structure, country support, and format rules. Local IBAN data reviewed 2026-07-17 against Swift IBAN Registry Release 102 - Jun 2026.

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.

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-07-17 against EPC List of SEPA Scheme Countries v8.0, issued 2025-12-24.

Review Dates

  • IBAN reference review: 2026-07-17, against Swift IBAN Registry Release 102 - Jun 2026
  • BIC visible-format reference review: 2026-07-17
  • Next scheduled shared reference review: 2026-10-17
  • SEPA country data review: 2026-07-17, against EPC List of SEPA Scheme Countries v8.0, issued 2025-12-24

Review cadence: quarterly, and sooner when Swift or EPC publishes source updates.

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 the shared review date only after the compared fields and public examples have been checked.
  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.