HaloKYC

HaloKYC / Workflow

Define the policy once. Run it consistently.

A HaloKYC workflow connects the checks you choose, the evidence users provide, and the decision your product receives.

Start buildingRead the docs
Route
6 auditable steps
Contract
REST + JSON
Callback
HMAC-SHA256

One source of truth

Every stage leaves a usable record.

The workflow is more than a sequence of screens. It is the policy reference that ties capture, processing, review, and delivery together.

01

Policy

Versioned intent

The selected workflow determines required evidence, enabled checks, and decision thresholds.

02

Evidence

Adaptive capture

The user flow requests only what the selected workflow needs for that verification.

03

Decision

Readable outcome

Check results resolve to a status, score, and reason your team can act on.

04

Delivery

Verified callback

Your backend receives the outcome through a signed webhook with retry visibility.

Every verification follows the same auditable route.

The flow is sequential because accountability is sequential: define the rule, collect evidence, run checks, write the result, then notify the product that asked for it.

  1. Step 01

    Design policy

    Client chooses selfie, liveness, document, age, and thresholds in a workflow.

    persisted event
  2. Step 02

    Start session

    Backend sends external_user_id, workflow_id, and optional callback_url.

    persisted event
  3. Step 03

    Capture evidence

    User completes only the screens required by that workflow.

    persisted event
  4. Step 04

    Run checks

    Worker runs OCR, face match, liveness, duplicate, and age as needed.

    persisted event
  5. Step 05

    Resolve decision

    Approved, rejected, or manual_review with a readable risk reason.

    persisted event
  6. Step 06

    Notify app

    Final result is sent through a signed webhook and remains available by API.

    persisted event

Start with a workflow ID. Finish with a signed decision.

HaloKYC is policy-driven: your dashboard defines the workflow, the API starts a session against that workflow, and the user capture flow adapts to the enabled services.

  • POST/verifications/start
  • GET/verifications/{id}
  • WEBHOOKPOST signed

Ready when you are

Turn your identity policy into a working flow.

Configure the checks, start a session, and follow the result from capture through callback.

Create your workspace