eKYC Platform

When to use it

eKYC Platform bundles the full eKYC process — document verification and selfie/liveness verification — into a single, ready-made verification journey. Because the steps that run, and the order they run in, are pre-configured for your account, integrating against it is typically faster than integrating against the eKYC Core API, which requires you to orchestrate each individual check (document scanning, tamper detection, liveness, face match, and so on) yourself.

Reach for eKYC Platform when you want a ready-made onboarding journey out of the box. Reach for the individual product APIs — Vision Score, Face Authentication, SIM Verification, Mule Account Database — or the eKYC Core API when you need to compose your own flow, run a single check in isolation, or plug a check into a step of a journey you already control.

How it works

Three steps, regardless of which journey runs for your account:

1. Start a session. Your backend generates a secure, per-applicant token that identifies the user and ties the session back to your account. See Authentication for how the token is created.
2. Launch the journey, handing that token to whichever integration surface fits your product — a mobile SDK (Android, iOS, Flutter, React Native), an embedded WebView, or a direct API call if you already hold the applicant's document/selfie assets from another channel (see Platform API). Which steps actually run — document only, selfie only, document then selfie, document with NFC then selfie, and so on — is decided by the journey configured for your account, not by the integration surface itself.
3. Get the result. Once the applicant finishes, TrustVision delivers the verdict and supporting evidence back to you — pushed to your backend automatically, retrieved on demand from the Service API, or picked up after the applicant is redirected back to your app.

See Integration Use Case for the full technical walkthrough of each step.

Choosing a journey

TrustVision configures a set of built-in journeys covering the common document/selfie orderings, plus flexible document-only or selfie-only journeys for when you want more control over the flow. Each journey is identified by an ID assigned to your account — see the Flow Id Reference for the full list.

Custom journeys and multi-client setup

eKYC Platform is provisioned per client. TrustVision issues each customer their own credentials ahead of integration, and every session reflects your account's configuration — language, allowed document types, and any custom settings — for its full duration.

Built-in journeys cover the common orderings out of the box; a custom journey beyond those is provisioned by TrustVision on request — contact your TrustVision integration manager to arrange one before integrating.