As your fintech business grows, bring new merchants, agent channels and payment products into the same operational structure. MagicPay connects Payment OS, agent infrastructure and payment channels through a shared merchant and transaction model for payment institutions and platform operators. Institution teams follow the journey from application to product activation, while finance follows commissions through to amounts payable. Merchants and agents work with the records they are responsible for, making new connections part of an existing commercial relationship.
Grow your merchant portfolio with connected operations
When a merchant's application, approved product and payment transaction connect to the same institution record, sales and operations can follow the same customer relationship. MagicPay Payment OS brings this structure into institution and merchant portals. Virtual POS, physical POS and payment links remain distinct channels while retaining a shared merchant identity. Teams can introduce a new product within the existing portfolio.
- Link applications, products and terminals to the same merchant.
- Manage institution, agent and merchant relationships together.
- Review payment channels through a shared transaction history.
A connected flow from agent acquisition to merchant use
A merchant acquired by an agent is linked to the correct institution and parent account. Documents, product requests and activation steps follow the same application. Institution teams manage the whole network, agents see their assigned merchants, and merchants access their own products and transactions within their roles. Platform operators use this account structure to bring payment connections into their channel operations, keeping the relationship established by sales visible throughout the operational journey.
One financial trail from commissions to amounts payable
Connect sales, voids and refunds to merchant commissions, bank costs and settlement dates. Double-entry ledger records, reconciliation, reserves and amounts payable let finance work from the same transaction. Operations investigates the provider result while finance follows the basis for the net payout. Refunds stay linked to the original sale, allowing transaction changes to be reviewed alongside commercial records and financial checks.
For institutions, agent networks and platform operators
Designed for payment institutions managing merchant portfolios, institutions growing through agent networks, and fintech platforms operating multiple payment acceptance channels. Payment OS provides the institution's operational foundation, agent infrastructure connects the distribution network, and the gateway brings provider connections together. Product teams position new services while sales and finance work with the same merchant structure, rather than creating a separate operational silo for every product.
Launch your institution model in three steps
Choose an initial group of merchants and prepare institution, agent and channel relationships together. Extend acceptance testing beyond the payment result: follow application, refund, commission and payout entitlement through the same example to validate how teams will work each day.
- 1. Map institution, agent, merchant and provider accounts to your existing business model.
- 2. Connect products, channels, roles, commissions and settlement terms to the shared operational structure.
- 3. Test application, payment acceptance, refunds, reconciliation and payouts together before launch.
MagicPay provides technical infrastructure and operational software. Payment services, merchant onboarding and funds movements are handled by the relevant authorized institutions within their contracts and service scope.