Prior verifications are reused by subject ID
A verification request that includes subject.id now completes straight away when the user already verified their age with k-ID under the same subject.id, in the same way a matching subject.email already did. The user isn't asked to estimate or prove their age again, and the original age is returned.
What's new
- Reuse by
subject.id. A prior verification counts when it was made with the samesubject.idin any product in your organization, used a method this product accepts in the jurisdiction, and verified at least the age your criteria requires. Asubject.idsent by another organization is never matched to yours. A prior facial age estimation also has to reach youroptions.facialAgeEstimation.passIfOvervalue, which defaults to the criteria age. - Email and ID together. When a request includes both
subject.emailandsubject.id, a prior verification that matches either one is reused. - No expiry. The most recent matching verification is used, and there is currently no time limit on how old it can be.
What you should check
Until now, subject.id only linked attempts so failed ones could be counted. If you send an identifier that several people share, such as a device or household ID, one person's verification now completes the next person's. Send an identifier that belongs to one user, such as a hashed user ID.