Form fixture
- Input
- test form → required identifier field
- Expected output
- EIN → plausible synthetic value
Use it when a form needs to accept EIN without depending on real data.
EIN in privacy-first sandboxes
EIN in privacy-first sandboxes
This page focuses on using synthetic EIN in test scenarios. The goal is plausible data without touching real identifiers or implying official validation.
How to use synthetic EIN safely
- The tool generates synthetic EIN following 9 digits with a valid prefix from the public IRS list. That is enough for masks, fixtures and contract tests that depend on plausible format.
- a valid prefix does not confirm a company, tax status, bank account or tax authorization.
- Use it for B2B fixtures, simulated business onboarding and prefix validation. Do not send the value to real verification, official registration, credit, employment, KYC or government services.
Useful test scenarios
Local rule test
- Input
- mask / prefix / check digit
- Expected output
- accepted locally → never treated as verified identity
The local rule covers 9 digits with a valid prefix from the public IRS list; it does not cover official lookup or registry existence.
Full tool FAQ
Not like CPF/CNPJ. Basic validation uses length and IRS-valid prefixes.
Frequently asked questions
Is synthetic EIN a real document?
No. It is a test value with plausible format or digits, without lookup in official databases.
What is the key limitation when using EIN in tests?
a valid prefix does not confirm a company, tax status, bank account or tax authorization.
How can privacy risk be reduced?
Generate the value in the browser, do not store it in URLs or logs, and ensure analytics receives only action metadata, never the identifier.