Welcome to Incode

Incode is an identity verification (IDV) platform. It helps:

• Onboard new customers by confirming their identity exists and they are who they claim to be.
• Authenticate returning customers against their identity established during onboarding.

Incode combines document verification, biometric matching, liveness detection, and risk scoring. You can configure the user's journey through these verification checks according to your use case, region, and regulatory requirements. The Incode Platform provides a single ecosystem for configuring and integrating IDV, including low-code and no-code solutions. Review the Choose Your Integration Path section below for an overview of ways to implement Incode.

Key Concepts

Review these key concepts before you begin:

• Onboarding Session: A container for one customer's identity verification process. Every image, score, and result is tied to a unique Session ID, referred to as interviewId in the API. A new session is created for each verification attempt.
• Module: A single step within a session. Examples include ID document capture, selfie capture, liveness check, face match, and eKYC database lookup. You choose which modules run and in what order by configuring Workflows in Dashboard.
• Score and Result: When customers complete modules, Incode returns a numerical score for each module and an overall session score. Your backend reads this score to make a decision: approve the customer, route them to manual review, or reject the attempt.

Read the full glossary​ for more terms and definitions.

Choose Your Integration Path

Incode supports four integration methods. Choose the one that fits your use case.

If you're not sure which to choose, see the full comparison of integration options by platform.

How a Verification Session Works

Regardless of the path you choose, every Incode integration follows the same four-step sequence:

1. Your backend creates a session. Call POST /omni/start with your API key. Incode returns a session token. Store this token; all subsequent calls for this customer's verification are scoped to it.

   → Start session API reference

2. Your frontend runs the capture modules. The SDK or Workflow guides your customer through the steps you have configured: ID scan, selfie, liveness check, and any others. Pass the session token to the SDK so all captured data is attached to the correct session.

   → Onboarding process overview

3. Mark the session complete. After the last module runs, call POST /omni/finish-status from your backend. This step is required; it signals to Incode that data collection is done and triggers final score calculation.

4. Fetch scores and make a decision. Read the verification score from the API or wait for Incode to send it to your backend via a webhook. Use the score to approve the user, route them to manual review, or reject the attempt.

   → Session lifecycle and status reference
   → Webhooks overview

What to Read Next