Browser support & platform requirements

This page describes which browsers, operating systems, and WebView environments are supported by Veriff's web-based verification flow, and which Web Platform APIs are required for it to function correctly.

HTTPS required

All camera, media, and real-time communication APIs used by Veriff are restricted by browsers to secure contexts. The verification URL must be served over HTTPS. Plain HTTP is not supported (except localhost for development and testing).

Supported browsers

The verification flow requires navigator.mediaDevices.getUserMedia, mediaDevices, and enumerateDevices to be available in the end-user's browser. Browsers that do not support these APIs are shown an error at session start. The tables below list browsers and versions where Veriff is known to work reliably.

Desktop

Legacy Microsoft Edge (EdgeHTML engine) and Internet Explorer are not supported.

Mobile

Operating system requirements

Unsupported browsers

The following browsers and environments are detected at session start. End-users will be shown an error screen directing them to switch to a supported browser before verification can proceed.

If camera access is blocked in Samsung Internet, a dedicated guidance screen is shown to help end-users grant the permission manually.

WebView environments

For WebView integration guides, see the WebView integration guide.

Required browser APIs

These APIs must be available for the verification flow to start. If any are missing, the end-user will see an error screen.

All required APIs are supported in every browser and OS version listed in the Supported browsers section above.

Optional APIs

These APIs are detected at runtime. When unavailable, the application falls back gracefully and the verification flow continues, but with a different code path.

Known WebView limitations

These are platform-level constraints that affect WebView environments.

Camera device labels are anonymised until permission is granted. On Android, navigator.mediaDevices.enumerateDevices() returns devices with empty labels until camera permission has been explicitly granted.

window.close() is a no-op in most WebViews. When a verification session ends, the Veriff flow attempts to close the page. In WebViews that did not programmatically open the page, window.close() is ignored by the browser. Use the session FINISHED event to handle navigation in your native layer.

localStorage must not be blocked. The Veriff flow wraps all storage calls defensively, so the session will not crash if storage is unavailable, but certain session features will degrade silently.

window.open() must be delegated to the system browser. When the verification flow opens an external URL (for example, to hand off to a third-party service), it calls window.open(). In most WebViews this call is silently ignored or opens inside the WebView itself, which may break the target service. Intercept the call in your native layer and forward the URL to the device's default browser, or open it in a Chrome Custom Tab (Android) or SFSafariViewController (iOS).

Connection requirements

Changelog