How does a platform go from configuration to live traffic?
Define the scope structure, apply domains, themes and menus, grant roles, permissions and TeamSpaces, then connect providers through governed contracts and run their activation tests. Production access opens once the program is cleared for live processing. Each step happens in the Console, and the readiness indicators show what remains.
In detail
The path runs through a sequence of configuration steps, all done in the Console, with readiness indicators showing what remains.
The steps
- Define the scope structure: Meta Program Managers, Program Managers, Companies and Merchant Accounts, using the levels that fit your model.
- Apply domains, themes, menus and hosted pages, so every interface carries your brand.
- Grant roles, permissions and TeamSpaces to the people who will run the platform.
- Connect providers through governed contracts, with their credentials and configuration, and run their activation tests.
- Open production access once the program is cleared for live processing.
Until production opens, the program works in sandbox. Your team can configure, test and prepare merchants without touching live traffic. Activation tests validate each provider contract against the staged configuration before it carries real payments.
Because these steps are configuration rather than development, a branded platform can be ready quickly once the decision is made. Your engineers integrate the checkout and the events your systems need, while the platform, its connections and its certifications are already in place.
After launch, the same Console is where your merchants configure their own stack, from payment methods to routing rules, within the boundaries you set.