Workflow Configuration

A verification flow is the core configurable object in HYPR Affirm. It combines the verification steps, retry policy, approvers and outcome that make up a single end-to-end verification. This section covers each part of workflow configuration in order: create the flow, configure its steps, set retry and injectable outcome behavior, assign approvers and escalation approvers, and optionally register a custom verification step.

In This Section

Create and Manage Verification Flows

Create a verification flow, choose its workflow type (Onboarding, Recovery Flow, CC Admin or Custom), assign an application and manage the flow list. Start here for any new workflow.

Configure Verification Steps

Choose which verification steps the flow runs and configure each one: Login Identifier, Phone Number / Email Verification, Location, Verified Credential, Document and Biometric Verification (with Motion Detection and Dual Document options and KYC compliance checks), Photo ID and Liveness Capture, Approver Chat and Video, Escalate to Live Chat and Attestation. Steps always run in a fixed order. The page covers which steps are required and the step-level configuration.

Injectable Outcomes and Retry Limits

Configure how a step responds to failure: the retry attempt count, the retry time window and what happens after retries are exhausted (deny, redirect to URL, or continue with or without escalation to live chat). The page also explains how the workflow-level retry limit and block duration relate to the per-step settings, and shows the screens a requester sees after a failed step.

Approvers and Escalation Approvers

Assign the approver who reviews the verification before the outcome fires: the requester's manager, a specific email address, an approver supplied per verification through the API, or HYPR automated approval. Also assign the escalation approvers who handle a verification when a step fails and escalates to live chat.

Custom Verification Step

Register a custom verification step through the Code Customization API. Use it when your organization needs a verification check that Affirm does not provide, such as proprietary data sources, internal compliance lookups or organization-specific identity assertions. The page is part of the Step Configuration section.