Age verification
Make age decisions from verified identity data
Confirm whether a user meets a configured age threshold by validating identity-document data and, when required, biometric proof of presence.
- Configurable workflow
- Hosted, API, and webhooks
- White-label experience
Eligibility
Self-declared birthdays are not reliable age evidence
Age verification replaces a simple age gate with a configurable decision based on verified document data, optional liveness, and a threshold set for the product or market.
Document-based evidence
Extract and validate date-of-birth information from an eligible government-issued document.
Minimum necessary result
Return a configured age-threshold result instead of exposing more identity data than the workflow requires by default.
Policy controls
Set different thresholds or step-up requirements by product, location, or risk level.
How it works
Age checks in four steps
Use a short identity flow to produce an eligibility result.
Capture an identity document
The user captures an eligible government-issued document in the browser or application flow.
Extract and validate date of birth
The configured checks read the date and compare available document zones and integrity signals.
Confirm presence when required
Add liveness and Face Match when the workflow must confirm the document holder is completing the check.
Return the threshold result
The customer receives a configured pass, fail, retry, or review outcome with appropriate session evidence.
Capabilities
Age controls that fit the product
Apply consistent thresholds without rebuilding the wider verification journey.
Discuss your workflow- 01Government-issued document checks
- 02Configurable minimum ages
- 03Liveness and Face Match options
- 04Pass or fail output
- 05White-label interface
- 06Reviewable decision record
Use cases
Where age verification fits
- Age-restricted accommodation
- Gaming and gambling
- Alcohol and tobacco sales
- Financial products
- Events and venues
- Restricted digital content
Security and compliance
Built for controlled identity workflows
Apply configured access, evidence, retention, and result-handling rules while using the approved security and compliance controls of the DocinVault platform.
Level 2 ISO 30107-3
CCPA compliant
SOC 2 Type 2
eIDAS compliant
FAQ
Frequently asked questions
Key implementation and workflow questions for age verification.
How is document-based age verification different from an age gate?
An age gate relies on a birthday entered by the user. Document-based verification reads and validates date-of-birth information from an eligible identity document.
Does the customer need the full date of birth?
Not necessarily. The configured output can provide an age-threshold result and the minimum structured data required by the workflow by default.
Can thresholds vary by market or product?
Yes. Thresholds and required step-up checks can be configured for different products, operating markets, and risk levels.
Configure your flow
See Age verification inside a DocinVault workflow
We will map the module to your customer journey, operating market, and review requirements.