Onboarding
What this use case solves
Identity verification with document capture and reuse addresses the challenge of verifying identity with the broadest set of risk signals while also capturing a government-issued document, all in a single process.
Use this use case when:
- You need biometric identity verification combined with behavioral alerts and document capture.
Do not use this use case when:
- You do not need document capture → look at the other onboarding use cases.
Capabilities involved
Pipeline executed within a single process:
| 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. |
| Risk Fraud Classification | Required in all cases | Cross-references behavioral signals to flag fraud risk associated with the document identifier. |
| Document Capture & Reuse | Required in all cases | Captures a new document image or returns a previously captured image associated with the user. |
Prerequisites
- Bearer token — see Authentication.
- Sandbox credentials — see Environments.
- SDK or Web component installed — only for Web and SDK integrations. See SDKs and Tools.
Step-by-step implementation
- Native
- Web
- API
Integration 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, iOS or Flutter.
- Create a process — call Create Process with the appropriate
flowvalue and the user's identifier. Use the returnedtokento initialize the SDK. - Start the capture — the SDK renders the camera UI and performs liveness detection on-device, returning the captured payload.
- Query the result — call Get Process to retrieve the capability results.
- Apply business rules — evaluate the response fields to approve, deny or escalate.
Integration via iFrame, Redirect or Native — Unico hosts the capture UI, and you receive the result via polling.
- Create a process — call Create Process with the appropriate
flowvalue and the user's identifier. The response includes auserRedirectUrl. - Redirect the user — send the user to
userRedirectUrl. Unico renders the capture journey. OrwebAppTokenin native apps. - User completes the journey — after capture, the user is redirected 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.
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.
- 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.
- Create a process — call Create Process with the user's identifier and the selfie as
imagebase64. - Query the result — call Get Process to retrieve the capability results.
- Apply business rules — evaluate the response fields to approve, deny or escalate.
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.


