Use cases
Website and app verification
Put the verification inside your own page or app, so the user never leaves your product.
The job
Your product has a website or an app, and the verification should feel like part of it. The user should not be sent to a separate site, and your team should not build the capture screens from scratch.
The flow
- The backend starts the session. Your backend creates a session through the REST API with the identifier of your scenario.
- The page opens the widget. Your website opens the web widget for that session. In a mobile app, the widget is opened inside a WebView.
- The user completes the steps. The widget guides the user through the steps of the scenario, in one of 29 interface languages.
- The page learns the outcome. The widget reports back to your page when the user is done.
- The backend reads the result. It reads the session status, or a webhook tells it the session is complete.
Scenario setup
The scenario decides which steps the user sees. Build it in the scenario editor. The look of the widget is your own: your colours and your logo, as described on the branded widget page.
What your system receives
A session with a status and a list of results, one entry per step. See session statuses.
Samples
Plain JavaScript and React are supported, and key-encryption samples are available for Node.js, PHP, Python and Go. The quick start shows the call sequence.
Next
Open the quick start, or see the screens on sample data in the interactive tour.
Questions, answered plainly
Does it work inside a mobile app?
Yes, through a WebView. The widget is a web widget that runs in desktop and mobile browsers, and a WebView needs separate app settings.
How many languages does the widget have?
29 interface languages.
What if the user opens my page on a desktop?
The user can scan a QR code and continue on a phone. See QR hand-off.
How does my backend learn that the user finished?
It reads the session status through the REST API, or it receives the SESSION_COMPLETE webhook.