A shared service catalogue is MoboGage’s Established capability for selling airtime, data, gift cards and utility services through scoped provider integrations with clear transaction tracking. Distributors and retailers get one digital offer instead of a drawer full of separate apps.
Retail and VAS networks rarely get into trouble because one recharge API is missing. The trouble starts when each new service arrives as another portal, another float and another reconciliation file, and by the third provider nobody at the counter is sure which balance pays for what. A shared catalogue keeps the front end consistent while each provider connection stays tightly scoped behind it.
The catalogue sits in MoboGage’s Established retail portfolio next to MoboEVD and CreditSync. Company-reported figures (reach across 17 countries through partners, and more than one million retailers using POS and airtime services) describe MoboGage’s wider operating context, not product SLAs. MoboGage’s only office is the Jaipur HQ.
What goes into a shared service catalogue entry
The catalogue is the list of things a channel user can sell, and each line is a record rather than a brochure tile. In our data model an entry carries: a SKU and provider ID; the product type (PIN voucher, PINless top-up, bundle, gift card, bill payment, prepaid utility token); either a fixed face value or an open range with minimum, maximum and step; currency; the channels allowed to sell it (POS, app, USSD, API); the commission and fee rule IDs; which float or inventory pool funds it; and effective-from and effective-to dates. Only privileged roles can publish a change, so a retired denomination stops selling at the date it was retired.
Each entry also points to a state model: what success, known failure, timeout and reversal look like for that provider, and who owns each one.
Airtime, gift cards and bills behave differently
Airtime and data are still the core in most markets. Depending on the operator interface, a product may be a PIN voucher sale, PINless electronic top-up, or a plan or bundle purchase, sold over POS, apps, USSD and SMS. The electronic top-up system post explains the PINless recharge transaction itself.
Gift cards come in two kinds. Some are imported serial stock with their own expiry; others are issued at the moment of sale through a provider API that returns the code. The receipt and the refund rule differ, so the catalogue shows which is which, and a just-in-time gift code is never treated like a pre-activated airtime card.
Utilities have the most steps. Bill payment is usually two calls: an enquiry with the customer account number that returns the name and amount due, then a payment that references the enquiry. Prepaid electricity in many markets returns a 20-digit STS token (IEC 62055-41), which has to be printed or sent by SMS exactly, because a mistyped token can’t be used on the meter. When a payment times out, the transaction is held, the provider is queried, and float is released or the payment confirmed. Decide before launch who retries, who refunds and who calls the provider.
Scoped provider integrations, in practice
The company profile says “scoped provider integrations” deliberately. Discovery covers credentials, test and production environments, rate limits, idempotency keys, duplicate detection, retry windows and ownership of unresolved exceptions. Interfaces are versioned. Two providers never share a state machine by assumption; each gets its own mapping from provider response codes to catalogue states.
The trust controls in the MoboGage profile apply: unique references, explicit states, duplicate prevention, controlled reversals and reconciliation. Privileged access, encryption, retention and recovery targets are set per engagement.
Who gets what out of it
The operator or aggregator can widen the merchant offer without adding channel software; new providers plug in behind the same retail screens, which is how many VAS partners grow past a single airtime brand. Voucher-backed products still follow the lifecycle described in our electronic voucher management system positioning.
The distributor can fund several catalogue products from one float where the commercial rules allow it, with hierarchy visibility as described in multi-tier reseller voucher distribution. The retailer gets one POS or app for airtime, data, gift cards and some utilities, with one receipt pattern, so staff can explain a timeout without ringing the helpdesk.
Finance and operations get a unique reference on every sale, the provider reference where one comes back, and an explicit state. Matching those against each provider’s settlement file is the daily work of retail control, and the reason buyers read voucher reconciliation even when some catalogue lines are PINless.
How the catalogue sits beside MoboEVD and wallets
Voucher-backed lines use MoboEVD inventory and activation. Wallet-funded lines use balances, 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. If you’re comparing platforms, start with what is electronic voucher distribution and the EVMS buyer checklist.
What to ask vendors in discovery
Several platforms advertise third-party products on the POS: Seamless ERS 360 describes the POS as a one-stop shop for third-party products, and Emida lists bill payment, international top-up and stored value cards. Breadth of the menu is easy to show. Ask instead for a product sheet per provider line (type, channels, funding pool, commission rule, timeout owner) and for the state diagram behind it. Then ask to see one utility payment forced into a timeout and resolved, and a denomination retired mid-day. We will run the same tests on our platform.
Training should follow the catalogue: one receipt pattern, one helpdesk script for “provider is down”, one escalation owner per provider.
If a GCC or multi-country programme reuses a catalogue pattern, expect providers to behave differently country to country even when the screens look the same. Country reach in MoboGage materials means business or project presence through partners, not identical interfaces everywhere.
Starting with one provider
The company profile suggests a first pilot of one service provider or one 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.
Bring the provider list you want first, the channels that have to sell them, and the person who’ll own reconciliation. Contact MoboGage 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 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