Enroll the authenticator
Overview
Before completing a 3DS challenge during an e‑commerce transaction, the end user must enroll a device authenticator in the issuer application.
The D1 SDK provides a FIDO‑based authenticator for EMV 3‑D Secure (3DS). Enrollment registers the end user’s authenticator on the device for 3DS.
Enrollment flow

Sequence diagram
The diagram below shows the end‑to‑end message sequence for authenticator enrollment.
Prerequisites
The issuer application integrates the D1 SDK and the SDK is initialized.
The issuer application is logged in to the D1 SDK.
The end user is registered in the D1 Platform.
Push notifications are configured in the issuer application.
Each device supports a maximum of one enrolled end user.
A single end user may be enrolled on multiple devices.
Certain Android devices may generate an incorrect attestation payload, which can result in enrollment failure. To mitigate this risk, it is strongly recommended to enroll using a
BIOMETRICauthenticator rather than aPLATFORMauthenticator.
D1 SDK integration
Enroll the authenticator
Next, proceed to Handle the OOB challenge.
Unenroll the authenticator
Call unenrollAuthnCredentials to remove enrollment on this device. The D1 backend and local device storage delete associated enrollment data. Other devices remain enrolled. If the device is already unenrolled, the call succeeds (idempotent).
Customize the prompt message
Android For BIOMETRIC, you can customize the message shown in the biometric prompt dialog. For PLATFORM, customizing the prompt message is not supported.
iOS Customizing the authentication prompt message is not supported.
Last updated
Was this helpful?