Know who's joining your product.

What happens inside

Five checks. One explainable decision.

1. 01DocumentPolicy-gated: passports and IDs where capture is lawful. Ghana Card goes authoritative-first
2. 02LivenessPresentation-attack detection on a live capture
3. 03Face matchLive face against the document portrait
4. 04FraudDevice, velocity, reuse and duplicate-face signals
5. 05DecisionApprove, review or reject — with reason codes

Every automated check records its engine, model version, configuration and threshold version.

Built for developers

One request starts an onboarding.

curl https://api.identityos.dev/v1/onboarding/sessions \
  -H "Authorization: Bearer sk_test_••••" \
  -H "Idempotency-Key: 6f1c-onboard-ama" \
  -d client_reference="kp_user_29481" \
  -d checks[]=document -d checks[]=liveness \
  -d checks[]=face_match -d checks[]=fraud \
  -d redirect_url="https://klarapay.app/welcome"

{
  "id": "onb_8Kq2x1",
  "status": "created",
  "hosted_url": "https://verify.identityos.dev/s/onb_8Kq2x1",
  "expires_at": "2026-10-02T10:12:00Z"
}

Signed webhooks: onboarding.started, .completed, .review_required, .rejected, .expired. Idempotency, replay protection and retries built in.

Built for operations

Reviewers see evidence, not guesswork.

Security

Sensitive data stays inside.

Identity vault

Document images, liveness captures and biometric representations are stored separately, accessed via short-lived signed URLs.

Audit trails

Every view, decision, export and deletion is an append-only event.

Minimal client data

Clients receive a verified profile and check summaries — never raw images or templates by default.

Access controls

Organisation-isolated data, least-privilege roles, separate sandbox and production.

Provider-agnostic

Document, biometric and fraud engines sit behind adapters and can be replaced.

Explainable decisions

Reason codes, checks performed and rule versions are stored with every outcome.

Future-ready verification

Ready for authoritative identity.

Document checks, liveness and face match confirm that a real person holds a genuine-looking document. They are not the same as verifying identity against a national register.

IdentityOS includes an authoritative identity provider adapter so an approved provider can be connected later without changing client integrations. Today, every result reports authoritative_identity: not_performed.