Test IBAN Numbers for Development: Sample IBANs for Every Country

Building a payment form, writing unit tests, or integrating with a banking API? You need test IBANs — numbers that pass validation but will not accidentally trigger real transactions.

Using real IBANs in development is risky:

• A misconfigured staging environment could initiate real transfers
• Real IBANs are personal financial data covered by GDPR and PCI requirements
• Storing real banking data in dev environments violates most security policies

Sample Test IBANs by Country

All of these pass standard IBAN validation:

Western Europe

Northern Europe

Eastern Europe

Need test IBANs for countries not listed here? Use our random IBAN generator to create valid test numbers for supported countries instantly.

How Test IBANs Are Generated

The process involves four steps:

1. Pick a country — determines the IBAN length and format
2. Choose a bank code — use a real bank code format for realistic testing
3. Generate an account number — random digits matching the country's length
4. Calculate check digits — using the MOD-97 algorithm

For a detailed explanation, see our IBAN validation guide.

Unit Testing with IBANs

Your test suite should cover:

Valid cases:

• DE89370400440532013000 ✓
• GB29NWBK60161331926819 ✓
• FR7630006000011234567890189 ✓

Invalid cases:

• Wrong check digits: DE00370400440532013000 ✗
• Invalid country: XX89370400440532013000 ✗
• Incorrect length ✗
• Empty string ✗

Edge cases:

• IBANs with spaces
• Lowercase letters
• Mixed formatting

Payment Provider Test IBANs

When testing with payment APIs, use their designated test IBANs:

• Stripe: DE89370400440532013000 (success), DE62370400440532013001 (failed charge)
• Adyen: NL13TEST0123456789 (success), NL36TEST0236169114 (refused)

Always check your provider's documentation for specific test behaviors.

Form Testing Checklist

Best Practices

Do:

• Use structurally valid test IBANs
• Test multiple countries (not just German IBANs)
• Test edge cases: shortest (Norway, 15 chars) and longest (Malta, 31 chars)
• Separate test and production environments
• Document test IBANs in a shared test data dictionary

Don't:

• Use real IBANs in tests (even your own)
• Hardcode test IBANs in production code
• Assume all IBANs are the same length (15–34 characters)
• Skip country-specific testing
• Use test IBANs from one payment provider with another

Multi-Currency Testing

The golden rule: if you are testing anything that touches bank account numbers, use test IBANs with no exceptions. Generate fresh test IBANs with our Random IBAN Generator.