Orchestration

Routing each user through the right checks instead of running all of them.

A low-risk customer might get a quick document and selfie check, while a higher-risk one gets extra steps, and the system decides which path each person takes.

Policy-driven coordination of verification services, data sources, and decision logic across a configurable flow. A flow is the ordered set of steps a user goes through, and policy-driven means business rules, not fixed code, decide the path.

An orchestration layer typically does several jobs:

• Routing, by choosing which checks to run for each user based on risk, region, or product.
• Sequencing, by running checks in a sensible order and stopping early when the answer is clear.
• Vendor coordination, by calling several verification providers and data sources through one integration.
• Fallbacks, by switching to another provider or method when one fails or is unavailable.
• Decisions, by combining results into approve, decline, or review outcomes.

A typical orchestrated flow works like this:

1. A user starts verification, and the system looks at known risk signals.
2. The orchestration layer picks the path that fits the risk, such as a light check or a deeper one.
3. It calls the needed services and collects the results.
4. A decision engine applies policy and returns an outcome.

Orchestration sits next to terms that are easy to mix up:

• Workflow builder is the visual tool people use to design the flows that orchestration runs.
• Decisioning engine is the component that turns results into approve, decline, or review.
• Rules engine applies explicit if-then logic inside the flow.