An electronic voucher management system is the software that keeps prepaid value under control, from generation or intake, through the dealer hierarchy and every sales channel, to redemption in charging and a day-close finance will sign off on. For MNOs, MVNOs and VAS partners, getting the shortlist wrong costs real money. It shows up later as disputed float, PINs exposed without anyone noticing, and reprints you thought you’d left behind with scratch cards.
EVD System by MoboGage is built to be that control plane for telecom and gift-card distribution. But this page isn’t a brochure. It’s the checklist we’d want a buyer to bring to our own discovery call, so your RFP tests what actually matters once you’re live.
The short version: buy for a lifecycle that runs all the way through reconciliation, not for a slick “generate PIN” demo. Settle your operating model (opco-owned, VAS-operated or hybrid) before anyone argues about screens. Insist on a concrete charging/BSS path, POS and offline behaviour that has been proven somewhere, and day-close packs an auditor would accept. Treat security as PIN custody plus velocity and replay controls, not a logo on a slide. And treat vendor rankings with caution; a reference who can walk you through an ordinary week of exceptions tells you more.
Opco, VAS partner or hybrid: decide this first
An opco, MNO or MVNO should own stock and fraud policy, with the EVMS plugging cleanly into charging and a hierarchy that mirrors national distribution. A VAS or distribution partner needs something more productised for running several opcos: white-label portals and POS, commissions, partner float and APIs, without rebuilding the lifecycle for each brand. A hybrid arrangement only works when it’s crystal clear who holds the keys, who runs L1 support, who owns blacklist and expiry, and how disputes escalate.
If your team can’t answer those ownership questions yet, pause the software comparison and settle the operating model. A common sticking point is who owns a compromised batch: who can blacklist it, who tells the dealers, and who signs off the write-off.
What an electronic voucher management system must cover, gate by gate
Take each product on your shortlist and walk it through six gates. Generation or intake comes first: controlled serialisation, denomination rules, batch metadata and expiry, with secrets never stored as plain text. Inventory next, with statuses you can believe (available, allocated, sold, redeemed, expired, cancelled). Then allocation across multi-level dealers, with float, credit limits and transfer rules your ops team will actually follow. Sale, over portal, Android/Linux POS, app, USSD/SMS and API, all under one fraud policy. Redemption, where credit reaches charging with duplicate and replay controls. And finally reconciliation: daily packs covering volumes, wallets and exceptions, with a named owner for every mismatch.
A gap at any gate becomes leakage later. The EVMS architecture guide maps each gate to a component you can ask vendors about. Hybrid physical and electronic programmes are fine, as long as print logistics are an option rather than the default cost of selling prepaid.
Two gates deserve a concrete test. For redemption on Ericsson-style charging, ask the vendor to show the UCIP refill request and response for one sale, including the originTransactionID they send and how a non-zero responseCode appears on the retailer’s screen. For offline POS, ask how the terminal sells without a connection: typically a small encrypted pool of pre-allocated PINs or an offline value cap per terminal, a sync that uploads sales with their local timestamps, and a rule for what happens when the server has already cancelled a voucher the terminal sold offline.
A 1 to 5 scoring grid for vendor demos
| Area | Questions to ask in discovery | Weak answer sounds like… |
|---|---|---|
| Security & trust | How are PINs encrypted at rest and in transit? Who can reveal a PIN? Velocity, duplicate, and replay controls? Audit logs for operator review? | “We use HTTPS” (and nothing else). |
| Hierarchy & float | Multi-level trees, credit limits, commissions, operator stock vs partner float separation? | Flat “admin / agent” only; float explained with a spreadsheet. |
| POS & field ops | Which Android/Linux families are in production (e.g. Sunmi-class)? Online/offline sale and sync rules? Remote disablement? | “Any Android phone” with no offline story. |
| APIs & charging | Documented sale/inquiry/reversal (where allowed)? Concrete charging/BSS integration path? | Slide that only says “API ready.” |
| Reporting & reconcile | Near real-time by region/dealer/product/channel? Day-close packs finance will use? Exception queues with owners? | Marketing dashboards; no mismatch workflow. |
| Catalog | Airtime, data, gift, OTT without fracturing inventory? PIN sale and PINless eTopup on the same wallet where required? | One denomination demo; gift cards “phase 2 forever.” |
| Commercial & hosting | Licensing, hosting (on-prem/private cloud), transaction economics, upgrade and support SLAs? | Opaque pricing until late; support undefined. |
Weight the rows before the demos, not after. A vendor who scores high on UI polish but low on reconciliation and charging is offering a sales screen rather than an EVMS.
When to walk away
Some answers should end the conversation, or at least put heavy conditions on it. The demo stops at “PIN appears on screen” and there’s no day-close pack. The vendor can’t tell the EVMS lifecycle apart from EVD channels, or worse, describes them in ways that contradict each other. You’re shown vanity metrics (“best in world,” ratings you can’t verify, inflated client counts) instead of reconcile references. Offline works “verbally,” with nothing written about sync conflicts or disabling a terminal. Reversals and duplicate controls are pushed to “custom, later.” Or your dealers would end up running a shadow system for float, because they already don’t trust the screen.
Six questions to bring to the kickoff
Who owns voucher secrets and the HSM/key ceremony, the opco or the partner? What’s the pilot slice (region, dealer tier, POS count), and what are its exit criteria? Where do sales and charging disagree today, and which report will prove they agree after go-live? What’s the end-to-end procedure for blacklisting a compromised batch? How are terminals versioned, configured and disabled when they’re lost or compromised? And what’s the training and L1 model for master dealers in the first 90 days?
A vendor with live rollouts should answer most of these from memory and show the matching screen or document for the rest.
Reading competitor brochures
The established suppliers publish feature lists that overlap heavily. Comviva describes PreTUPS VMS as covering the voucher lifecycle from product management to consumption, with expiry-date modification and status changes, and cites uptime figures for the platform. Seamless positions ERS 360 around dealer management, campaigns and third-party products on the POS. Telepin and Emida describe eTopUp, eVoucher, PINless and QR top-up. These are real capabilities. What brochures rarely show is the exception path: the unmatched report, the timeout handling, the dual-control reprint. Score that part from the demo, for every vendor including us.
EVMS vs EVD vs eTopup (so RFPs stay coherent)
| Term | Meaning in practice |
|---|---|
| EVMS / VMS | Lifecycle & inventory core: generate/receive, serialise, allocate, expire, cancel, reconcile. |
| EVD | Distribution/channel layer: how digital vouchers reach resellers and customers via POS, apps, USSD, APIs. |
| eTopup | Often PINless recharge: credit via dealer float or API without handing over a scratch PIN. |
When buyers say “we need EVD software,” they usually mean this whole prepaid stack. Deep dive: What is electronic voucher distribution (EVD)?.
How MoboGage EVD System maps to this checklist
We position EVD System as the electronic voucher management system control plane for operators and VAS partners: hierarchy and float you can audit, Android/Linux POS (Sunmi-class included) next to portals and APIs, and a BSS-adjacent path to charging scoped per contract. The exact device fleets, offline behaviour and charging adapters belong in discovery. A one-size public matrix would mislead you.
Product overview: Electronic voucher management system for telecom. Contact: voucher-management-system-mobogage · projects@mobogage.com · +91-9928 366 889.
FAQ
What is an electronic voucher management system?
Software that controls prepaid voucher value end to end: generate or intake stock, inventory and hierarchy allocation, multi-channel sale, redemption into charging, and reconciliation, typically for telecom airtime, data, gift cards, and related digital products.
How do I choose an electronic voucher management system for telecom?
Score vendors on security and PIN custody, hierarchy and float, POS and offline realism, charging or BSS path, day-close reconciliation, catalog breadth, and commercial clarity. Prefer references that describe exception handling.
Is EVMS the same as EVD software?
Not exactly. EVMS or VMS is the lifecycle core; EVD is the channel and distribution layer. Strong platforms connect both under one inventory and fraud policy.
What should VAS partners prioritise?
Prioritise multi-opco operating efficiency: white-label portals and POS, commissions, partner float separation, APIs, and reconciliation packs for each opco without rebuilding the core.
Can an EVMS run hybrid physical and electronic stock?
Yes. Require one control framework for batches, status, expiry, and audit so print logistics are optional.
Does offline POS matter?
In many GCC, MEA, and emerging retail networks, yes. Ask how offline sales sync, how conflicts resolve, and how lost terminals are disabled.
What is the fastest way to fail an EVMS project?
Skipping operating-model ownership, launching without a charging truth, and ignoring day-close exceptions until finance escalates.
What to do this week
Run the scoring grid against your shortlist. If you’d like a discovery-style walkthrough of how EVD System handles hierarchy, POS and reconcile for your operating model, talk to MoboGage. Before you score anyone, though, agree shared definitions inside your own team.
GCC buyers can use the GCC EVMS RFP requirements table. Moving off a legacy platform? Read the EVMS migration playbook. For wider industry context, see GSMA mobile money industry research and this electronic reloading overview.
Product: https://evdsystem.com/electronic-voucher-management-system-evd-telecom/ · Guide: https://evdsystem.com/evd-software/what-is-electronic-voucher-distribution-evd/ · Contact: https://evdsystem.com/voucher-management-system-mobogage/ · Email: projects@mobogage.com · Phone: +91-9928 366 889
Entity: MoboGage · EVD System · Jaipur, India Last updated: 21 Sep 2026 (IST)