Age Verification
Age verification confirms that a person meets an age threshold — without necessarily enrolling them as a Customer. It can run against a facial age estimate (where the law allows) and fall back to a document check when stronger proof is required.
When to use it
Gating access to age-restricted goods or services — alcohol, gambling, adult content, certain financial products. The person can stay anonymous; the platform only needs to answer "is this person old enough?".
How it works
- Face capture & liveness — the User takes a selfie.
- Age estimate — the platform estimates age from the selfie. If the estimate is comfortably above the threshold and estimation is legally acceptable for the use case, the check can pass here.
- Document fallback — if estimation is not conclusive or not permitted, the User captures an identity document and age is computed from its date of birth.
- Decision — an outcome is returned.
Whether estimation alone is allowed, and the safety margin above the legal limit, are configurable per workflow.
Outcomes
| Outcome | Meaning |
|---|---|
| Age verified (estimation) | The facial age estimate cleared the threshold with margin. |
| Age verified (document) | The document's date of birth confirms the person is old enough. |
| Age rejected | The person is below the required age. |
| Rejected | The data could not be trusted (poor capture or spoofing). |
| Incomplete | The User did not finish. |
Notes
- Age verification can be anonymous — results may be stored for audit (e.g. paired with a purchase) without creating a full Customer identity.
- To verify age and onboard the person, use Identity Verification instead.