Identity orchestration, end to end

An identity orchestration platform runs every identity check from one place instead of stitching point solutions together. Document verification, liveness, face match, device and behavioral signals, government and database checks, and AML screening run as modules inside a single workflow, configured in one dashboard and called through one API.

Yes. The workflow builder is drag and drop. Your team assembles modules on a canvas, starting from a blank flow or a template for cases like identity verification, KYC, KYB, step-up age verification, and account recovery, then publishes without writing code. The same workflow runs whether the session arrives through a hosted link, the Web SDK, or a mobile app.

Condition nodes route users on the output of any module. Each node follows an if-then structure: pick a signal, set an operator and a value, define the path, and chain conditions with AND or OR. Every branch ends in one of four outcomes: pass, fail, warn, or manual review.

Yes. Accepted document types are scoped globally or market by market, drawn from a catalog of more than 4,900 documents, and thresholds are adjustable per check so separate flows can run per region or product line. Verification rules sit above the modules and can force a completed session to pass, fail, or route to review.

More than this page can list. Incode connects through a REST API, web and mobile SDKs, a hosted verification experience, and pre-built connectors across identity and access management, ITSM, HR, CRM, video conferencing, and messaging, with OpenID Connect for anything custom. To check a specific tool in your stack, talk to an expert.

Flagged sessions land in the sessions view with the decision, the score behind every check, and a plain-language summary of what drove the outcome. Reviewers open the connected sessions that Trust Graph surfaces, escalate to manual review, and export an evidence bundle as a PDF where each page carries a hash, so any later change to the document is detectable.

High-risk moments trigger step-up verification: face authentication against the identity enrolled at onboarding, supported by device intelligence, behavioral signals, and velocity checks. Because the same platform ran the onboarding, the step-up compares the user to their verified identity instead of to a password or a one-time code.

Analytics are built into the dashboard, with no external BI tool required. Teams track session volume, funnel drop-off by step, top rejection reasons, and fraud vectors, and build custom widgets from any available signal. Precision, recall, and accuracy views show whether current thresholds catch fraud without rejecting legitimate users.

You choose a deployment region when your organization is created, and that setting carries through storage, processing, and backups. Retention is configurable field by field, role-based controls restrict who can see sessions and identities, and every retention and deletion event is logged for audit.