Recurring liveness (proof of life)
For benefits, registrations and contracts that require periodic confirmation that the person is alive and is who they say they are.
- In-person visitsPeople with limited mobility or who live far away are left with no alternative.
- Misuse of a registrationBenefits paid in the name of someone who is no longer around.
- A non-technical audienceConfusing instructions turn into rejections and support queues.
Renewal on the calendar
jan
feb
marrenewal
apr
may
jun
jul
aug
seprenewal
oct
nov
dec
Example of a six-month cycle · the date and the channel are up to you
The suggested policy
A starting point for this solution. Everything is adjustable in the console, with no deploy, and every session records the policy that applied.
FlowAUTHENTICATION or LIVENESS_ONLY
Gestures per session2
Window for each gestureup to 7.5 s
Attempts3
Questions about this solution
Does it work for older people?
The page was designed for non-technical people: one gesture at a time, with a countdown, live guidance and the reason in plain language. The time for each gesture is configurable.
What about people who can't complete it?
An inconclusive case goes to human review instead of being rejected automatically.