Multi-Factor Authentication
How Multi-Factor Authentication works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Multi-Factor Authentication 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.
Getting started
Getting started applies specifically to Multi-Factor Authentication. It behaves the same in both environments, and the values it depends on are visible in the dashboard for the environment you have selected.
If the behaviour you see does not match this description, check which environment your API key belongs to before anything else — a staging key against production data is the most common cause.
Enabling MFA
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.
Integrating via the API
Integrating via the API is handled by Multi-Factor Authentication 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.