As your representative network grows, see centrally which portfolio each new merchant belongs to and which product it is waiting for. MagicPay Merchant Representative Infrastructure establishes the PF → Merchant relationship between the payment institution, representative and merchant within one account hierarchy. Submerchant onboarding, document tracking, product requests and collection history follow the same relationship. Head office follows the entire network; each representative follows the portfolio under its responsibility.
Know who owns each portfolio and where it came from
Make a merchant record more than a contact entry. See the referring representative, parent institution, subaccount relationship and activated products together. Sales follows a new application while central operations tracks the merchant's next step in the same record. The representative network is managed through current portfolio relationships rather than disconnected application lists.
- Institution, representative and merchant hierarchy
- Merchant portfolios assigned to representatives
- Shared application and product-status tracking
From merchant onboarding to product requests
A merchant acquired by a representative is linked to the relevant institution and representative record. Application documents and product requests progress through that merchant, with submerchants joining the account hierarchy. The central team runs the institution's acceptance process and links approved products and terminals to the merchant. Representatives follow application progress in their own portfolios within their access scope.
- Merchant and submerchant applications
- Documents and product requests linked to the application
- Product and terminal mapping following central approval
Head office, representatives and finance work together
Institution users see the whole network, representatives see their merchants and merchants see their own transactions. Payments, cancellations and refunds remain linked to merchant and provider references. Merchant-specific commission and settlement-date information lets finance examine the relationship between collections and merchant settlement amounts. When investigating a transaction question, the central team can reach both the portfolio owner and the original sale through the same history.
- Views scoped by role and account
- Merchant-level commission and settlement-date tracking
- Shared transaction references from collection to merchant settlement
For institutions growing through representative networks
Designed for payment institutions that onboard merchants through representatives or sales partners. It supports teams keeping regional portfolios, submerchant relationships and central product management together. The PF → Merchant model preserves the institution's existing merchant and transaction framework as new representatives join.
Connect your network in three steps
Start with a sample representative portfolio. Validate the head-office, representative and merchant steps together, from acceptance to first collection, then apply the same account model across your network.
- 1. Define institution, representative, merchant and submerchant relationships and user roles.
- 2. Connect applications, documents and product requests to the central acceptance process.
- 3. Test product activation, portfolio views and collection tracking linked to commissions.
MagicPay provides technical infrastructure and operations software. Payment services and fund movements are carried out by the relevant authorized institution within its own contractual and service scope.