Partner Portfolio Overview
This guide is written for acquirer and reseller partners who need to set up and administer their partner portfolios in the system. These instructions are intended for newly enrolled partners who are properly contracted and enabled for the .
Initial Preparation
Review these introductory topics to prepare yourself and your organization before you log in to your partner portfolio account:
- Environment types: Understand the production and test environment types and the purpose of each.
- Portfolio administrator: Assign a portfolio administrator who can begin setting up your portfolio account.
- Assemble an operations team: Assign an operations team to support your portfolio as life-time administrators.
- Portfolio hierarchy: Understand the three-level hierarchy and how to organize your merchants within the hierarchy.
- Set-up tasks: Understand your chosen solutions and products and how to begin their set up.
Your Environments
As a partner, your organization is provided with a portfolio account in the production environment for merchant boarding, administration, support, and other operational capabilities. The products enabled for your portfolio are based on those that were introduced during the scoping and planning process and confirmed through your agreements.
Depending on your organizational needs, you might be issued a test portfolio account in the test environment. This environment is also known as the customer acceptance system (CAS) environment. You can use your test account to test you and your merchants' integration, training, and test needs. Both environments are provided to you with the same product and service options. New and additional products and services can be added to the test portfolio account separately from the production portfolio account for evaluation and new commercialization purposes.
If you are a reseller, consider how both the production and test portfolio accounts can be used based on your needs and your merchants' needs. Some resellers might have multiple test and production portfolio accounts depending on how their organization operates.
Assign a Portfolio Administrator
Assign a portfolio administrator who can take ownership of the partner portfolio. It is the portfolio administrator who should be the first member of your organization to log in to the .
The portfolio administrator assumes these responsibilities:
- Serving as the primary contact with account representatives.
- Managing portfolio deployment activities.
- Completing portfolio administrator training.
- Administering day-to-day operations after deployment.
The portfolio administrator is responsible for the complete solution and experience for the shared merchants. For the merchant experience within the solution, it is the portfolio administrator who helps define the solution architecture, operational management of the solution, as well as the implementation and support program.
First Time Logging In
The portfolio administrator should log in first to take these actions:
- Create roles and users for your operations team. See Create Roles and Users Quick Start.
- Ensure that the requested solutions are enabled for the portfolio. See Board Merchants Quick Start.
- Enable merchant templates and merchant accounts. See Board Merchants Quick Start.
If the person who receives the initial login credentials is not the portfolio administrator, then a user account must be created for the portfolio administrator with their role set to administrator. The administrator role is a default role that has all privileges and access to all features within a portfolio.
Assemble Your Operations Team
Setting up and maintaining a portfolio requires the coordinated efforts of business and technical staff. Your team might include network administrators, product owners, project managers, implementation managers, solution managers, and product developers. Members of your deployment team have the collective responsibility for these tasks:
- Portfolio Hierarchy
- Create Roles and Users Quick Start
- Board Merchants Quick Start
- Transaction Reports Quick Start
- Set Up Billing
Assigning Roles and Users
Each staff member should have their own user account with specific roles and permissions to access and perform tasks within the . The Portfolio Administrator can create their user accounts and assign their roles in the .
- Roles: Roles enable you to give a user access to specific services in the , such as Reports and Transaction Search. The offers default roles, but you can also create new roles that support your business model. Roles must also be given a set of permissions for each service. Permissions determine a role's duties and the level of access to a service.
- Users: User accounts are for accessing and performing tasks in the . Each member in your organization should have their own unique user account. Users must be assigned to a merchant ID (MID) or transacting MID, which determines the data that the user can access. A user must also be assigned a role that determines which features and security the user can access.
For more information about how to create roles and users, see Create Roles and Users Quick Start.
Portfolio Hierarchy
The consists of a three-level hierarchy for organization management:
- Portfolio level
- Merchant level
- Transactional level
As a partner, you log in to the at the portfolio level. You should organize your merchants within the merchant level and transactional level. Each merchant and transactional account within a partner portfolio is given its own ID type to perform organizational tasks specific to its level.
Organization ID Types
- Portfolio ID: A portfolio ID is provided to you, the partner. Portfolio IDs enable partners to onboard merchants into a test or production environment.
- Merchant ID: A merchant ID (MID) represents the merchant on an account level and can store multiple transacting MIDs. It is directly associated with the merchant agreement and is created by the partner at the portfolio level. MIDs are configured to specific services, such as the Token Vault configuration, and have their own user administration, reporting, and aggregated views.
- Transacting MID: A transacting MID is the representative MID used for processing transactions. Each partner's merchant can have multiple transacting MIDs. The transacting MID is typically the account that sends API requests with controlled authentication. Transacting MIDs are created by MIDs.
This figure shows how portfolio accounts, merchant accounts, and transactional accounts can be organized within the three-level hierarchy.
Merchant Experience
Before you begin enabling merchants in your portfolio, consider how your merchants should be organized within the merchant-level and transaction-level hierarchy. Consider these aspects of the merchant experience:
- Which users are processing transactions.
- Which users are managing merchant onboarding and operations.
- Which users manage ongoing updates to products.
You can test creating and managing merchant accounts and transactional accounts in the CAS environment before you enable merchants in your production environment.
Thanks for your feedback!
Last published: November 18, 2026