Merchant and agency channels connect merchant onboarding, agent hierarchies, commissions, QR acceptance and cash workflows through agreed financial integrations, so banks, wallet providers and distribution groups can grow acceptance without losing track of who may sell, collect or settle.
MoboGage labels this an Established foundation with extensions in its banking portfolio. It is the channel layer that usually sits next to mobile money, CreditSync and EVD retail sale, and the company profile frames the buyer value as service access, controlled credit operations, and clearer visibility of transactions and balances.
Company context, as reported by MoboGage: experience since 2007 (IWT Group heritage), more than one million retailers using its POS and airtime services, and business or project reach across 17 countries. MoboGage Private Limited was incorporated in February 2017; its only office is the Jaipur HQ, and other countries are served through partners.
Merchant and agency channel management is more than a sign-up form
A registration form gets you a list of names. Running the channel means onboarding merchants and agents under the institution’s own compliance rules, placing each one in the hierarchy (master agent, sub-agent or merchant outlet), granting permissions per product, channel and cash activity, attaching a commission scheme, enabling QR where the payment integration allows it, and reconciling cash back to wallet or bank positions. New payment schemes or device types beyond that foundation are scoped by agreement.
Onboarding states and who sees them
Onboarding captures the identity and commercial fields the institution requires, routes the application to an approver, places the party in the hierarchy and activates only the products it has authorised. The record keeps the approver’s ID and timestamp. Field supervisors see each application as submitted, in review, approved, rejected or suspended, so a sales rep can’t tell a shop it is live while compliance is still checking documents. Product activation waits until those checks are done; the KYC rules themselves belong to the regulated client.
Device and channel binding matter as much as the approval. An agent approved to sell through the app should not acquire cash-out rights that nobody granted, and QR acceptance should switch on only after the acquiring or wallet scheme confirms the merchant. Edges like these prevent the “the system let me” argument later.
Hierarchy changes are money events
The tree defines reporting lines, float relationships and how commission cascades. Moving an agent to a new parent looks like an admin edit, but it rewires money and support paths. We treat it as a dated event: open commissions stay with the old parent up to the effective date, new transactions accrue to the new one, and the move itself is approved and logged. Suspension stops new activity immediately while keeping history intact for settlement, and exit terms (data rights, documentation, training) belong in the commercial schedule.
Airtime networks already think in trees, which gives distribution and VAS groups a head start when they extend into wallet cash-in/out and merchant acceptance. That only works if the discipline from multi-tier reseller voucher distribution carries over, including who may sell to whom and at what limit.
Commission you can trace to a rule version
Commission can differ by product (airtime, bill pay, QR), by channel and by level in the tree. Each commission line we post stores the transaction reference, the rule ID and the rule version that produced it, so “what rate was live on Tuesday?” has a database answer. Master and sub-agent splits are calculated once from the same transaction event. Promotions get explicit start and end dates. Recalculating history is rare, needs authorisation and is audited, because each retroactive change opens a fresh dispute.
Agents on the same street compare rates. Where policy allows, print the applied rate on the receipt or statement line, and write the commission logic in words a field team can explain at the counter.
QR acceptance: what the code actually contains
Most national QR schemes follow the EMVCo merchant-presented QR specification. The payload is a string of tag-length-value fields: tag 00 for the payload format, tag 01 for static (11) or dynamic (12) codes, tags 26 to 51 for the merchant account information the scheme assigns, 52 for the merchant category code, 53 for the ISO 4217 currency, 54 for an amount on dynamic codes, 58 and 59 and 60 for country, merchant name and city, and tag 63 for a CRC checksum. A printed sticker at a till is usually static, so the customer types the amount; a code shown on a POS screen is usually dynamic and carries the amount and a reference.
That reference is what lets a QR payment reconcile against the outlet’s ledger. QR acceptance depends on the agreed financial integration and on acquiring or wallet scheme rules, so we present it as a scoped capability per market, not a universal claim.
Cash and the till
In many markets cash and QR will run side by side for years. Cash ties back to wallet balances through cash-in, cash-out and till reconciliation at the end of each shift, and QR failures need scheme-specific messages the shopkeeper can read. A 200 response from an API is no help to a shopkeeper whose drawer is short, so receipts and training are part of the design.
Who needs what from the channel
A bank or licensed wallet provider needs accountable merchants: onboarding evidence, clear hierarchy ownership and commission transparency, which help growth and help during regulatory review. Regulated responsibilities stay with the licensed institution. Merchants and agents need to see their activation status, product rights and commission statements. Finance and operations need commission accruals, cash variances and dormant outlets reported with unique transaction references and explicit states, in line with voucher reconciliation and the reversal design in the wallet cash-in/out deep-dive.
Fit with EVD System and mobile money
Retailers already selling from an electronic voucher management system are natural candidates for agency roles once wallet products expand. Keep one merchant master record across EVD and wallets so catalogue airtime, utilities and cash-in share the same outlet identity, and no orphan accounts appear. CreditSync may fund agent float, while the channel modules decide what that agent is allowed to do.
For the bigger picture, read the mobile money platform with merchant payment overview, the telecom product page EVMS for telecom, and about MoboGage. The buyer checklist is at how to choose an EVMS.
Questions to put to any channel vendor
Large recharge and distribution suites such as Comviva PreTUPS and Seamless ERS 360 market multi-level hierarchies, segment-based commission and dealer management. Those are reasonable baselines. In a demo, ask each vendor to move an agent between parents mid-month and show where the open commission lands, to show the rule version on a commission line, and to reconcile one dynamic-QR payment against the outlet ledger. Ask us the same.
A pilot sized to the field
Delivery follows the same five stages as our other work (Discover → Design → Pilot → Roll out → Operate and expand). For channels we pilot on one city or one hierarchy branch, with one product set (cash-in plus airtime, or QR plus bill pay) and a training cohort that stays the same throughout. Measure the quality of completed onboarding rather than the application count, how clear agents find their commission statements (ask them in feedback sessions), and how old cash variances get. Label: Established foundation with extensions. Proposed banking exception hubs and settlement-exception products are not included as available features and stay out of the pilot charter unless discovery adds them.
Useful links for evaluators: telecom EVD systems for context, electronic top-up for PINless sale at the same outlets, and the CreditSync post for the float funding behind the hierarchy.
For a first call, bring your compliance owner, your hierarchy model and the product set you want live first. Contact us through the voucher management system enquiry page, projects@mobogage.com, or +91-9928 366 889. Founder & CEO: Sohan Lal Soni, Jaipur, India.
Frequently asked questions
What are merchant and agency channels in this context?
They are the operating structures that onboard merchants and agents, organise hierarchies, calculate commissions, accept QR payments and run cash workflows through agreed financial integrations, an Established foundation with extensions in MoboGage’s banking portfolio.
How does onboarding usually work?
Onboarding collects identity and commercial data required by the institution, applies approval workflows, assigns hierarchy placement and activates channel permissions (POS, app, QR, cash). Exact KYC rules belong to the regulated client.
Why do agent hierarchies matter?
Commissions, float, limits and support ownership usually follow the tree. Without a clear hierarchy, settlement and dispute routing become informal and slow.
What is QR acceptance used for?
QR acceptance lets merchants take wallet or payment-scheme payments at the point of sale under agreed financial integrations. It sits beside cash workflows rather than replacing them overnight.
How do commissions stay trustworthy?
Commission rules should be versioned, attributable to transaction types, and visible to finance. Silent rule changes create channel conflict.
How do we pilot merchant and agency channels?
Bound one city or hierarchy branch, agree onboarding completion and commission clarity measures, then expand. Contact projects@mobogage.com or the enquiry page.
