Skip to main content
This document is a stage-by-stage reference of every event recorded in the session journey. For the concept of the session journey and how to interpret it, see the Session Journey overview first.

How to read the tables

  • SourceFE: an action observed on the user’s screen · BE: a verification or decision executed on the server
  • User impactNONE no impact · BLOCKED blocked · RETAKE recapture / retry · PENDING hold · REJECTED rejected · APPROVED approved · COMPLETED stage completed
The tables are organized by stage, but events within a single stage may run concurrently. Keep in mind that the display order does not necessarily imply causality.

Session start · entry

Pre-checks · blocking (Guard / policy)

Observing API calls from the screen (FE)

These events record the moment the screen called a specific API. The server-side result of the same action is logged separately in the corresponding BE event (marked with below). If the call itself fails, it is logged as API_ERROR.

Screen · environment observation (FE)

Camera · capture (FE)

Auxiliary authentication (SMS · email · address · account)

STEP1 — ID document

Pre-STEP2 (account verification)

STEP2 — selfie · face

Face Auth (add-on)

Knowledge-Base verification

Final decision · notification

Post-process

Final decision reasons

Use the reason value of the final decision events (REJECTED · PENDING) to determine the exact reason.

Rejection (REJECTED) reasons

Hold (PENDING) reasons

For the mapping between rejection/hold reasons and the error codes / error pages shown to the user, also see the Error codes and pages document.