Organization-scoped providers
How Organization-scoped providers works in Paycux, what it is for, and the smallest setup that gets it running.
Overview
Organization-scoped providers 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.
Configure organization credentials
An organization is the tenant boundary in Paycux. Connections, directories, roles and audit log streams all hang off an organization, and a user reaches your application through a membership in one.
Create an organization per customer, not per environment. The same organization exists in staging and production with separate configuration.
Configure provider settings
Configure provider settings is handled by Organization-scoped providers 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.
Management widget
Widgets are prebuilt interface components that talk to the Paycux API with a scoped token. Drop one into your application and your customers manage their own users, roles and connections without you building those screens.
A widget token is minted on your server for one organization and one scope, and expires in minutes. Never mint one in the browser.
API
API is handled by Organization-scoped providers 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.
View organization-scoped providers in the dashboard
View organization-scoped providers in the dashboard controls what the credential is allowed to do. Grant the narrowest set that lets the integration work, and widen it deliberately.
Scopes are evaluated at the API boundary, so an over-broad token is a real risk even if your own code never uses the extra capability.