Distribution
This section outlines the product usage hierarchy, options for distribution, and sales and marketing support for .
Product Usage in the Portfolio Hierarchy
acquirers are onboarded with a three-level hierarchy.
Portfolio Hierarchy Descriptions
- Portfolio MID: this is the parent portfolio MID under which you occupy and board your resold merchant accounts. This portfolio MID is registered with your business information.
- Merchant Account MID: this is a specific merchant account and represents a resold merchant under your portfolio. This is the level at which operates and where the token vault is configured for token storage. This merchant account MID is registered with the business information of the end merchant that is resold by you.
- Transacting MID: this is a child MID that is used for processing transactions. A merchant account MID can have multiple transacting MIDs that are boarded beneath it. These represent different processing entities under a merchant account. This transacting MID is registered with the business information for the specific entity that is under the merchant account MID.
Options for Distribution
supports two implementation models for distribution. For definitions of Standalone Reseller and with Payments Reseller, see Solution Overview.
Sales and Marketing Support
- Visa and Pay.com TMS Case Study on YouTube
- Token Management in the API Explorer:
POST /tms/v2/tokenized-cards
Distribution and Integration
Use to provide and distribute to your solution portfolio. The rest of this document focuses on your role in enabling and providing support resources.
Resources for Merchants
This guide contains links and examples from the Token Management Service Developer Guide and API requests from the Token Management Service Developer API Reference. Refer to these resources in full to explore all the end-to-end integration flows:
- Token Management Service Developer Guide
- Token Management in the API Explorer:
POST /tms/v2/tokenized-cards
Thanks for your feedback!
Last published: November 18, 2026