Requirements
The Human Token journey operates within browser environments, either directly embedded in web pages or launched via system browsers in applications. End-user devices must meet the following technical standards.
Supported browsers
The capture frame requires WebRTC support and recent browser versions:
| OS | Chrome | Firefox | Safari | Samsung Internet | Opera | Edge |
|---|---|---|---|---|---|---|
| Windows | ✅ | ✅ | N/A | N/A | ❌ | ❌ |
| macOS | ✅ | ✅ | ✅ | N/A | ❌ | ❌ |
| Android | ✅ | ❌ | N/A | ✅ | ❌ | ❌ |
| iOS | ✅ | ✅ | ✅ | N/A | ❌ | ❌ |
Edge and Opera are Chromium-based and may function in practice, but they lack official Unico certification and support.
Minimum OS versions (in-app browsing)
| Platform | Minimum version |
|---|---|
| Android | 8 (API 26) |
| iOS | 13 |
Security requirements
Pages must use HTTPS encryption. All registered domains must use secure protocols, as camera APIs require a secure context.
App integration guidance
Avoid embedding the journey in WebView containers. Instead, use native system browsers:
- Android — Custom Tabs
- iOS — ASWebAuthenticationSession
Social-network in-app browsers are not supported.
Market coverage
Approximately 95–97% of active devices meet these requirements, supporting high conversion rates across global markets.