Skip to main content
Back to Numbers generators

Numbers

Fake Bank Account Number Generator

Used by developers, writers, and creators worldwide.

A fake bank account number generator solves a real problem for developers and QA engineers: you need structurally plausible financial data, but using real account numbers in test environments creates compliance and privacy risk. This tool generates fictional account numbers across four formats — UK sort code and account number pairs, US routing and account numbers, EU IBANs, and generic 16-digit numbers. Each output matches the character counts, separators, and structural patterns of real account numbers, so payment forms, onboarding flows, and fintech dashboards render exactly as they would in production. Pick your format, set the count, and copy a clean batch directly into your seed scripts or fixtures.

Loading usage…

Free forever — no account required

How to use

  1. Choose your options above
  2. Click Generate
  3. Copy your result

Detailed instructions

  1. Select your target banking format from the Format dropdown: UK, US, EU IBAN, or generic 16-digit.
  2. Set the Count field to how many unique account numbers you need for your test batch.
  3. Click Generate to produce a fresh list of fake account numbers in your chosen format.
  4. Copy the output list and paste it directly into your test fixtures, seed script, or design file.

Use Cases

  • •Seeding a Postgres staging database with 50 varied UK sort code and account number pairs
  • •Testing IBAN field validation and MOD-97 error states in a SEPA payment integration
  • •Populating bank detail fields in a Figma fintech prototype for a client design review
  • •Generating fixture data for Jest or Cypress tests covering US ACH routing number formatting
  • •Demoing a fintech onboarding flow to investors without exposing any real account holder data

Tips

  • →Generate a new batch for each test run rather than reusing the same numbers to catch edge cases in uniqueness validation.
  • →If testing IBAN field length limits, generate EU format numbers and compare against your input's maxlength attribute — real IBANs vary by country from 15 to 34 characters.
  • →Combine UK sort code and account outputs with a fake name generator to build complete, realistic mock bank records for demos.
  • →For US ACH testing, verify that your form correctly separates the routing number field (always 9 digits) from the account number field before using generated values.
  • →When seeding a database, generate more numbers than you need and deduplicate programmatically — random collisions are rare but possible at high volumes.
  • →Use the generic 16-digit format for testing card number fields, but remember it won't pass Luhn algorithm checks used by most payment forms.

FAQ

can these fake bank account numbers be used with Stripe or GoCardless sandbox testing

No — payment gateways like Stripe, GoCardless, and Braintree require their own official test credentials to trigger API calls, even in sandbox mode. Use this generator for UI rendering, form validation logic, and database seeding, then swap in provider-specific test credentials when you need to exercise the actual payment flow.

do the generated IBANs pass checksum validation

The IBANs are format-realistic but are not guaranteed to pass MOD-97 checksum verification. If your integration strictly validates check digits, run the output through a dedicated IBAN validator, or use your payment provider's official test IBANs for transaction-level tests.

is it safe to include fake account numbers in Figma files or staging demos shared externally

Yes, and it's the right approach. Sharing design files or demo environments containing real account details creates a genuine data exposure risk. Generated numbers have no connection to any real bank or account holder, making them safe for client presentations, public staging environments, and recorded product demos.