Skip to main content
Version: 11.3.0

Verification Status Values

HYPR Affirm records the state of every verification as a small set of status values. The Activity Log shows a workflow status and a decision for each verification, a status for each step and a result for each check within a step. The workflow API returns a result for each verification.

Workflow Status​

The workflow status says where a verification is in its lifecycle. The following table lists each value, the label the Activity Log shows and its meaning.

ValueActivity Log labelMeaning
NOT_STARTEDNot StartedThe verification was created through the Affirm API or the Helpdesk and the requester has not started it.
IN_PROGRESSIn ProgressThe requester has started the verification and no decision has been made yet.
COMPLETEDCompletedThe verification finished and a decision was made. The decision says whether the requester was verified.
ABANDONEDAbandonedThe requester started the verification and closed the browser or tab before a decision was made.
EXPIREDExpiredThe verification timed out before a decision was made: the verification page stayed open without activity until the session timed out, no approver joined a live chat in time or the approver did not complete the review in time.
ERRORErrorA system error occurred during the verification and may have prevented it from completing.

Records created before the workflow status was introduced show Completed when they carry a decision and Not Applicable otherwise.

Decision​

The decision says whether the requester was verified. The following table lists each value.

ValueActivity Log labelMeaning
APPROVEDVerifiedThe requester was approved, by an approver or by HYPR automated approval. The Verified Outcome applies.
DENIEDUnverifiedThe requester was declined or failed verification. The Unverified Outcome, or the failing step's failure outcome, applies.
NOT_ASSOCIATEDUnverifiedNo decision is associated with the record.

While a verification is In Progress or Not Started, the Unverified label appears in gray rather than red.

Workflow API Result​

The workflow API, GET /cc/api/idv/workflow/{id}, returns isCompleted and a result for a verification. The following table lists the result values.

ValueMeaning
SUCCESSThe attestation result is a success; the requester was verified.
FAILUREThe attestation result is a failure, a timeout or skipped; the requester was not verified.
NONENo attestation result exists yet.

Step Status​

Each step in a verification has its own status. The following table lists each value.

ValueMeaning
PENDINGThe step is enabled for the workflow and has not run yet.
IN_PROGRESSThe requester is at this step.
COMPLETEDThe step finished. Its checks say whether it passed.
ABANDONEDThe verification was abandoned while this step was in progress.
EXPIREDThe session expired while this step was in progress.
ERRORAn error occurred while the step was running.
NOT_ENABLEDThe step is not enabled for the workflow.

Check Result​

Each check within a step, such as the phone number match, the one-time code or the IP list check, records a result. The following table lists each value.

ValueMeaning
PASSThe check passed.
FAILEDThe check failed.
PENDINGThe check is enabled and has not run yet.
CANCELEDAn earlier blocking action in the workflow prevented the check from running.
NOT_CONFIGUREDThe check is not enabled for the workflow.
NOT_APPLICABLEThe check was enabled but was not required for this verification.
NOT_ASSOCIATEDKept for older records.

Retry Counters​

Affirm counts failed attempts for each requester and verification flow, and for each step within a verification. These counts drive the workflow retry limit and each step's Retry Limit; see Injectable Outcomes and Retry Limits.

Reading Status Across Surfaces​

Use the Workflow ID to correlate a verification across surfaces. The Activity Log shows the workflow status and decision, the workflow API returns the result, and the AFFIRM_WORKFLOW_RESULT audit event records the end of each verification.

Status vs. Error Code​

HYPR Affirm distinguishes between status (the categorical outcome of the verification) and error code (a more granular identifier of the specific error, when applicable). For a step with the ERROR status, the Activity Log records the error message and status code where one is available.

For the full HYPR error-code catalog, see HYPR Error Codes Troubleshooting Table.

  • Observability Concepts: how the status values tie together with the Workflow ID, evidence packages and other observability mechanics
  • Activity Log: primary per-requester record view where status is the headline field
  • Audit Trail: verification flow configuration changes and per-verification events, each with a Success or Failure status
  • HYPR Error Codes: granular error code reference