Stop smashing your keyboard to pass "IBAN Validation" in tests 😅

Hey DEV community! 👋

If you've ever built a fintech app, an e-commerce checkout, or any form that requires bank account details, you know this struggle.

You're in the staging environment, trying to test the "Add Payment Method" flow. You reach the IBAN field. You don't want to use real data (obviously). So you do the "developer smash":

DE99 1234 5678...

Form: 🚫 Invalid IBAN format.

Ugh. You try again.

Form: 🚫 Checksum validation failed.

Suddenly, a 2-minute UI test turns into a 20-minute hunt for a working dummy string on Google.

Why Random Numbers Don't Work 🧮
The problem is that an IBAN isn't just a random string. It’s a structured format defined by ISO 13616, and it relies on the Modulus 97-10 algorithm for checksums.

If the first two "check digits" don't mathematically match the rest of the bank code, any decent validation library (backend or frontend) will reject it immediately.

Why should we, as developers, waste brainpower manually calculating checksums just to run a simple test?

So, I built a thing to fix it 🛠️
I got tired of dealing with bad test data, so I built a simple, no-nonsense tool to generate valid test IBANs on the fly.

Introducing 👉 RandomlyIBAN.com

It's designed specifically for developers and QA folks.

What it does:
✅ Generates mathematically valid IBANs (passes Mod-97).
✅ Supports country-specific formats (e.g., a 18-char NL IBAN or a 22-char DE IBAN).
✅ No sign-up, no BS. Just grab the data and get back to coding.

Try it out
Next time you get stuck on an IBAN validation error in your dev environment, give it a try.

Where do you usually get your test data from? Let me know if this is useful for your workflow or if there are any specific country formats you'd like me to add!

Happy testing! 🚀