Does each brand or sub-program keep its data separate?
Yes. Each brand, legal entity or sub-program keeps its own boundary on the shared infrastructure. Its data, its merchants and its branding belong to it alone, and activity in one stays sealed from the others. Access follows the same structure, so each team, ISO or agent sees only the brands it runs while you keep the full picture.
In detail
Yes. Each brand, legal entity or sub-program keeps its own boundary on the shared infrastructure. Its data, its merchants and its branding belong to it alone, and activity in one stays sealed from the others.
How the boundary holds
The boundary comes from the structure itself. Programs, companies and merchant accounts each sit in their own scope, and every view, export, API call and connector query is filtered by that scope. Access follows the same structure, so each team, ISO or agent sees only the brands it runs.
TeamSpaces add another layer for internal teams. A TeamSpace bundles users with a set of companies and merchant accounts, and its users see only what it includes. You can draw the data boundary for a regional team or a risk team precisely.
What you keep
You keep the full picture. From the level above, you see every brand and program, compare their activity and apply common policies where you choose. Reporting can consolidate across brands for your own view, while each brand reads only its own data.
Why it matters
Brands and sub-programs often belong to different legal entities, with different obligations and partners. Separation lets them share one infrastructure, with the same providers and the same platform, without sharing information they should not.