Skip to main content
Version: 11.3.0

Branding and Customization

HYPR Affirm exposes several end-user-facing branding and customization surfaces. Each one is controlled by a Control Center administrator and applies automatically to the requester, approver, or recipient who encounters that surface during a verification flow.

This section is the user-experience view: what gets branded, what the recipient sees, and which customization surface controls which element. For the admin walkthrough on configuring each surface, follow the cross-link inside each page.

Custom Branding — the cross-product baseline​

Custom Branding is the cross-product visual baseline HYPR uses to identify your organization across every product surface — Control Center, Device Manager, Affirm, and the Helpdesk portal. The logo, color theme, background, Company Name, and Support Email you configure under Custom Branding appear consistently to every end user, approver, and agent who interacts with HYPR.

When Custom Branding is configured at the Control Center level, the following Affirm surfaces inherit those values automatically:

  • Verification screens — the logo, background, and primary color shown to the requester on the welcome screen, the per-step screens, and the outcome screen
  • Approver review surfaces — the same branding applies to what a human approver sees when reviewing an escalated verification
  • SMS and email notifications — the {CompanyName} and Support Email placeholders used in notification templates are sourced from the Company Identity section of Custom Branding
  • Helpdesk portal — the agent-facing Helpdesk surface uses the same logo and color scheme

For the configuration walkthrough — logo upload, color picker, Company Identity fields — see Custom Branding (Control Center documentation).

What Custom Branding does not control​

Custom Branding handles the visual baseline. The following Affirm-specific elements are controlled by separate, scoped customization surfaces (covered in the pages linked below):

The general rule: Custom Branding is global and visual; the other customizations are scoped (per-workflow, per-screen, per-notification) and content-focused. Most deployments configure Custom Branding once at the Control Center level and then use Affirm Studio and notification customizations for any workflow-specific overrides.

Affirm-specific customization surfaces​

The remaining customization surfaces are Affirm-specific. Each layers on top of the Custom Branding baseline.

Affirm Studio​

Per-screen content and styling on every verification screen the requester and approver see — titles, descriptions, instructions, button labels, typography, button colors, layout. Built and managed as workflow-assignable kits.

SMS Notification Branding​

The three SMS message categories Affirm sends — OTP, approver invitations, Helpdesk invitations — and the {CompanyName} placeholder pulled from Custom Branding for each.

Email Notification Customization​

The email categories Affirm sends — approver invitations, email-channel OTP, Helpdesk invitations, outcome confirmations — and the cross-product template system that backs them.

For admin configuration​