Form fixture
- Input
- test form → required identifier field
- Expected output
- PIS/PASEP → plausible synthetic value
Use it when a form needs to accept PIS/PASEP without depending on real data.
PIS/PASEP in privacy-first sandboxes
PIS/PASEP in privacy-first sandboxes
This page focuses on using synthetic PIS/PASEP in test scenarios. The goal is plausible data without touching real identifiers or implying official validation.
How to use synthetic PIS/PASEP safely
- The tool generates synthetic PIS/PASEP following 10 base digits with modulo-11 check digit. That is enough for masks, fixtures and contract tests that depend on plausible format.
- the generated number does not query employment links, benefits, CNIS or social-security records.
- Use it for simulated payroll flows, test spreadsheet imports and form 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 10 base digits with modulo-11 check digit; it does not cover official lookup or registry existence.
Full tool FAQ
They appear in different contexts, but many systems use the same 11-digit structure with a check digit.
Frequently asked questions
Is synthetic PIS/PASEP 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 PIS/PASEP in tests?
the generated number does not query employment links, benefits, CNIS or social-security records.
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.