Web App Integration
This page describes how the Unico journeys work and the available integration models for embedding them into an application.
A journey is the set of steps the user goes through to complete an identity verification. For example: capturing a document photo and performing a facial capture (liveness).
Unico manages the entire experience. The integration effort is minimal: the journey is created via CreateProcess, the user is directed to it, and the result is received at the end. Everything in between — screens, instructions, validations — is already built and maintained by Unico.
Choosing your integration approach
- Web SDK (
unico-webframepackage) — use when your back-end already controls the identity verification flow and only needs the client-side capture component. Returnsbase64+ encrypted JWT directly to your callback; you manage the API calls. - Web App Integration (
idpay-b2b-sdkpackage) — use when you want Unico to orchestrate the full journey (multi-step flows, document capture + liveness). Theidpay-b2b-sdkpackage powers the embedded Journeys SDK (iFrame) model; the Direct access (redirect) model needs no library.