Skip to main content
The verification runs in the browser. It needs a camera and a secure page (HTTPS).

​
Browsers

Current versions of the major browsers, such as Chrome, Safari, Edge and Firefox, on phones and computers. A browser too old to run the widget is told so before anything starts. For document checks a phone is the better device: its rear camera photographs documents far better than a laptop’s webcam. On a computer, the widget offers a QR code to continue on a phone.

​
In-app browsers

Links opened inside apps such as Instagram or Snapchat open in the app’s own browser, which often blocks the camera. When that happens the widget tells the person to open the page in Safari or Chrome. To avoid it, send people to the verification from your own site or app rather than inside a social app, or tell them to open the link in their browser.

​
Your own app (WebView)

Showing the verification inside a native app’s WebView works only if the WebView may use the camera:
  • iOS (WKWebView): add NSCameraUsageDescription to your app, and allow inline media playback.
  • Android (WebView): request the CAMERA permission, and grant the page’s camera request in WebChromeClient.onPermissionRequest.
Opening the verification in the system browser (Safari View Controller, Chrome Custom Tabs) avoids this and is the simpler choice.

​
When the camera is blocked

The widget works out where the block is and says what to do:
  • The person dismissed the prompt: they can tap Enable Camera and choose Allow.
  • The site is blocked in the browser: step-by-step instructions for that browser, for example the camera setting next to the address bar in Chrome, or Website Settings in Safari.
  • The system blocks the browser: where to allow it in the phone’s or computer’s privacy settings.
If none of that helps, it suggests another browser or another device.

​
Embedding

The Browser SDK’s modal runs the widget in an iframe on your page. Your page must be served over HTTPS; see Browser SDK.