vlayer docsVerification channels
Choosing a channel
Where your user completes a verification — the browser extension, the Vouch mobile apps, or your own app via our mobile SDKs.
All three return the same result payload, so you can start with one channel and add another later without touching your webhook handler.
The three channels
| Channel | Where the user verifies | Integration effort | Best when |
|---|---|---|---|
| Vouch browser extension | Chrome, Brave or Edge on desktop. Installed once, reused for every later verification. | None. Redirect to a Vouch URL. | Your users are on desktop and you want the fastest route to live. |
| Vouch mobile apps | The Vouch app on iOS or Android, which returns the user to your app. On iOS it runs as an App Clip, so there is nothing to install. | None. Redirect to a Vouch URL. | Your users are on their phones, or the platform being verified is mobile-only. |
| Mobile SDKs | Inside your own iOS, Android or React Native app. The user never leaves it. | High. A native SDK integration. | A handoff to another app would cost you completions. |
You do not have to choose one. A desktop user can scan a QR code and finish on their phone. It is the only route for mobile-only platforms, and a fallback when a desktop user will not install the extension. See how it works →
What the user sees in their language
Verification messages are shown to the user in their own language where the data source supports it. See Localization for what a user sees when a translation is missing.
Last updated on