Payment Test Data Generator

  • 85 IBAN countries + India, US, Canada & more
  • Runs entirely in your browser

Generate structurally valid dummy IBANs, BICs, bank & branch codes, account numbers and test card numbers for testing payment flows. Pick a country and the tool builds one consistent record, broken out into the fields a real system actually reads — each one labelled by exactly which check it passes, so you know what will survive a strict validator and what won’t. Nothing you generate is uploaded or stored; every value is computed locally.

Why your test IBAN can pass one check and fail another

A payment identifier can be valid at two very different levels, and most confusion in testing comes from mixing them up:

  • Structure & check-digit valid — the value is the right length for its country, uses the right character pattern, and its check digits are mathematically correct. This is pure arithmetic: mod-97 for IBANs, Luhn for cards, national schemes for some account numbers. Everything this tool generates is valid at this level.
  • Directory valid — the identifier points at a real registered institution: the BIC exists in SWIFT’s directory, the bank and branch codes appear in a national master list. Confirming this needs licensed reference data, so generated values are never directory-valid. That is why every record here is marked directory —.

So if you paste a generated German IBAN into a strict checker, the IBAN check digit passes but you may see “account check digit not correct” and “the bank cannot be identified”. That is expected: the tool labels each field so you can feed whichever one your system under test actually validates.

Countries that don’t use IBAN

Not every country uses IBAN. India, the United States, Canada, Australia, China, Japan and others use their own national formats — IFSC, ABA routing numbers, BSB, CNAPS and so on. Those are in the Non-IBAN group of the dropdown, decomposed into their own fields. Where the scheme has a real check digit (the US routing number and Mexico’s CLABE), it is computed correctly; the rest are structure-valid.

What you can generate

  • IBANs for all 85 countries in the ISO 13616 registry, with correct mod-97 check digits and country-specific BBAN structure.
  • The decomposed bank code, branch code and account number from each IBAN.
  • Format-valid BIC / SWIFT codes.
  • National account formats for 11 non-IBAN countries (India, US, Canada, Australia, New Zealand, China, Japan, Hong Kong, Singapore, South Africa, Mexico).
  • Luhn-valid test card numbers across Visa, Mastercard, Amex, Discover, JCB, Diners and RuPay.
  • An IBAN validator that checks length, country and mod-97.

Frequently asked questions

Is a generated IBAN a real bank account?

No. It is structurally correct and passes the mod-97 check, but it is not tied to any real bank or account and must never be used for a real transfer. It is for sandbox and unit testing only.

Why does iban.com say the account check digit is not correct?

Some countries carry an extra check digit inside the account number (Germany, Spain, Belgium, Norway and others). Computing it needs bank-specific rules — in Germany, one of roughly 150 methods selected by the real bank code — so this tool fills that position without computing it. The IBAN-level mod-97 is always correct; the tool flags the countries where this inner check applies.

Can I use these as test cards in a payment gateway?

The card numbers pass the Luhn check and use real network prefix ranges, but they are random and unissued. For a specific gateway sandbox, prefer the processor’s own published test cards (Stripe, Adyen and so on), because those trigger scripted behaviour.

Does anything I generate get sent to a server?

No. The whole tool is JavaScript running in your browser. Nothing is uploaded, logged or stored.