Identity orchestration
Also known as: Verification orchestration · Identity decisioning platform · Onboarding orchestration · Identity workflow orchestration
A layer that coordinates the many checks in an identity flow — document, biometrics, databases, watchlists, anti-fraud — deciding which to run, in what order, and what to do with each result.
Legal basis
NIST SP 800-63-3 — Digital Identity Guidelines
Verifying identity today involves many vendors and checks, and wiring them together by hand is brittle. Orchestration is the layer that sequences those calls: it runs the document check, then liveness, queries an authoritative source, passes through watchlist screening — and conditions each step on the last, stopping early when there is already an answer and adding friction only when risk appears.
The value is in decoupling policy from integration: reordering the checks, swapping a vendor or tightening a rule becomes configuration, not a code rewrite. It is what identity platforms call *orchestration*, and it works hand in hand with the decision engine, which produces the verdict from the signals orchestration has gathered.
Frequently asked questions
What is identity orchestration?
It is the layer that coordinates the various checks in a verification flow — document, biometrics, authoritative databases, watchlists, anti-fraud — deciding which to run, in what order, and how to react to each result, without hand-coding every integration.