Age Verification
# Age Verification
**Age Verification** answers "**Is this user old enough?**". The user proves they meet the minimum age you set, backed by a genuine government document, and you never see their date of birth. Nothing else is asked, and nothing else is revealed.
It's the narrowest, fastest workspace to configure: set one number and deploy.
## What the user proves
- They hold a **genuine, government-signed document** (at your chosen [security level](/docs/self-enterprise/flows/disclosures/#security-level)).
- They are **at least the age you set**, a pass/fail fact computed on their device from the document's birth date, which never leaves the phone.
- Optionally, that they **clear the OFAC sanctions list**.
## What you receive
- A `valid` / `invalid` result via the [`verification.completed` webhook](/docs/self-enterprise/webhooks/events/): `valid` means "old enough", `invalid` means a rule failed.
- The enforced rules echoed in `proof_attributes` (for example `{ "minimumAge": 21, "ofac": true }`).
- A [nullifier](/docs/self-enterprise/get-started/how-it-works/#one-account-per-person-nullifiers) for duplicate detection.
For example, a flow with a 21+ floor and OFAC on carries:
```json
{ "minimumAge": 21, "ofac": true }
```
That's the whole object: the rules that were enforced, echoed back. The pass/fail answer is the event's `status`, and no personal data appears.
No name, no birth date, no document number. An age gate that holds zero personal data is the point.
## Rules you can configure
| Rule | Default | Notes |
| -------------- | ----------- | ---------------------------------------------------------------- |
| Security level | Hi-security | Standard also accepts non-chip documents. |
| Minimum age | 21 | 13–110. Pick the threshold your regulation requires (18, 21, …). |
| OFAC | On | Checked against the daily-updated US Treasury list. |
No country rules and no data reveals. If you need those, use [Pre-KYC](/docs/self-enterprise/workspaces/pre-kyc/).
## Use cases
- **Age-restricted commerce**: alcohol, tobacco, vaping, CBD. Prove 18+/21+ at checkout without collecting IDs.
- **Age-gated content and platforms**: adult content, gambling, and social features with regulatory age floors.
- **Regulatory compliance**: meet age-assurance rules (e.g. for app stores or regional online-safety laws) with a documented, privacy-preserving check instead of a self-declared checkbox.
- **Events and communities**: gate registration to adults without storing anyone's birth date.
## Cost
**10 credits** per completed verification. See [Credits and usage](/docs/self-enterprise/billing/credits-and-usage/).
Read https://docs.self.xyz/docs/self-enterprise/workspaces/age-verification.md so I can ask questions about this Self documentation page.
Age Verification answers “Is this user old enough?”. The user proves they meet the minimum age you set, backed by a genuine government document, and you never see their date of birth. Nothing else is asked, and nothing else is revealed.
It’s the narrowest, fastest workspace to configure: set one number and deploy.
What the user proves
- They hold a genuine, government-signed document (at your chosen security level).
- They are at least the age you set, a pass/fail fact computed on their device from the document’s birth date, which never leaves the phone.
- Optionally, that they clear the OFAC sanctions list.
What you receive
- A
valid/invalidresult via theverification.completedwebhook:validmeans “old enough”,invalidmeans a rule failed. - The enforced rules echoed in
proof_attributes(for example{ "minimumAge": 21, "ofac": true }). - A nullifier for duplicate detection.
For example, a flow with a 21+ floor and OFAC on carries:
{ "minimumAge": 21, "ofac": true }That’s the whole object: the rules that were enforced, echoed back. The pass/fail answer is the event’s status, and no personal data appears.
No name, no birth date, no document number. An age gate that holds zero personal data is the point.
Rules you can configure
| Rule | Default | Notes |
|---|---|---|
| Security level | Hi-security | Standard also accepts non-chip documents. |
| Minimum age | 21 | 13–110. Pick the threshold your regulation requires (18, 21, …). |
| OFAC | On | Checked against the daily-updated US Treasury list. |
No country rules and no data reveals. If you need those, use Pre-KYC.
Use cases
- Age-restricted commerce: alcohol, tobacco, vaping, CBD. Prove 18+/21+ at checkout without collecting IDs.
- Age-gated content and platforms: adult content, gambling, and social features with regulatory age floors.
- Regulatory compliance: meet age-assurance rules (e.g. for app stores or regional online-safety laws) with a documented, privacy-preserving check instead of a self-declared checkbox.
- Events and communities: gate registration to adults without storing anyone’s birth date.
Cost
10 credits per completed verification. See Credits and usage.
Was this page helpful?
Thanks — what went wrong?
Thanks for your feedback!