Generate one or ten clearly synthetic records for checkout mockups, validation tests and QA automation. Nothing is uploaded, and every record uses deliberately non-deliverable values.
Copy one field, copy a full record, or save records for a batch export.
Ready for common client-side form and state/ZIP format tests.
Saved only in this browser. Export a clean fixture file when your test batch is ready.
No saved records yet. Save a generated card to build a batch.
The generator follows common US field shapes while reserving obvious markers that keep test fixtures separate from customer data. That makes screenshots, bug reports and exports safer to share inside a development team.
Test User QAA recognizable QA name keeps the fixture separate from customer data.
70001 QA Fixture LaneA normal field shape with a clearly fictional QA street name.
97204 or 97204-0001Uses a known city/state ZIP pair so common state/ZIP checks can pass.
+1 (503) 555-0124Uses the reserved 555-0100 through 555-0199 fictional range.
qa.test.4821@example.comexample.com is reserved for documentation and passes common email syntax checks.
This is a field-format reference, not tax advice. Alaska may have local sales taxes, and merchants decide the final taxable location and amount.
No state or local general sales tax; seller gross-receipts tax can still apply.
Official state source ↗No general state sales or use tax; narrow product-specific taxes can still exist.
Official state source ↗No general state sales tax on goods; specific taxes still exist.
Official state source ↗No general state sales tax; selective and some resort-area taxes can apply.
Official state source ↗No statewide sales tax; many municipalities impose local sales tax.
Official state source ↗Check required fields, 5-digit versus ZIP+4 parsing, state selectors and phone formatting.
Fill wireframes and staging checkouts without putting a customer address into screenshots.
Export stable JSON or CSV records for Cypress, Playwright and integration tests.
Attach a recognizable TEST record to a bug report so nobody mistakes it for production data.
No. The common-form profile uses a real city/state/ZIP relationship so frontend validation can pass, but combines it with a clearly fictional QA street, reserved phone and TEST ID.
No. Those are live-account or eligibility scenarios and require your own truthful information. This tool is only for software testing, prototypes, education and QA.
No. Generation, saved records and exports stay in your browser. Clearing the browser's site data removes the saved list.
That block is reserved for fictional use, which reduces the chance that a test fixture points to a real subscriber.
Yes. Choose 1, 5 or 10 records, then save selected cards or export your saved batch as CSV or JSON.
Common form pass uses format-compatible fields and known city/state/ZIP pairs. Reject-path test deliberately inserts values such as ZIP 00000 and example.invalid so you can test form errors.