Skip to content
Paycux
Custom Domains

Authentication API Domain

How Authentication API Domain works in Paycux, what it is for, and the smallest setup that gets it running.

Configuring a domain

Verify a domain before you let it drive access. Paycux issues a TXT record; once it resolves, the organization owns that domain and users arriving with a matching email address are routed to its connection.

Verification is re-checked periodically. If the record is removed, the domain returns to unverified and routing stops — it does not silently keep working.

Custom domains for SCIM endpoints

Directory Sync keeps your user list in step with the customer's directory. Paycux receives create, update and delete operations and normalizes them into a single shape regardless of the source system.

Deletes arrive as deactivations. Treat a deactivated user as a user who can no longer sign in, and decide separately whether to delete their data.

Using custom domains in SDKs

Using custom domains in SDKs applies specifically to Authentication API Domain. 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.

Navigate to Domains configuration

Navigate to Domains configuration is configured per environment in the dashboard, so staging and production can differ while your application code stays identical.

Changes take effect on the next request. There is no deploy step and no cache to clear.

Add an email domain

Add an email domain applies specifically to Authentication API Domain. 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.

Create CNAME records

Create CNAME records applies specifically to Authentication API Domain. 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.