Use cases
Desktop to phone verification
The user starts at a computer and scans a QR code to finish on a phone.
The job
Many users reach a service on a computer, but the camera that suits a document and a selfie is on the phone. The verification should follow the user from one device to the other.
The flow
- The computer page. Your backend creates a session, and your page shows a QR code for it.
- The scan. The user scans the QR code with a phone. The phone opens the widget for the same session.
- The steps on the phone. The user photographs the document, takes the selfie and follows the two ovals. See document verification, face verification and liveness.
- Back on the computer. The session status changes. Your backend reads it, or a webhook announces it, and the computer page moves on.
Scenario setup
Nothing in the scenario changes. The hand-off is a way to open the same session on another device. Build the scenario in the scenario editor.
What your system receives
One session with a status and the results of each step, wherever it was completed. See session statuses.
Next
Read about QR hand-off and one-time links, or try the interactive tour.
Questions, answered plainly
Does the user have to install an app?
No. The widget runs in the browser of the phone.
Is a QR code the only way to move to a phone?
No. You can also create single-use links and send them through your own channels. See bulk link invitations.
How does the computer page learn that the user finished?
Your backend reads the session status through the API, or receives the SESSION_COMPLETE webhook, and your page follows it.