A shared service catalogue is MoboGage’s Established capability for offering airtime, data, gift cards and utility services through scoped provider integrations and clear transaction tracking—so distributors and retailers sell one coherent digital offer instead of a patchwork of disconnected apps.
Retail and VAS networks rarely fail because a single recharge API is missing. They fail when every new service arrives as another portal, another float, and another reconciliation story. A shared catalogue keeps the commercial front coherent while each provider connection stays explicitly scoped.
This capability sits in MoboGage’s retail Established portfolio alongside MoboEVD and CreditSync. Figures such as company-reported reach across 17 countries and more than one million retailers using POS and airtime services describe MoboGage’s broader operating context; they are not product SLAs. MoboGage’s only office is Jaipur HQ.
What a shared service catalogue is
In operating language, the catalogue is the sellable product list presented to channel users—denominations, bill-pay services, gift offers—backed by provider integrations that return definitive transaction states. It is not a marketing brochure. Each catalogue entry should declare:
- Provider and product identity
- Price or denomination rules (or bill enquiry behaviour)
- Channel eligibility (POS, app, USSD, API)
- Commission and fee treatment
- Success, failure, timeout and reversal behaviour
When those fields are vague, retailers invent workarounds and finance inherits the exceptions.
Stakeholder value
Operator or service aggregator
You extend the merchant offer without multiplying channel software. New providers attach behind the same retail experience, which is how many VAS partners grow beyond a single airtime brand. For voucher-backed products, catalogue sale still respects the lifecycle described in the site’s electronic voucher management system positioning.
Distributor
One float or balance model can fund multiple catalogue products when commercial rules allow. That reduces the “which wallet pays for which service” confusion that slows field teams. Hierarchy visibility remains essential—see multi-tier reseller voucher distribution.
Retailer
A single POS or app surface for airtime, data, gift cards and selected utilities shortens training and speeds the counter. Receipts and failure messages must be consistent enough that staff can explain outcomes to customers without calling a helpdesk for every timeout.
Finance and operations
Clear transaction tracking means each sale carries a unique reference, a provider reference where returned, and an explicit state. Matching those to provider settlement files is the daily work of retail control—and the reason buyers also study voucher reconciliation practices even when some catalogue lines are PINless.
Service families typically included
Airtime and data
Prepaid top-up remains the core catalogue family in many markets. Products may be PIN voucher sale, PINless electronic top-up, or plan/bundle purchase depending on the operator interface. Channel mix often spans POS, apps, USSD and SMS. For PINless patterns, the companion page on an electronic top-up system explains the recharge transaction itself.
Gift cards
Gift and brand vouchers introduce different inventory and expiry rules. Some are imported serial stock; others are issued at sale via provider APIs. Catalogue entries must reflect those differences so retailers do not treat a just-in-time gift PIN like a pre-activated airtime card.
Utility services
Bill enquiry, bill pay and prepaid utility tokens depend on accurate customer identifiers, provider fee rules and printable or SMS receipts. Timeouts and partial confirmations need defined ownership: who retries, who refunds float, who contacts the provider.
Provider integration discipline
Company profile language is deliberate: “scoped provider integrations.” That means discovery covers credentials, environments, rate limits, idempotency keys, duplicate detection and who owns unresolved exceptions. Document versioned interfaces. Agree retry windows. Do not assume every provider returns the same state machine.
Trust controls from the MoboGage profile apply here: unique references, explicit states, duplicate prevention, controlled reversals and reconciliation. Privileged access, encryption, retention and recovery targets are engagement-specific.
How the catalogue sits beside MoboEVD and wallets
Voucher-backed catalogue lines lean on MoboEVD inventory and activation. Wallet-funded lines lean on balance, cash-in/out and bank connectivity. Merchant payments and agency onboarding extend the same retail network when QR acceptance and cash workflows are in scope. None of these modules erase the need for a clear product list—the catalogue is the commercial map agents actually sell from.
Buyers comparing platforms can start with what is electronic voucher distribution and the EVMS buyer checklist, then ask how multi-provider offers will appear in one channel experience.
Delivery and readiness
A useful first pilot, per the company profile, is one service provider or distributor network, with agreed measures for inventory availability and unmatched value. Delivery follows Discover → Design → Pilot → Roll out → Operate and expand. The shared service catalogue is labelled Established. Proposed retail items such as settlement exception hubs or retail intelligence are roadmap topics only and are not presented as available products here.
Enquire about a catalogue pilot
Bring the provider list you want first, the channels that must sell them, and the reconciliation owner. Contact MoboGage via the voucher management system enquiry page, projects@mobogage.com, or +91-9928 366 889. Founder & CEO: Sohan Lal Soni · Jaipur, India.
Operating detail buyers should demand in discovery
When you open a catalogue programme, ask for a product sheet per provider line—not a slide. That sheet should state whether the line is voucher-backed, PINless, gift issuance, or bill enquiry/pay; which channels may sell it; what float or inventory it consumes; how commissions calculate; and who owns timeouts. If the answer is “we will figure it out at go-live,” you are funding future dispute volume.
Also demand a state diagram. Retail staff need language for success, known failure, and indeterminate outcomes. Finance needs the same states mapped to settlement expectations. Channel managers need to know whether a failed utility pay reversed float automatically or requires a case.
Training materials should mirror the catalogue: one receipt pattern, one helpdesk script for provider-down scenarios, and one escalation owner per provider. That sounds mundane. It is how multi-service networks stay operable when the third utility provider joins.
Catalogue change control
Products appear and disappear. Denominations change. Fees change. Without change control, retailers sell yesterday’s offer. Catalogue entries should carry effective dates, and privileged roles alone should publish changes. Pair that discipline with the inventory activation habits described for MoboEVD so voucher-backed lines do not activate under retired marketing rules.
Where GCC or multi-country programmes reuse a catalogue pattern, remember that provider behaviour is country-specific even when the UI looks familiar. Country reach in MoboGage materials is business/project presence, not a promise of identical interfaces everywhere.
Frequently asked questions
What is a shared service catalogue in an EVD or retail platform?
A shared service catalogue is a controlled list of sellable digital services—typically airtime, data, gift cards and utility payments—offered through scoped provider integrations with clear transaction tracking from the retail or agent channel to the provider.
Which service types can sit in one catalogue?
Established catalogue patterns include prepaid airtime and data, gift cards, and utility services. Each product maps to a provider interface, denomination or bill rules, commission scheme and settlement expectation.
How do provider integrations stay scoped?
Integrations are agreed per provider: credentials, transaction states, retries, timeouts, reversal rules and exception ownership. The catalogue exposes only products that have a live, tested interface and a commercial owner.
How does the catalogue help distributors and retailers?
Agents see one coherent offer instead of separate apps per provider. Inventory or float rules, commissions and receipts stay consistent, which reduces training load and mismatched settlement narratives.
Does a shared catalogue replace voucher inventory controls?
No. Catalogue products that are voucher-backed still rely on voucher lifecycle rules. Catalogue products that are PINless or bill-pay rely on float, eligibility and provider confirmation. Both can share retail channels under one operating view.
How should a catalogue pilot be bounded?
Pick one provider or one service family, agree availability and unmatched-transaction measures, then expand. Contact projects@mobogage.com or the voucher management system enquiry page to shape the pilot.
Add a Comment