Enrollment UX
How Enrollment UX works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Enrollment UX is part of the Paycux platform. This page explains what it does, when to reach for it, and the smallest working setup you can ship.
Everything below applies to both environments. Build and test in staging, then promote the same configuration to production without changing your code — only the API key and client ID differ.
Provide multiple methods
Provide multiple methods is handled by Enrollment UX rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Let users choose their primary method
A user record holds the identity Paycux resolved for the person: email, name, verification state, and the identities they have linked. It is the object your application should key on.
Users are unique by email within a project. When the same person arrives through a second provider, Paycux links the identity to the existing user rather than creating a duplicate.
Setup a totp factor accessibly
Paycux supports time-based one-time codes and SMS. Enrollment returns a secret and a QR payload; verification exchanges a code for a factor that is then attached to the user.
Always issue recovery codes at enrollment. Without them, a lost device turns into a support ticket that only you can resolve.
Interoperable one-time-passcode input
Magic Auth sends a six-digit code to the user's email address and exchanges a correct code for a session. There is no password to reset, phish or leak.
Codes expire after ten minutes and are single-use. Rate limit requests per email address so the endpoint cannot be used to send mail on your behalf.
Provide the right affordance
Provide the right affordance is handled by Enrollment UX rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Autofill
Autofill is handled by Enrollment UX rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Validation
Validation is handled by Enrollment UX rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.