---
title: Non-document verification
description: Identity verification, in any region, with liveness, Biometric Identity Verification and fraud risk assessment.
canonical: https://developer.unico.io/products/sign-up/non-document-verification/index
locale: en
generated_by: markdown-export
---

- [/](/)
- [Build](/products/)
- [Sign-up](/products/sign-up/)
- Non-document verification

**On this page# Non-document verification

### What this product solves​

Onboarding addresses the challenge of validating the identity of a new user in any region, with a pipeline focused on three essential signals — liveness, facial verification and fraud risk — using a region-agnostic response schema that works anywhere in the world.
**Use this product when:**

You want a lean, agnostic pipeline that operates in any region of the world.
Local regulation does not require document capture integrated into the same process.
Your architecture needs a single integration contract for multiple markets.

### Capabilities involved​

Pipeline executed within a single process:
[Liveness](/capabilities/liveness)[Identity Verification](/capabilities/identity-verification)[Fraud Risk Classification](/capabilities/fraud-risk-classification)
CapabilityRequiredRole in the flow**Liveness**Optional for API; required for Web and NativeConfirms that a real person is in front of the camera at capture time. Biometric anchor of the process.**Identity Verification**Required in all casesVerifies whether the transaction face belongs to the holder of the provided government identifier, using Unico's identity base and additional signals.**Fraud Risk Classification**Required in all casesCross-references behavioral signals to flag fraud risk.
Optional derivation when IDUnico is inconclusiveThe base pipeline stays the same — Brazil adds optional risk layers on top of it.When IDUnico returns inconclusive, Score is triggered to calculate a fraud probability score based on historical data. You use this score to make the approval decision according to your risk appetite.LivenessIdentity VerificationRisk ScoreFraud Risk Classification
### Prerequisites​

**Bearer token** — see [Authentication](/developers/start/authentication).
**Sandbox credentials** — see [Environments](/developers/start/environments).
**SDK or Web component installed** — only for Web and SDK integrations.

### Step-by-step implementation​

NativeWebAPIIntegration via native SDK — capture runs inside your app using the Unico SDK for Android, iOS or Flutter.

**Install the SDK** — add the Unico SDK dependency for your platform. See the setup guide for [Android](/developers/sdks-and-tools/android/requirements), [iOS](/developers/sdks-and-tools/ios/requirements) or [Flutter](/developers/sdks-and-tools/flutter/requirements).
**Create a process** — call Create Process with the appropriate `flow` value and the user's identifier. The response includes the `webAppToken`.
**Open the journey** — open the SDK with the `webAppToken`. The SDK runs the journey in your app and calls `onSuccess` with the `processId` when the user finishes.
**Query the result** — call Get Process to retrieve the capability results.
**Apply business rules** — evaluate the response fields to approve, deny or escalate.

AndroidNative Android SDK for in-app capture.[View overview](/developers/sdks-and-tools/android/requirements)iOSNative iOS SDK for in-app capture.[View overview](/developers/sdks-and-tools/ios/requirements)FlutterCross-platform Flutter SDK for in-app capture.[View overview](/developers/sdks-and-tools/flutter/requirements)Integration in the browser — Unico hosts the journey, and you open it with the Journeys SDK or by redirecting the user.

**Create a process** — call Create Process with the appropriate `flow` value and the user's identifier. The response includes the process `id`, the `token` and the `userRedirectUrl`.
**Open the journey** — open it inside your page with the [Journeys SDK](/developers/sdks-and-tools/web), passing the process `id` (as `transactionId`) and the `token`. This is the recommended option. If the journey can run outside your page, use Direct access instead: send the user to `userRedirectUrl`, and set `callbackUri` in [Create Process](/developers/api-reference/post-processes) so Unico knows where to send them back.
**User completes the journey** — the Journeys SDK calls `onFinish`. With Direct access, Unico sends the user back to your `callbackUri`.
**Query the result** — call Get Process to retrieve the capability results.
**Apply business rules** — evaluate the response fields to approve, deny or escalate.

WebJourneys SDK or Direct access, in the browser.[View overview](/developers/sdks-and-tools/web)Direct API integration — capture the selfie using the [Unico SDK](/developers/sdks-and-tools/overview) or your own UI following the [Capture Standard](/developers/sdks-and-tools/capture-standard), then send the image directly to the Unico API.

**Capture the selfie** — use the [Unico SDK](/developers/sdks-and-tools/overview) for your platform, or build your own UI following the [Capture Standard](/developers/sdks-and-tools/capture-standard), to obtain a selfie image that meets liveness requirements.
**Create a process** — call [Create Process](/developers/api-reference/post-processes) with the user's identifier and the selfie as `imagebase64`; the executed capabilities are defined by your API Key configuration.
**Query the result** — call [Get Process](/developers/api-reference/get-process) to retrieve the capability results.
**Apply business rules** — evaluate the response fields to approve, deny or escalate.

APIFull control over the flow with back-to-back integration.[View overview](/developers/api-reference/post-processes)
Operating in Mexico?KYC Magic Link offers an alternative with zero front-end development — send a link via WhatsApp, SMS or email and Unico hosts the entire INE + liveness capture journey for you. No SDK installation required.[See KYC Magic Link](/products/sign-up/kyc-magic-link/index)Last updated on Oct 8, 2026**