Test data for developers

Test IBANs: examples and test cases for your software

Need a test IBAN for the UK or another country? Use these published examples with the correct country format and MOD-97 checksum, plus deliberately invalid variants for form and software tests.

Reference example from the SWIFT IBAN Registry. Use it for development, tests and documentation; do not create payment instructions from it. Formal validity confirms neither account ownership nor the existence of an active account.

Example IBANs for the UK and other countries

These 6 reference values come from the SWIFT IBAN Registry, release 101. Country format, length and checksum were recalculated locally on 15 October 2026. Copying gives you the electronic format without spaces.

Published reference examples for format and checksum tests
CountryTest IBANCharactersAction
United Kingdom (GB)22
Germany (DE)22
Austria (AT)20
Switzerland (CH)21
France (FR)27
Netherlands (NL)18

A dummy IBAN with a correct checksum does not prove that its bank details are valid. Its bank code could be missing from a current directory, for example. Decide separately whether your application needs format and checksum validation or also bank identification.

Test cases for valid and invalid input

These eight cases cover normalization, required fields, length, allowed characters and checksum. The expected result concerns the format after normalization. It is not a guaranteed API status code; implementations may run checks in a different order.

Test cases derived from the UK reference example
Test caseInputExpected form-test result
UK reference exampleGB29NWBK60161331926819Formally valid after normalization
Remove spaces during normalizationGB29 NWBK 6016 1331 9268 19Formally valid after normalization
Normalize lowercase lettersgb29nwbk60161331926819Formally valid after normalization
Checksum deliberately changed to 00GB00NWBK60161331926819Invalid checksum
One character missingGB29NWBK6016133192681Invalid length
One extra characterGB29NWBK601613319268190Invalid length
Invalid special characterGB29NWBK6016133192681!Invalid character
Required field empty(empty)Required field missing

Downloads are generated in your browser from these fixed examples and need no account. You can use the files as test fixtures in your project.

Test IBAN, IBAN generator or IBAN validation?

  • Test IBAN: A fixed example for reproducible form and software tests.
  • IBAN generator: Calculates an IBAN from the bank details you enter. Use the IBAN generator.
  • IBAN validation: Checks an existing IBAN and adds available bank information. Use the online IBAN checker.

For sandbox payments, follow your payment provider’s instructions and use its documented test data and test mode. This collection does not define provider-specific successful or failed payment scenarios.

Integrate IBAN validation into your application

Use the IBAN validation API to automate checks in forms, shops or ERP workflows. The test cases on this page describe format expectations; the API can apply additional checks.

curl --request POST 'https://www.iban-test.eu/api/v2/iban/validate' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{"iban":"GB29NWBK60161331926819"}'

For IBAN validation, 2100 indicates a valid result. A negative validation result such as 3100 can be returned with error: false. Evaluate the result code and handle authentication, quota and technical errors separately. See the API documentation for response details.

Your own API access includes 10 free requests per 24 hours. The examples above remain available without registration.

Frequently asked questions about test IBANs

Is a test IBAN a real bank account?

A published example does not prove that an active account exists. These examples illustrate the format and checksum. Use them only for development, testing and documentation.

Why can a test IBAN be rejected despite a valid checksum?

Your application may apply additional rules, such as a bank-code lookup or a national account check. A sandbox may also accept only specific test values. Passing MOD-97 alone does not cover those requirements.

How do I test spaces and lowercase letters?

Normalize input according to your application’s rules. The variants GB29 NWBK 6016 1331 9268 19 and gb29nwbk60161331926819 should produce the same reference value after removing spaces and converting letters to uppercase.

Sources and verification

Reference values and country formats: SWIFT IBAN Registry, release 101 (December 2025). These 6 values were checked locally for format and checksum on 15 October 2026. Negative cases were derived for this collection. For sandbox test data, see the Adyen developer documentation.

Bank data validation

Bank directory checks for 40 countries

IBAN-Test goes beyond checksum-only validation. For these countries, we check the bank identifier against available bank directories and return bank details such as institution, city and BIC when available. See how IBAN validation works.

ALAlbania ADAndorra ATAustria BEBelgium BGBulgaria HRCroatia CYCyprus CZCzech Republic DKDenmark EEEstonia FIFinland FRFrance DEGermany GIGibraltar GRGreece HUHungary ISIceland IEIreland ITItaly LVLatvia LILiechtenstein LTLithuania LULuxembourg MTMalta MDMoldova MEMontenegro NLNetherlands MKNorth Macedonia NONorway PLPoland PTPortugal RORomania SMSan Marino RSSerbia SKSlovakia SISlovenia ESSpain SESweden CHSwitzerland VAVatican City

IBAN syntax check

Format checks for 115 IBAN formats

Check IBANs for a valid structure, correct length and checksum. This helps you catch typos and transposed digits before a payment fails. Additional bank validation against real bank directories is available for the countries listed above.

MCP Server for AI Agents – Connect AI clients to IBAN validation tools – https://www.iban-test.eu/mcp – API documentation