Skip to main content
Version: 11.3.0

Customizable Consent Screen

Customizable Consent Screen lets administrators configure custom Terms and Conditions per verification workflow instead of using the default HYPR consent text. Custom content can be authored via the Control Center UI or via the Affirm API, and is presented to the requester at the start of the verification flow.

Available in 11.3

Customizable Consent Screen is new in HYPR 11.3. Tenant enablement is required — coordinate with your HYPR representative for activation.

What customization controls​

Administrators can configure the following elements per workflow:

  • Custom Terms and Conditions text — replace the HYPR default consent text with organization-specific language
  • Branding context — header, footer, and supporting branding follow the workflow's Affirm Studio kit; the consent body is the customizable element
  • Per-flow assignment — different workflows can use different consent content (one for employee onboarding, another for partner onboarding, etc.)

What stays fixed​

The Entrust (Onfido) consent language required for the underlying document and biometric verification is preserved automatically and presented alongside the custom content. Administrators cannot remove or override the Entrust consent block — it is mandatory for the document verification to proceed.

This ensures custom content can match corporate communication standards without compromising the legal language required by the document-verification provider.

End-user experience​

When the requester begins a verification flow, the consent screen presents:

  1. The customer-authored Terms and Conditions (if configured)
  2. The Entrust consent block (always present, identical content across workflows)
  3. Accept / Decline buttons

If the requester declines, the flow terminates with ABANDONED status and the declination is recorded in the Activity Log.

Configuration via API​

Consent content can also be configured via the Affirm Content Customization API. The API uses the same content-customization schema as other Affirm Studio screen overrides. Use the API for programmatic provisioning (across many workflows) or for multi-language content management where a CMS owns the source content.

Audit and observability​

Consent acceptance and declination are recorded as flow-level events in the Audit Trail, and the consent-version identifier is captured in the Activity Log so compliance reviews can correlate "this requester saw consent version X."