Loading page
Organization Setup
End users of your application create organisations and invite colleagues with single-use links. Your team registers applications and reviews organisation members from the console. A self-serve portal for your customer's IT administrator is planned.
Available in part — Organization Setup: Organisation creation, single-use invites, console review and one-step application onboarding exist today; the IT-administrator portal does not. Items listed as planned below cannot be enabled yet. What Paycux provides today.
Status
How it works today
From /dashboard/connect an owner or admin names the application, chooses an environment and an identity mode. The project, its first environment, the setup draft and the audit records are created in one transaction.
In your application, a signed-in user calls the organisations API with their realm access token. The caller becomes the organisation's owner.
Owners and admins invite colleagues by e-mail with a role. Your team reviews members and pending invites in the console and can revoke an invite.
Invites
An invite returns its token exactly once. Paycux stores only a SHA-256 hash, expires the invite after 7 days and accepts it only from an identity whose verified e-mail address equals the invited one.
Console
Each environment lists the organisations its end users created, with active member and pending invite counts. Opening one shows members and invites with masked e-mail addresses. Invite tokens never leave the API.
Available today
Each item marked available is a route or a console screen today. The planned item cannot be enabled from the console.
Requests
End-user routes carry a realm access token and the scope of that token. Console routes carry the dashboard session cookie.
1curl -X POST https://api.paycux.com/v1/billing/organizations \2 -H "Authorization: Bearer <realm access token>" \3 -H "Content-Type: application/json" \4 -d '{5 "projectId": "a1000000-0000-4000-8000-000000000002",6 "environmentId": "a1000000-0000-4000-8000-000000000003",7 "realmId": "a1000000-0000-4000-8000-000000000004",8 "displayName": "Example Robotics"9 }'1011HTTP 20112{13 "billingAccountId": "c2b1a0f9-8e7d-4c6b-9a5f-4e3d2c1b0a99",14 "kind": "organization",15 "role": "owner"16}
Transparent pricing
In part No separate price for what works today.Workspace plans
Included in every workspace plan. Limits (projects, provider connections, members, usage events) are listed on the pricing page.
Questions
Not yet. There is no self-serve portal. Identity-connection setup, domain verification and branded onboarding links are planned.
Any signed-in end user of your application whose realm access token carries a verified e-mail address. The creator becomes the owner.
Not for organisation invites: the token is returned once to the inviter and your application delivers it. Workspace invites for your own team are e-mailed when the platform scope is configured; otherwise the console shows the link once.
Only masked, such as a***@example.test. Invite tokens and their hashes are never returned to the console.
It creates a project, its first environment and a setup draft in one transaction and records the audit events for them. No provider call is made and no credential is accepted by that route.
Keep exploring
Create a workspace, register an application from the console and let your end users create their own organisations. The IT-administrator portal is planned and will be listed in the changelog when it is available.