Magic Auth
How Magic Auth works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Magic Auth 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 Magic Auth. 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 Magic Auth
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.
Integrating via the API
Integrating via the API is handled by Magic Auth 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.