Product Documentation

Transaction Statuses

V.1

Suggest Edits

Overview

This section outlines transaction statuses, their definitions, and interpretation guidelines. Each status reflects a specific step or result from initiation to completion.

StatusValueDescription
Pending0The expected status while waiting for the user to complete the requested action.
Accepted1
  • Verified transaction (biometric authentication) Accepted status Indicates successful authentication for a Verified transaction, allowing the user to proceed with the action you invoked authentication for.
  • For Get Biometry (selfie request) Accepted status indicates the selfie was obtained with all requested quality and liveness checks completed, and TempId contains data.
  • Get ID Document (Proof request) Accepted status indicates data is available in TempId. Developers should review the data to verify the transaction’s legitimacy. Refer to Process the Proof Results for details.
    Rejected2
    • Verified transaction goes into the Rejected state when the user declines verification or fails to authenticate after multiple attempts.
    • Get Biometry and Get ID Document can also enter the Rejected state, though users typically ignore the request.
      Expired3Indicates the user ignored or did not complete the requested action. The transaction lifetime is configurable via API.
      Error4Indicates an issue occurred. The response body will contain an explanation of the error.
      Canceled5Indicates that a session was canceled.

      🚧

      Rejected Message

      For rejected messages, you would usually find a message similar to this:

      • Not authorized. Biometry verification failed.
      • Not authorized. Liveness detection failed.
      • Not authorized. Biometry verification and liveness detection failed.

      Updated 9 days ago