NexionLabsAGE ASSURANCE
Verify age.
Keep the experience
moving.
Combine NexionLabs age estimation, reusable age verification and provider checks. Let users establish age before accessing a feature, joining a service or completing a restricted transaction.
Illustrative user flow
18+Confirm you’re old enough.
Choose an available way to verify.
Reusable age proofExplore reuse ↗Age estimationExplore age checks ↗Digital credentialExplore credentials ↗Methods shown depend on your configured flow.
MATCH THE METHOD TO THE MOMENT
A first check.
A simpler return visit.
An eligibility check can give your application an age result without passing the underlying identity document to your business.
Age estimation
Estimate age without making a document check the first step.
Verified age
Establish age through a digital credential or verification provider.
Reusable proof
Let returning users present an age proof instead of repeating the original check.
HOW IT WORKS
From age requirement
to access.
- 01
Set the requirement
Choose the age threshold and verification routes.
- 02
Offer the check
Let users choose a method, with a fallback if they cannot complete it.
- 03
Evaluate the result
Check completion, validity and the current rule on your server.
- 04
Record the decision
Keep the allow or deny decision linked to the check.
DOUBLE-BLIND REUSABLE VERIFICATION
Prove age again.
Skip the repeat check.
A returning user can present an age proof without repeating the original verification.
Double-blind reuse keeps the user’s identity from the accepting business and the destination service from the original verifier.
Explore reusable verificationA proof for the next visit.
- Presentation
- Existing age proof
- Checks
- Valid · accepted for this flow
- Application decision
- Allow returning member
- Context
- New session · linked result
The verification result linked to the access decision.
Coverage and conditions
- Choose methods against the age requirement, audience and market. We confirm method and device coverage during integration.
- Reusable proofs must be valid for the new request. Expired or insufficient proofs require a new check.
- Double-blind disclosure applies to the reusable proof flow. Processing and retention differ across estimation, document and provider flows.
Does age estimation establish identity?
No. It assesses age. Use identity verification when the account or transaction requires verified identity attributes.
What happens when a check cannot complete?
Offer another route or stop the flow. An incomplete check is neither a pass nor proof that the user is underage.
LET’S MAKE IT CONCRETE
See age assurance
in your user flow.
Choose a point of access and walk through first checks, reuse and fallback.
A conversation around your product.