Non-document verification

Markdown

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:

LivenessIdentity VerificationFraud Risk Classification

Capability	Required	Role in the flow
Liveness	Optional for API; required for Web and Native	Confirms that a real person is in front of the camera at capture time. Biometric anchor of the process.
Identity Verification	Required in all cases	Verifies 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 cases	Cross-references behavioral signals to flag fraud risk.

Optional derivation when IDUnico is inconclusive

The 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.
• Sandbox credentials — see Environments.
• SDK or Web component installed — only for Web and SDK integrations.

Step-by-step implementation

Native

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

1. Install the SDK — add the Unico SDK dependency for your platform. See the setup guide for Android, iOS or Flutter.
2. Create a process — call Create Process with the appropriate flow value and the user's identifier. The response includes the webAppToken.
3. 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.
4. Query the result — call Get Process to retrieve the capability results.
5. Apply business rules — evaluate the response fields to approve, deny or escalate.

Android

Native Android SDK for in-app capture.

View overview

iOS

Native iOS SDK for in-app capture.

View overview

Flutter

Cross-platform Flutter SDK for in-app capture.

View overview

Web

Integration in the browser — Unico hosts the journey, and you open it with the Journeys SDK or by redirecting the user.

1. 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.
2. Open the journey — open it inside your page with the Journeys SDK, 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 so Unico knows where to send them back.
3. User completes the journey — the Journeys SDK calls onFinish. With Direct access, Unico sends the user back to your callbackUri.
4. Query the result — call Get Process to retrieve the capability results.
5. Apply business rules — evaluate the response fields to approve, deny or escalate.

Web

Journeys SDK or Direct access, in the browser.

View overview

API

Direct API integration — capture the selfie using the Unico SDK or your own UI following the Capture Standard, then send the image directly to the Unico API.

1. Capture the selfie — use the Unico SDK for your platform, or build your own UI following the Capture Standard, to obtain a selfie image that meets liveness requirements.
2. Create a process — call Create Process with the user's identifier and the selfie as imagebase64; the executed capabilities are defined by your API Key configuration.
3. Query the result — call Get Process to retrieve the capability results.
4. Apply business rules — evaluate the response fields to approve, deny or escalate.

API

Full control over the flow with back-to-back integration.

View overview

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