01 /
Multiple evidence types
Model identity, document, business, and institutional evidence with provenance and purpose. Capture requirements depend on the workflow, not a universal checklist.

Verification Engine / Evidence with context
Structured identity, document, business, and compliance workflows designed to connect evidence, review, and an accountable decision.
More than a successful check
Verification starts with a question: what needs to be established, for which purpose, and using what evidence? Collecting more information is not a substitute for defining the right scope.
Verification Engine’s role is to organise checks and review around that question, with understandable states and an evidence trail that survives beyond the initial result.
Consistent foundations
01 /
Model identity, document, business, and institutional evidence with provenance and purpose. Capture requirements depend on the workflow, not a universal checklist.
02 /
Make missing evidence, uncertainty, and escalation visible. Automation should not silently convert an inconclusive check into a definitive judgement.
03 /
Keep the actor, reasons, evidence references, and review events traceable, with retention and access governed by policy.
The evidence lifecycle
A coherent workflow includes the moments when evidence is incomplete, a provider is unavailable, or a person disputes the result.
Explain what is requested and why. Limit collection to the evidence required for the authorised workflow.
Evaluate evidence using the configured checks and record provenance. Provider coverage, liveness methods, and accuracy require separate validation.
Distinguish pending, inconclusive, and completed work. Escalate sensitive or uncertain outcomes to an authorised reviewer.
Record reasons, lifecycle events, and the relevant appeal path. Apply expiry, retention, and access boundaries to the resulting evidence.

Clarity when the answer is not simple
People should understand what is happening to their evidence, what is still needed, and where to seek help when a result seems wrong.
The product direction keeps human oversight and explanation in the workflow, rather than presenting every check as an instant yes or no.
Protect the evidence
Identity documents and biometric evidence, where required by an approved workflow, need appropriate collection, storage, access, and retention controls. They do not belong in public pages or client-side logs.
This page explains an architectural model. It does not collect evidence, run checks, certify provider coverage, or promise verification accuracy or turnaround times.
Review evidence protectionConnect verification to the wider system
Explore how the API layer connects verification workflows and lifecycle events to your product architecture.