Skip to content
Generate Random IBAN logo

Generate Random IBAN

Produces test IBAN strings that pass the mod 97 checksum for 91 countries, downloadable as CSV, JSON or SQL.

Actively maintained

At a glanceswept Oct 23, 2026

≈ 40visits/mo

Little sign of use · estimate, read Oct 13, 2026

For
Developers and QA testers who need valid test IBANs for software without real payments
Activity
Actively maintainedsite updated 9 days ago
Runs as
API
Used for
  • generate test IBANs for a chosen country
  • export lists of test IBANs as CSV, JSON or SQL
  • request test IBANs from an AI assistant through the MCP server
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 19, 2026
  • MCP servercom.generaterandomiban/iban-generatorverified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-19
  • Address to connectgeneraterandomiban.com/mcp
  • API docsgeneraterandomiban.com/en/apisthe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Generate Random IBAN for?

Sign in to leave a note
Questions this page answers
  • What is Generate Random IBAN?

    Produces test IBAN strings that pass the mod 97 checksum for 91 countries, downloadable as CSV, JSON or SQL.

  • Who is Generate Random IBAN for?

    Developers and QA testers who need valid test IBANs for software without real payments

  • Do people use Generate Random IBAN?

    Little sign of use: ≈ 40 visits/mo · estimate, 2026-10.

  • Is Generate Random IBAN still maintained?

    Actively maintained: site updated 9 days ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk