Solutions / Use Case

Customer Onboarding and KYC Flows

KYC onboarding combines synchronous API calls, asynchronous checks, human decisions, and long-running process state. This page shows a practical orchestration model using Unmeshed workflow primitives.

Start Building

Typical KYC Flow

A realistic onboarding flow keeps one durable case from request intake to final activation:

START
  -> Receive onboarding request
  -> Validate input
  -> Create customer record
  -> Identity verification (external API)
  -> Document upload and validation
  -> AML / sanctions screening
  -> Risk scoring (decision table)
  -> Switch: auto approve | manual review | reject
  -> Account activation
  -> Notify systems
END

1. Intake and Input Validation

Workflow entry can come from an HTTP trigger, backend API, or event source. Validation should happen before any expensive external call.

  • Start from HTTP trigger, backend API call, or event ingestion.
  • Validate required fields early using a Script or Decision Table step.
  • Create a durable case context immediately to avoid losing in-flight requests.

2. Identity Verification Integration

External KYC providers are handled as explicit workflow steps. Each provider response is captured in context and can be traced per case.

  • Submit identity verification to external providers through HTTP steps.
  • Store provider references (for example verification IDs) in workflow context.
  • Route failed provider calls through retry policy and explicit failure paths.

3. Parallel Screening and Decisioning

AML and sanctions checks are naturally parallel. Consolidate results and pass one structured payload into rule-based scoring.

  • Run AML, sanctions, and related checks in parallel branches.
  • Aggregate risk signals into one normalized decision input object.
  • Use Decision Table rules so policy can evolve without orchestration rewrites.

4. Routing, Human Review, and Finalization

KYC decisions usually include both automated and manual paths. Human-in-the-loop steps handle reviewer approvals without losing state or introducing separate coordination systems.

  • Route to auto-approve, manual review, or reject through Switch conditions.
  • Send high-risk cases to Human-in-the-Loop steps for reviewer actions.
  • Finalize by activating account and notifying downstream systems.

Build Your First KYC Workflow

Start with one onboarding flow, then incrementally add checks, review paths, and policy rules without rewriting core application services.

Get Started