Waitlist
How Waitlist works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Waitlist 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.
How the waitlist works
How the waitlist works is handled by Waitlist 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.
Who can sign up when the waitlist is enabled
Who can sign up when the waitlist is enabled is handled by Waitlist 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.
Enabling the waitlist
Enabling the waitlist is handled by Waitlist 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.
Additional fields
Additional fields is handled by Waitlist 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.
Confirmation email
Confirmation email is handled by Waitlist 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.
Approving and denying entries
Approving and denying entries is handled by Waitlist 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.
Waitlist webhooks
Webhooks deliver each event to your endpoint over HTTPS with a signature header. Verify the signature before you trust the body, and respond with a 2xx status within thirty seconds.
Delivery is at-least-once, so make your handler idempotent — key it on the event ID and ignore an ID you have already processed. Failed deliveries retry with exponential backoff for twenty-four hours.