How verification works
Which methods an Adaptive Access check offers, how facial age estimation is judged, and what the session records.
When an Adaptive Access check runs, k-ID handles the verification itself: which methods the user sees, how each result is judged, and what the session records. This page explains those rules so you know what users experience and what your app reads afterward. You don't implement any of it.
Verification methods
Both product-level and feature-level checks offer the methods configured for your product under Assurance & Verification > Age Assurance in Compliance Studio, including any market-specific rules. See Product configuration: Verification and Verification methods.
If you don't see Age Assurance under Assurance & Verification, your organization doesn't have access to that page. Contact your k-ID Account Manager.
Facial age estimation margins
Facial age estimation gives an estimate, not a proven age, so k-ID only counts an estimate that clears the age with room to spare. Each estimate falls into one of three bands:
| Estimate | Result |
|---|---|
| At or above the pass line | The check passes |
| Below the fail line | The check fails |
| Between the two lines | Too close to call: facial age estimation isn't offered again for this check, and the user can use another method, such as an ID document or an AgeKey |
Every face scan counts the whole estimated age range. The check passes only when the bottom of the range is at or above the pass line, and fails only when the top of the range is below the fail line. A range that overlaps either line is too close to call.
Each check judges an estimate against two lines:
- Pass line: the age being checked. For an 18+ check, an estimate of 18 or older passes.
- Fail line: 2 years below that age. For an 18+ check, an estimate under 16 fails.
On a feature-level check, you can raise the pass line with options.facialAgeEstimation.passIfOver and lower the fail line with options.facialAgeEstimation.failIfUnder on POST /session/upgrade. Neither moves past the age being checked. Product-level checks always use k-ID's lines.
Platform age signals
A trustworthy platform age signal whose ageLow is at or above the age being checked satisfies the check without a challenge:
- At the age gate, the signal must reach the age being checked.
- At a feature, the signal unlocks each requested permission whose threshold it reaches, and only the rest go to a challenge.
A signal never verifies above the age the user declared. When you also send dateOfBirth, age, or kuid and it gives a lower age, k-ID uses that age, and the signal verifies permissions only up to it. Signals from xbox and meta-horizon never count as trustworthy for age assurance.
What the session records
When a check passes, the session stores the result as ageVerification:
| Field | Description |
|---|---|
verifiedAge | The age the verification measured |
platformName | k-id for a k-ID check, or the platform that supplied a verified signal |
declarationType | The method that verified the user, or the platform's declaration type |
verificationId | The verification that produced the result |
verifiedAt | When the user verified |
verifiedDob | The verified date of birth, present only when the method read one rather than estimating an age |
Later checks reuse it. A POST /session/upgrade for a permission whose threshold the recorded result already meets is granted without another challenge.
Your app doesn't need to read ageVerification to decide access. Read each permission's enabled value, which already reflects the result.