Version: 11.3.0

11.3.0 Release Notes

HYPR 11.3 is an Enterprise Channel Release.

The Enterprise Release Channel follows a quarterly upgrade cycle, ensuring a stable and predictable update process. This schedule provides organizations with ample time to test, adapt, and implement changes while minimizing disruptions to business operations. With each release, customers receive the latest security, performance, and feature enhancements, allowing them to stay up to date with improvements while maintaining operational stability.

Looking for bug fixes and known issues?

The full, per-item list of bug fixes and known issues for this release — and every prior release — is maintained in the Changelog.

Minimum Supported Versions

Release Date	HYPR Product	Minimum Requirement	Notes
June 24	HYPR Passwordless for Windows 11.3.0	Windows (10 "2004", 11)	Reboot required if upgrading from 7.6 or below; Security Key Support for YubiKey 5 Series with firmware 5.X, YubiKey Bio Multi-Protocol Edition, IDEMIA ID-One on Cosmo 8.2, Feitian K9 Plus and K40 Plus and its offshoots
June 24	HYPR Passwordless for Mac 11.3.0	macOS (High Sierra, Mojave, Catalina, Big Sur, Monterey, Ventura, Sonoma 14.1 [not 14.0], Sequoia, Tahoe)	Security Key Support for YubiKey 5 Series with firmware 5.X and Feitian ePass K9 Plus, K40 Plus and their respective offshoots
June 24	HYPR Mobile App for Android 11.3.0	Android 9.0+
July 15	HYPR Mobile App for iOS 11.3.0	iOS 12.4+	Released later than the other 11.3.0 components — see Breaking Changes.
June 24	HYPR Server 11.3.0	Java Development Kit (JDK) 17	Upgrade to 7.10 required before upgrading to 8.0.0 or higher
June 24	HYPR SDK for Android 11.3.0	Android 9.0+
June 24	HYPR SDK for iOS 11.3.0	iOS 12.4+
June 24	HYPR SDK for Java 11.3.0	Java Development Kit (JDK) 17+

Backward Compatibility

All HYPR components are fully compatible across the three previous/subsequent minor (X.X) HYPR releases.

Breaking Changes

[HYPR Mobile App for iOS] The HYPR Mobile App for iOS 11.3.0 ships separately from the rest of the 11.3.0 components — the other components release on June 24, and the iOS app follows on July 15. Until the 11.3.0 build is available in the App Store on July 15, customers should continue using their currently-deployed iOS app version.
[API] The /rp/api/versioned/recoverypin/retrieve endpoint now requires an access token minted under the controlCenterAdmin RP app. Tokens minted under any other RP app return 403 Forbidden. Integrations already calling this endpoint with a Control Center token are unaffected.

HYPR Affirm

New Features

▸ Directory Image Writeback

Organizations can push document photos and selfies captured during an Affirm workflow directly to an enterprise directory or external system (Entra ID, Okta, Ping, or a custom endpoint) without retaining those images in HYPR, supporting privacy-by-design and data minimization requirements. Images are transmitted immediately following a verification outcome and are not stored in the HYPR database.

Configurable writeback target with per-tenant credentials.
Per-workflow and per-step enablement (Photo & Liveness; Document & Biometric).
Per-image-type attribute mapping (selfie, document front, document back).
Configurable rotation / frequency policy per user (for example, update at most every 12 months).
Outcome gating (PASS only / PASS + no escalation / PASS + manual approval).
Synchronous retry with configurable attempt limit and terminal-failure handling.
Full audit trail via writeback lifecycle events (AFFIRM_WRITEBACK_TRIGGERED, _SUCCESS, _SKIPPED, _FAILURE, _EXHAUSTED).
Code customization hook (USER_DIRECTORY_IMAGE_WRITEBACK) for organizations that need custom writeback logic.
Image repository configuration screen refreshed for clearer per-target setup and per-image-type mapping.
Document capture is available at the Photo ID and liveness step regardless of prior step state, so users can re-submit a document image without restarting earlier steps.
When writeback is configured as required for a verification, a writeback failure after approver approval is reflected in the final outcome, keeping the directory image and the verification result consistent.

▸ Risk Policy Builder

A Control Center editor where administrators define how Affirm responds to risk signals during a verification workflow. Policies are organized into Policy Evaluation Kits; each kit is assigned per verification flow, with customizable built-in defaults shipping for common workflows. See Risk Policy Builder for full configuration details.

Per-action configuration — for each protected action (for example, Reading IDV Outcome), the kit exposes the action's emitted Risk Signals (read-only reference), an Action Retry Budget (maximum attempts and time window), and a list of Evaluation Rules.
Predicate-driven Pass and Fail rules — each rule combines one or more predicates (risk signal + operator + value) with AND/OR grouping. Available operators include equality, range, set membership, and substring matching.
Fail-rule outcomes — Deny the action, Escalate immediately, Redirect immediately, or Continue on failure (escalate). Escalate-type failures carry an admin-supplied escalation reason that surfaces in audit and review surfaces.
Policy ledger — each policy evaluation appends a ledger entry to the Activity Log identifying the rules that fired, the signals that matched, and the action taken, providing per-verification policy auditability.

▸ Observability refresh

Affirm observability surfaces (CC Logs, Helpdesk logs, Scorecards, API results, and Events) received a coordinated refresh that unifies status semantics, surfaces evidence packages per step, and dynamically renders only the steps and attributes configured for the workflow.

Standardized status semantics replace "N/A / Not Applicable" with explicit outcomes: VERIFIED, UNVERIFIED, ABANDONED, SKIPPED, ERROR, and TIMED_OUT. Outcomes also report retry-attempt counts at the workflow level and per step, and the system clearly distinguishes system errors from user abandonment.
Verification Flow ID propagated across CC Logs, Helpdesk logs, API responses, and Affirm Events, enabling end-to-end correlation for audit and support.
Activity Log UI refreshed in both Control Center and Helpdesk surfaces, including a redesigned table view and per-record detail view with evidence-package display per step.
Step-conditional rendering: log surfaces only display steps that are actually configured in the workflow, removing empty "Not Applicable" placeholders.
Attribute-conditional rendering: tenants can configure logs to display only the attributes used in their workflow (for example, hiding location when not configured).
Document type uploaded during verification is captured in Logs, Events, and Scorecards, enabling analysts to filter and report on outcomes by document type.
Affirm verification attempts from geographically blocked regions surface a user-friendly error message rather than a generic failure.

▸ Dual document verification

Affirm workflows can verify two identity documents per requester against a single live biometric capture. The Entrust SDK requests a second document upload at the end of the standard capture flow; both document checks reuse the original live photo or video, so the user does not repeat live capture. Supports verification flows that require two identity documents (for example, a government-issued ID plus proof of residence) while reducing end-user friction and improving completion rates compared with chaining separate flows.

Administrators can configure custom Terms & Conditions per workflow rather than using the default HYPR consent text. Custom content is configured via UI or API; required Entrust consent language is still included automatically alongside the customer-supplied text.

▸ Custom verification steps

Affirm workflows support pluggable custom verification steps, allowing organizations to insert their own verification logic alongside HYPR's built-in verification steps. Custom steps are configured via the Code Customization API; supporting functionality (CSP policy validation) makes custom steps usable in production verification flows.

▸ Location and network policy expansion

Affirm risk policy controls include two additional location-based enforcement capabilities.

Sanctioned nation-state enforcement: administrators can configure a tenant-level sanctioned-country list. Verification workflows that originate from a sanctioned country are blocked before any verification step executes. Includes optional admin override and audit logging of blocked attempts.
Multi-headquarters location policy: organizations with multiple primary locations can define location policies that reflect their distributed geographic footprint. Optional trusted IP ranges may be associated with each configured headquarters. Location validation succeeds when the user is within the configured threshold distance of any defined headquarters.

▸ Extended document-type restriction with National ID Document

The document-type restriction control adds National ID Document as a configurable allowed/disallowed type, complementing the existing passport, driver's license, and residence permit options.

▸ Configurable verification data retention

Administrators can set distinct data-retention periods for biometric and document verification data within a verification workflow, supporting data-residency and minimization requirements.

Notable UI/UX Changes

▸ Risk Policy Builder UI

New Control Center policy editor for Affirm verification workflows. Administrators manage Policy Evaluation Kits, assign them per workflow, configure per-action retry budgets and evaluation rules, and review the policy ledger that records how each kit evaluation resolved.

▸ Activity Log UI refresh

Activity Log tables and detail views have been redesigned in both Control Center and the Helpdesk portal, with new columns and Verification Flow ID surfaced for easier audit.

Refreshed table view:

Refreshed Affirm Activity Log table view in Control Center

Per-record detail view (opened by clicking a row):

Refreshed Affirm Activity Log detail view for a single verification record

▸ Directory image writeback configuration

A new configuration section in Control Center lets administrators define writeback targets (Entra ID, Okta, Ping, or a custom endpoint) for identity verification images. Settings include per-tenant credentials, retry attempt limits, rotation rules, and writeback lifecycle event history alongside standard verification records.

Affirm verification flow Image Directory configuration tab in Control Center

▸ Location and network policy controls

Location policy configuration now includes a sanctioned-country block list and support for multiple headquarters locations. Combined IP, sanctioned-country, and headquarters-proximity evaluation results surface in Control Center logs.

Affirm Location Settings with Known Locations panel and sanctioned-country block list

Enhancements

▸ Per-tenant custom-step execution timeout

The execution timeout for custom code steps in Affirm workflows is now configurable per tenant rather than fixed. Organizations with file uploads or other operations that require longer processing windows can adjust the timeout without needing custom engineering support.

▸ SMS OTP field auto-focus

The SMS OTP code input field auto-focuses when the step loads, reducing manual taps for users completing SMS-based verification.

▸ Workflow engine performance

Performance improvements across the Affirm workflow engine reduce end-to-end verification latency on high-volume tenants.

Consent content caching reduces redundant fetches.
An initial action-handler registry replaces per-step service lookups.
Verification-context propagation between workflow steps avoids redundant database lookups.

▸ Unified workflow configuration schema

Internal workflow configuration schema unified for consistency between Control Center UI and Affirm API. Existing workflow configurations are migrated automatically and continue to function unchanged; no customer action is required.