Age assurance
Age assurance is the process of establishing a user's age with more confidence than a self-declared date of birth. Laws in some markets require it before a user can access a product, or a particular feature inside it. How strong the proof must be depends on the market and on the risk of the feature.
Age verification compared to age estimation
Age assurance is achieved through different kinds of methods:
- Age verification confirms an age from a trusted source, such as an ID document.
- Age estimation estimates an age with technology, such as facial age estimation.
k-ID offers both kinds, plus reusable proofs such as AgeKey. The methods available depend on the market and your product's configuration in Compliance Studio. See Verification methods.
Age assurance in k-ID
In a CDK integration, age assurance runs through Adaptive Access. You don't decide in your code who must verify, or when. k-ID decides from your Compliance Studio settings and each market's rules, then asks for proof in one of two places:
- At entry, with product-level age assurance:
/age-gate/checkreturns aCHALLENGE_AGE_GATE_AGE_ASSURANCEchallenge, and the session is created after the user passes. - At a feature, with feature-level age assurance: a permission carries a
verifiedAgeThreshold, and/session/upgradereturns aCHALLENGE_SESSION_UPGRADE_BY_AGE_ASSURANCEchallenge.
The result is saved on the user's session, and later decisions reuse it.
If you only need a single age check with no session, AgeKit+ runs age assurance on its own. See Adaptive Access or AgeKit+ on its own to choose.
ageAssuranceRequired
/age-gate/get-requirements returns an ageAssuranceRequired field. It reports the Age Assurance Reporting value configured for the market in Compliance Studio. It never starts a check, and it doesn't tell you whether an Adaptive Access check will run. Handle the challenges the API returns instead.