featured

Case Study: Service Distribution — Voucher, Wallet and Utility Integration

Service distribution engagement (West Africa market context): a company-reported MoboGage engagement covering voucher, wallet, utility and external-provider integration, written up for aggregators and operators who are adding more services to their retail network.

This is a company-reported, anonymised summary. We don’t name the client or operator, and we don’t publish performance metrics. Project scope, references and supporting records can be shared through an agreed due-diligence process.

The problem with adding one more utility or service

Many distribution networks follow a similar path. Airtime comes first. Then someone adds utilities, then wallet moves, then a third-party digital product, and each one arrives with its own portal, its own float and its own way of failing. After a while the counter staff are juggling apps and finance is matching four settlement files that don’t agree.

The brief here was to bring voucher, wallet, utility and external-provider workflows together so the channel could sell and support one offer, with every transaction traceable.

Service distribution in Nigeria: the context

The market was Nigeria (company-reported selected experience), and the workflow class was service distribution. The Established capabilities in play were MoboEVD distribution, shared service catalogues, wallets and CreditSync-related channel finance. For context, MoboGage reports (company-reported) business or project presence across 17 countries through partners; its only office is the Jaipur HQ.

If you want the product detail behind this, read the shared service catalogue post, voucher generation and inventory activation, the mobile money platform page, and the wallet cash-in/out deep-dive.

What we built

The work covered voucher distribution controls for prepaid sale, wallet transaction paths where they were in scope, utility integration patterns, and connections to external providers with explicit tracking on each one. We aren’t publishing implementation detail, provider names or volumes.

The controls that made it hold together

When several providers sit behind one counter, the routine controls decide whether it works: credentials scoped per provider, idempotent requests so a retry doesn’t charge twice, final states that stay final, and an owner for every exception. Utility lines add their own steps, usually a bill enquiry that returns the amount due before the payment call, and for prepaid electricity a token that must reach the customer exactly as issued. Commission and hierarchy rules also need to stay visible across product families, the same thinking as in multi-tier reseller design. And the voucher reconciliation habits apply just as much when some lines are PINless or bill-pay. A utility payment that timed out needs the same day-close treatment as a voucher that didn’t redeem.

If you’re planning something similar

A first phase works best with one provider or one distributor network. Before you add anything to the catalogue, agree how you’ll measure availability and unmatched transactions, because that argument is much harder to have after go-live. Be honest about readiness labels as well: the Established distribution and catalogue capabilities are available to scope, while Proposed items like settlement hubs are roadmap only.

Our delivery path runs Discover → Design → Pilot → Roll out → Operate and expand. For the wider platform, see the homepage on our electronic voucher management system.

Talk to MoboGage

Contact / voucher management enquiry · projects@mobogage.com · +91-9928 366 889 · Hub: Case Studies.

Frequently asked questions

What was the focus of this service distribution engagement?

Company-reported experience covered voucher, wallet, utility and external-provider integration workflows for service distribution.

Why anonymise the client?

Because commercial confidentiality is the default. Market context (Nigeria) situates the workflow class without naming institutions.

Which product areas does this map to?

Electronic voucher distribution, shared service catalogue patterns, wallet connectivity and scoped provider integrations.

What buyer lesson stands out?

Multi-provider retail needs one channel experience and explicit transaction states per provider, not a separate informal process for each new service.

Are performance results published here?

No. Numbers and outcomes are not invented or disclosed in this summary. Evidence is available through due diligence.

How do we start a similar pilot?

Bound one provider or service family on one distributor network; agree unmatched-value and availability measures. Contact projects@mobogage.com.

shared-service-catalogue-airtime-data-utilities

Shared Service Catalogue for Airtime, Data, Gift Cards and Utilities

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.