Age Assurance
Confirm age requirements without exposing unnecessary data.
Confirm whether a user meets a configured age threshold by validating identity-document data and, when required, biometric proof of presence.
- Part of a guest compliance session
- Hosted, API, and webhooks
- Configured human review
How it works
Age checks in four steps
Use a short identity flow to produce an eligibility result.
Capture an identity document
The guest 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 operator receives a configured pass, fail, retry, or review outcome with appropriate session evidence.
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 property, booking flow, 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 property, booking type, market, or risk level.
Capabilities
Age controls that fit the booking workflow
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
- Minimum-age booking rules
- Age-restricted accommodation
- Unaccompanied guest policies
- Property access restrictions
- Hospitality events and packages
- Booking exception review
Security and privacy
Controlled by design, documented in public.
Every module uses the same access, output, audit, and retention boundaries as the wider guest compliance workflow.
Minimum necessary output
Operators receive the approved status and fields rather than unrestricted document copies by default.
Booking-linked history
Configured consent, status, access, and review events remain tied to the relevant session.
Controlled retention
Access and retention rules are configured for the customer's workflow and applicable obligations.
FAQ
Frequently asked questions
Key implementation and workflow questions for age assurance.
Configure your flow
See Age Assurance inside a DocinVault workflow
We will map the module to your customer journey, operating market, and review requirements.