Skip to content
Paycux

Documentation availability

Paycux is in private beta. Most pages describe roadmap or reference material. The implemented boundary is published at docs/API_CONTRACTS.md in the release source and under What exists today in this documentation.

Custom Domains

Organization Setup Domain

How Organization Setup 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.

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 Organization Setup domain

Organization Setup is a hosted set of screens your customers use to configure their own connection. You generate a signed link, they finish the setup, and you stay out of the email thread.

Links are single-purpose and expire. Generate one per task — SSO setup, directory setup, domain verification — rather than one link for everything.

Create CNAME records

Create CNAME records applies specifically to Organization Setup 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.