Custom Emails
How Custom Emails works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Custom Emails 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.
Disabling default emails
Disabling default emails is handled by Custom Emails 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.
Invitations
Invitations is handled by Custom Emails 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.
Set up your user invitation URL
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.
AHandle manually creating invitations
AHandle manually creating invitations is handled by Custom Emails 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.
BHandle invitations created via the API
BHandle invitations created via the API is handled by Custom Emails 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.
Send your email
Send your email is handled by Custom Emails 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.
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.