Random Bank Account Number Generator

How to use

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

Detailed instructions

1. Set the count field to the number of account number records you need for your test data.
2. Select the account format that matches your target system: UK sort code, US routing, IBAN-style, or generic.
3. Click Generate to produce a fresh batch of fictitious account numbers in the chosen format.
4. Copy the output directly into your test fixture, database seed file, or form validation script.
5. Re-click Generate as many times as needed to produce additional unique batches without duplicating.

Use Cases

• •Seeding a Postgres staging database with 500 fake UK account and sort code pairs before a BACS payment integration test
• •Populating Figma payment form mockups with realistic-looking account numbers for stakeholder review
• •Generating fixture JSON for Cypress end-to-end tests that validate account number field length and character rules
• •Filling Postman environment variables with US routing and account numbers to test a multi-region payment API
• •Creating a GDPR-compliant demo dataset for a banking dashboard without using any real customer records

Tips

• →For UK testing, always use the UK format so sort codes appear in XX-XX-XX notation, matching what your validation regex expects.
• →When populating a demo database, mix multiple format types if your app supports international accounts — one batch per region keeps data realistic.
• →IBAN-style output works well for testing field length limits; real IBANs range from 15 to 34 characters depending on country.
• →Pair generated account numbers with a fake name generator and fake address generator to build complete, coherent customer test records.
• →If your system strips hyphens from sort codes before storing them, test both the raw output and a manually stripped version to catch formatting bugs.
• →Avoid using the same small set of generated numbers across all your test cases — generate a fresh batch each sprint so edge cases in your validation logic get exercised properly.

FAQ