Repeatable software tests
Test IBAN Examples for Software QA
Select a fixed example with a visible source and expected format result. Each country returns the same value, so a failed test can be reproduced. No random bank identifiers or account numbers are created. No upload, no login, no persistent storage.
Two kinds of fixture, with different origins
The GB and NL fixtures contain TEST in the alphabetic bank-code position. BankCodeKit constructed these fixed values to make demonstrations recognizable. The international check digits match the fixture, but TEST is not a claim that a banking authority has reserved the value.
The other eight countries use examples already documented in our country references from Swift IBAN Registry Release 103. Those examples are labeled as registry examples, not as synthetic or guaranteed unused accounts. A public example can resemble an assigned account; keep every fixture outside live payment and onboarding systems.
The catalog does not grant a license to redistribute third-party source documents. See source and reuse boundaries before building a published dataset from external references.
Constructed fixture record
TEST DATA — NOT A PAYMENT INSTRUCTION. The fixed GB fixture is GB43 TEST 1111 1111 1111 11; the fixed NL fixture is NL96 TEST 0000 0000 00. BankCodeKit's regression checks expect both unchanged values to pass the covered national character pattern, length and international checksum. The GB value also appears in the public validation test cases.
A repeatable validation test
- Select the country and save the labeled fixture with your expected result.
- Use the printed form to test spaces and the compact form to test field length. Record which normalization your application permits.
- Expect the country length, covered national character pattern, and MOD97 checksum to pass for the unchanged fixture.
- Compare a failing case from the public test cases with the positive case. A changed check digit should produce a checksum error, while a letter in a numeric-only segment should produce a structure error.
- Keep fixtures in an isolated test environment with payments and live onboarding disabled.
A single fixture per country cannot exercise every account length, local bank convention, or domestic check-digit rule. Add application-specific negative cases and provider sandbox cases separately; record their origin and expected outcome.
Copying keeps the test label
The copy action requires acknowledgment and includes TEST DATA — NOT A PAYMENT INSTRUCTION, the value, and its source. If an automated parser needs only the IBAN field, extract it inside your isolated test harness while retaining the label in the fixture record. Do not remove the label from screenshots, demonstrations, or shared examples.
What changed from the earlier generator?
On 3 October 2026, the random generator was replaced by this finite catalog. The existing page address is retained, but quantity selection and random generation have been removed. Repeating a selection returns the same example. See the change record.
Can these examples be used for payments?
No. Use them for software testing, form QA, and demos only, never real invoices, payouts, direct-debit mandates, customer records, or account registration. A format pass cannot confirm account existence, account ownership, bank reachability, fraud risk, sanctions status, or payment success.
Test example sources
Public references for fixed IBAN examples are linked below; detailed standard scope, review methods, and licensing boundaries are documented on the Sources and Updates page.
IBAN lengths, 15 national patterns and examples. Reference data reviewed: 2026-10-01. Next scheduled data review: 2027-01-01. Sources: Swift IBAN Registry Reference data is reviewed periodically. BankCodeKit does not perform live bank, account, sanctions, or payment-network confirmation.