Liveness verification

Liveness verification in a layered identity workflow

Liveness verification provides an additional signal about the capture session. It is most useful as part of a layered workflow with clear user instructions, response handling, and escalation rules.

Use layered evidence

Liveness does not replace identity-data verification or selfie comparison. BOIVA IDVC brings these supported signals into one comprehensive verification scope.

Prepare the capture experience

Set clear device, camera, lighting, and network expectations before the verification step. Distinguish capture-quality issues from verification outcomes in user-facing messages.

Define safe outcome handling

Map each documented response to a controlled application state. Avoid revealing internal thresholds, and provide a support or review path when a user cannot complete the normal flow.

  • Limit retries according to your risk policy.
  • Log technical events without storing unnecessary sensitive data.
  • Monitor completion and exception patterns using approved local fixtures in non-production environments.

Test the complete decision path

Exercise successful capture, poor capture, interrupted connectivity, timeout, and an inconclusive outcome with approved non-production fixtures. Confirm that each state preserves user context and reaches the intended retry, support, or review destination.