RBAC
Role-Based Access Control (RBAC)
How Role-Based Access Control (RBAC) works in Paycux, what it is for, and the smallest setup that gets it running.
Introduction
Role-Based Access Control (RBAC) 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.
Key features
Key features is handled by Role-Based Access Control (RBAC) 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 resources
Additional resources is handled by Role-Based Access Control (RBAC) 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.