Device authenticator

During the MFA enrollment step of a registration journey, customers can enroll a mobile device as an authenticator. After enrollment, the device can be used to approve authentication requests through your brand's mobile application.

📘

Device enrollment options

Customers can enroll a device:

  • During registration, as part of MFA enrollment.
  • During a login journey, when device enrollment is configured.
  • From My Account under Security settings > Multi-factor authentication (MFA).

What customers experience

  1. When prompted to enroll an MFA method, the customer selects Device.
  2. Strivacity displays the Enroll a device screen with a QR code.
  3. The customer scans the QR code using the brand's mobile application and completes the enrollment in the application.
  4. During enrollment, the customer can name the device. If no name is provided, Strivacity generates a default name from the available device make and model information.
  5. After enrollment completes, Strivacity confirms that push notification authentication was successfully added, and the customer continues their journey.
📘

If enrollment is optional, customers can select Skip for now and enroll a device later from My Account.

Managing enrolled devices

Customers can enroll multiple devices. Enrolled devices appear under Security settings > Multi-factor authentication (MFA) > Device authenticators in My Account.

Customers can:

  • select Add to enroll another device using the same QR-code enrollment process;
  • remove an enrolled device.
📘

Customers cannot remove a device authenticator if it is their only configured MFA method.

Settings that affect this step

  • Adaptive Access policy: Controls whether customers can enroll a device authenticator and whether enrollment is optional or mandatory.
  • Push notification configuration: Controls the mobile application, authentication method, deep-link URL, and platform-specific delivery service configuration.
  • Branding policy: Controls the appearance of the enrollment screens displayed in the web journey. The appearance of screens within the mobile application is controlled by the application itself.

What happens next

After enrollment, the customer continues to the next step of the journey. The enrolled device is available as an authentication method during subsequent logins.

See Device authenticator in the login journey for the authentication experience.



Did this page help you?