Who decides what a program below me can configure on its own?
Governance controls sit at the level above. A set of toggles decides whether a program can manage payment partners, create webhook templates, customize hosted payment pages, configure branding and interface options, and customize the menu for the companies and merchant accounts below it. When a toggle stays closed, the corresponding section becomes read-only or hidden, and the configuration remains centrally managed.
In detail
You do. Governance controls sit at the level above each program, and a set of toggles decides what that program can manage on its own.
What the toggles cover
- Managing payment partners.
- Creating webhook templates.
- Customizing hosted payment pages.
- Configuring branding and interface options.
- Customizing the menu for the companies and merchant accounts below it.
When a toggle stays closed, the corresponding section becomes read-only or hidden for that program, and the configuration remains centrally managed. When it is open, the program configures that area itself, within its own scope.
Production access follows the same logic. It is a dedicated toggle held above the program, so the decision to process live payments stays with the level that carries the responsibility.
Delegation that stays visible
Delegation is explicit, and every change is auditable. The program list shows the governance permissions in effect for each program, alongside its readiness indicators, so you can review your whole portfolio from one table.
This lets you treat programs differently. A long-standing reseller can manage its own branding and partners, while a new client program starts with central control and gains rights as it matures. Your standards hold where they need to, and autonomy grows where it makes sense.