UX guidance

Handling cancellations

Due to the nature of the protocols involved, it is unlikely that a legitimate user would complete the entire verification flow and for your backend to then receive an error. In practice, if a user encounters an issue — an unsupported wallet, a connectivity problem, or confusion with the flow — they will close the modal. When this happens, all your application knows is that the user cancelled.

Design your UX around this: treat cancellation as the primary “unhappy path.” Consider offering the user a way to retry or contact support, rather than showing a generic error message.

Privacy and consent

The SDK does not display a privacy policy or consent screen before launching the verification flow. Your application is responsible for:

• Informing the user what data you are requesting and why.
• Displaying your privacy policy before starting verification.
• Obtaining any consent required by your jurisdiction’s regulations.

Choosing a display mode

The verification UI can render in three modes — full-screen overlay, embedded card, or raw content — so you can match the look and feel of your application. See Display modes for details and container setup.