How do the scope levels map to my organization?
The structure runs from Meta Program Manager to Program Manager, then Companies, then Merchant Accounts. You use the levels that match your model and keep the structure as flat or as deep as your business calls for. Groups let you gather companies or merchant accounts for access control, reporting and configuration inheritance, and TeamSpaces sit on top for the way your teams actually work.
In detail
The structure runs from Meta Program Manager to Program Manager, then Companies, then Merchant Accounts. You use the levels that match your model and keep the structure as flat or as deep as your model calls for.
How operators typically map it
- A PSP or PayFac runs one Program Manager, with a Company per merchant and Merchant Accounts per brand, market or channel.
- An operator reselling payments uses a Meta Program Manager on top, with one Program Manager per reseller or client program.
- An ISV embedding payments keeps the structure flat, often with one Company and Merchant Account per customer.
- An ISO running its own gateway keeps it flat and wide, one entry per merchant, each with its own MID.
- A marketplace acting as master merchant groups seller accounts into the cohorts it manages.
Groups and TeamSpaces
Groups gather companies or merchant accounts for access control, reporting and configuration inheritance. A rule set on a group applies to every member, which keeps large portfolios manageable.
TeamSpaces sit on top for the way your teams actually work. A TeamSpace bundles a set of users with a set of Companies and Merchant Accounts, and its users see only what it includes. You can create one for risk, one for finance and one per regional operations group.