Step Configuration
Each HYPR Affirm verification step has its own configuration page describing what the step does, when to use it, all configurable controls, and the directory attributes it requires.
For the workflow-editor-side perspective (which steps are available, how they're grouped, save/revert), see Configure Verification Steps.
Identity capture
- Login Identifier — always required; captures the requester's work login identifier
- Phone Number / Email Verification — OTP delivery and confirmation
- Document and Biometric Verification — government-issued ID + live selfie + Motion Detection, Dual Document, AML/OFAC, Identity Verification with Document Issuer
- Photo ID and Liveness Capture — lighter alternative to Document and Biometric
- Identity Verification via Verified Credentials — Entra Verified ID presented from Microsoft Authenticator
- Liveness-Only (Anchor Image) — selfie compared to a directory-stored anchor image
Policy and context
- Location — geolocation + IP + Known Locations + IP allow/block + distance + country block
- KYC Compliance Checks (AML / OFAC / Watchlists) — optional compliance screening alongside document verification
Custom
- Custom Verification Step — pluggable single-page application as a verification step, registered via Code Customization API
Approval and attestation
- Approver Chat and Video — live chat / video with approver
- Escalate to Live Chat — automatic escalation on failure
- Attestation — required human attestation before outcome fires
Outcomes
- Verified Outcome — six outcome types for successful verifications
- Unverified Outcome — two outcome types for failed verifications
Profile data each step requires
Most verification steps compare what the requester presents against the profile held in your system of record. Use this table when you plan a flow, and again when you write a User Directory customization that has to supply the data.
| Step | Profile data it requires |
|---|---|
| Login Identifier | The login identifier itself must resolve to a record in the system of record. |
| Phone Number / Email Verification | A mobile phone number or an email address. |
| Location | The full postal address. |
| Document and Biometric Verification | First name and last name. |
| Photo ID and Liveness Capture | None. This step compares the captured selfie against the captured document and does not read profile data. |
| Liveness-Only (Anchor Image) | An anchor image, supplied by a User Image Directory Source customization. |
| Approver Chat and Video | A manager identifier, unless an approver is configured explicitly on the flow. |
| Escalate to Live Chat | A manager identifier, unless an approver is configured explicitly on the flow. |
| Attestation | A manager identifier, unless an approver is configured explicitly on the flow or HYPR automated approval is used. |
| Verified Outcome | None. |
| Unverified Outcome | None. |
Choose steps whose required data your system of record actually holds. Each step you add raises the level of assurance and adds a step for the requester to complete, so select the set that meets your requirement rather than the largest set available.
Related
- Writing Affirm Code Customizations — supplying profile data from a system of record other than Okta or Entra ID
- Configure Verification Steps — steps table grouped by category (workflow-editor view)
- Approvers and Escalation Approvers — approver chain configuration (workflow-level)
- Injectable Outcomes & Retry Limits — per-step retry and failure-outcome configuration
- Network and Location Policy — policy-composition view for the Location step
- Escalation Policy — risk-signal-driven escalation policy