Skip to content
Documentation

Build identity verification with Othento.

Drop in one SDK — Web, iOS or Android — and launch a fully managed document, face and liveness flow. Every platform shares the same model: configure a session, launch it, and receive one terminal decision. This guide gets you from zero to a working integration.

How a verification works

A verification is one session running one workflow. The shape is the same on every platform:

  • You configure a workflow once in the Console and get a workflowExternalId.
  • The SDK creates a session for an end user and presents the capture flow.
  • The user scans their document and completes liveness and face checks in the managed UI.
  • The session resolves to a decisionApproved, Declined or InReview — delivered to the SDK and to your webhook.

Core concepts

A handful of terms appear throughout these docs and across every SDK.

Workflow

A reusable verification flow you configure in the Console — which checks run (document, liveness, face match, AML) and in what order. Referenced by a workflowExternalId.

Session

A single run of a workflow for one end user. Created when the SDK starts, it moves through a status lifecycle and ends in a decision. Identified by an externalId.

Decision

The terminal outcome of a session: Approved, Declined or InReview. Returned to the SDK and to your webhook.

clientData

Your own identifier for the end user (e.g. a user id). It is echoed back on session events and webhooks so you can correlate a result to a user.

API keys

Public keys issued in the Console. The prefix decides the environment — pk_sandbox_… for testing, pk_live_… for production. No separate environment flag.

Modes

Create mode mints a session from the client with your public key. Token mode resumes a session your server minted, keeping keys off the client.

Pick your SDK

The integration surface is intentionally identical across platforms — learn it once, ship it everywhere.

Next steps

  • Quickstart — get keys, reference a workflow and ship your first flow.
  • API reference — sessions, modes, webhooks, configuration and error codes.