Electronic Voucher Management System by MoboGage

What is an electronic voucher management system?

An electronic voucher management system (EVMS / E-VMS) is software that manages the full lifecycle of prepaid vouchers—generation or intake, inventory and hierarchy allocation, multi-channel sale (POS, app, USSD, API), redemption into charging, and reconciliation—for telecom airtime, data, gift cards, and related digital products.

EVD System by MoboGage is that control plane for operators and VAS partners: one inventory truth, dealer float you can audit, and channel rules that apply whether the sale happens on a handheld POS, a dealer portal, or a partner API.

TL;DR for buyers

• Operators: Cut print and logistics OpEx where electronic channels can take share; tighten PIN custody; change denominations and promos without a reprint cycle; close the day against charging with fewer disputes.
• VAS partners: Run distribution as a productised service—hierarchy, commissions, white-label portals/POS, and APIs—without rebuilding lifecycle controls for every opco.
• Dealers & agents: Fast sale flows, clear wallet balances, and less risk from holding physical PIN stock.
• Outcome: Prepaid value moves under software control from batch creation to redemption—not through cartons and spreadsheet archaeology.

For how EVD, VMS, and eTopup relate as connected capabilities, see EVD vs VMS vs eTopup.

Five applications of an electronic voucher management system

1. Telecom airtime and data vouchers

MNOs and MVNOs use an EVMS to generate or intake PIN stock, allocate it through master dealers and retailers, and sell prepaid voice/data across retail and digital channels. Product catalogs stay policy-driven: denominations, expiry, and promo windows change in software instead of on a print press.

2. Gift cards and digital entertainment

The same lifecycle pattern extends to gift cards, OTT entitlements, gaming top-ups, and loyalty rewards. Catalogs can grow without fracturing inventory logic—serialisation, status, and reconciliation stay in one framework.

3. Dealer POS retail (Android / Linux)

Field sales still run on handhelds. EVD System is built for dealer and retail POS on Android and Linux platforms, including Sunmi-class terminals, with portal and mobile-app paths for assisted sales. Offline-capable POS behaviour matters where connectivity is uneven; terminal management (versions, config, disablement) belongs in the operating model, not as an afterthought.

4. Hybrid physical + electronic stock control

Many markets still need scratch cards alongside digital PINs. A serious electronic voucher management system can govern hybrid programmes under one set of controls—batch intake, status tracking, expiry, and audit—so physical logistics stop being the default cost of selling prepaid even when cards remain part of the mix.

5. API and aggregator distribution

Aggregators, super-apps, banks, and operator digital channels need documented APIs for sale, inquiry, and reporting—with a clean path to charging. One inventory truth and one fraud policy should apply whether the sale was on a kiosk POS or via a partner API.

Voucher lifecycle: generate → reconcile

Think of a pipeline with hard gates—not a shared folder of PIN files.

• Generate or intake — Controlled serialisation, denomination rules, batch metadata, expiry, and protection of voucher secrets. Unissued stock must never sit as plain text.
• Inventory — Digital stock with clear status (available, allocated, sold, redeemed, expired, cancelled).
• Allocate — Hierarchy that mirrors how the market sells: master dealers, regional distributors, retailers, agent wallets—with float, credit limits, and transfer rules ops will actually follow.
• Sell / activate — Approved channels only; PIN revealed at sale or PINless top-up posted; dealer float debited; transaction logged.
• Redeem — Credit hits charging / billing with duplicate and replay controls.
• Reconcile — Daily close that finance and fraud can trust: what sold, where, at what margin, with which exceptions, and what remains in each wallet.

Add expiry handling, blacklisting of compromised batches, and audit trails that survive operator review. Weak reconciliation leaks both the radio investment and the promotion calendar.

Feature table

Area	What buyers should expect
Security & trust	Encryption of voucher secrets at rest and in transit; role-based access; device and user authentication; duplicate, replay, and velocity controls; audit logs suitable for operator review.
Hierarchy & float	Multi-level dealer trees with credit limits; transfers and commission rules that match local practice; clear separation of operator stock vs partner float.
POS & field ops	Android / Linux POS support (including Sunmi-class handhelds); defined online/offline sale and sync behaviour where required; basic terminal management (versions, remote config, disablement).
APIs & integration	Documented APIs for sale, inquiry, reversal (where allowed), and reporting; a concrete path to charging / BSS—not a slide that only says “API ready.”
Reporting & ops	Near real-time views by region, dealer, product, and channel; reconciliation packs finance will use; exception queues with clear owners.
Catalog adjacency	Multi-product catalogs (airtime, data, gift, OTT) without fracturing inventory logic; dealer wallets that can support PIN sale and, where required, PINless eTopup paths.

If a vendor can only demo “generate PIN → show on phone,” keep looking.

Devices and integrations (honest scope)

Channels commonly in scope for EVD System deployments:

• Web portals for admin, distributors, and retailers
• Android and Linux POS applications (Sunmi-class and similar handhelds)
• Mobile apps for agents and partners
• USSD / SMS where smartphones are not the default
• APIs for aggregators and operator digital channels

Integration posture: EVD System is designed to sit BSS-adjacent—aligned with charging, dealer management, and partner onboarding. Exact charging adapters, USSD gateways, and device fleets are scoped per opco or VAS contract. Do not treat a public feature list as a guaranteed device matrix for every market; pressure-test offline behaviour, terminal support, and reconciliation packs in discovery.

Adjacent platforms: MoboGage also builds digital wallet and telecom VAS capabilities that can sit beside EVD where dealer float, merchant payments, or mobile money belong in the same operating story. Those are separate products—ask for the boundary that fits your contract.

Physical vouchers vs electronic voucher management

Dimension	Physical scratch cards	Electronic voucher management system
Production	Print, package, ship	Digital generation / secure intake
Denomination changes	Slow; reprint cycles	Fast; policy and catalog updates
Theft / leakage risk	High along the supply chain	Lower when PINs stay encrypted until sale
Inventory visibility	Delayed, often incomplete	Near real-time by hierarchy node
Channel reach	Retail shelf + limited partners	Web, POS, app, USSD/SMS, API
OpEx profile	Print, logistics, returns, write-offs	Software, float, channel ops
Promo agility	Weak	Strong (bundles, time-boxed offers)
Reconciliation	Manual, error-prone	Designed for daily close and audit

Hybrid programmes still exist. The point of an EVMS is that value moves under software control, so cartons stop being the default cost of selling prepaid.

How to implement EVD System (practical path)

• Discovery — Map where stock disappears, where denomination changes stall, and where channel sales disagree with charging. Fix operating model first (opco-owned, VAS-operated, or hybrid): who holds keys, who runs L1, who owns fraud policy.
• Pilot POS & portal — Stand up a controlled hierarchy slice with web portal plus a small Android/Linux POS fleet. Prove sale, float debit, and exception handling on a normal Tuesday—not only in a demo script.
• Hierarchy & float rules — Encode credit limits, transfers, and commissions to match how distributors actually work. If dealers distrust the float screen, they invent workarounds—and workarounds become leakage.
• Charging / BSS integration — Wire redemption and inquiry paths so sales and charging share one truth. Document reversals and duplicate controls before go-live volume.
• Go-live by region or dealer tier — Expand catalog and channels (USSD, API, apps) once reconciliation packs are trusted.
• Operate & reconcile — Daily close, exception queues, batch blacklist procedures, and terminal lifecycle (versioning, disablement). Treat EVMS as critical prepaid infrastructure, not a side app.

FAQ

What is an electronic voucher management system?

An electronic voucher management system is software that controls prepaid voucher value end to end: generate or receive stock, inventory and hierarchy allocation, multi-channel sale, redemption into charging, and reconciliation. In telecom, it is the lifecycle core behind airtime, data, gift, and similar digital products.

How is EVMS different from EVD software?

EVMS / VMS emphasises lifecycle and inventory control (generate, serialise, allocate, expire, cancel, reconcile)—often across physical and electronic stock. EVD emphasises the commercial and channel layer: how digital vouchers move to resellers and customers via POS, apps, USSD, and APIs. Strong platforms connect both; buyers who say “we need EVD software” usually mean this whole prepaid stack. See EVD vs VMS vs eTopup.

EVMS vs VMS vs eTopup — what’s the difference?

VMS/EVMS is the lifecycle core. EVD is distribution across channels. eTopup is often the PINless recharge itself—credit to a subscriber via dealer float or API without handing over a scratch PIN. One dealer wallet can support PIN sales and PINless top-up while VMS rules govern generation and reconciliation.

What channels does an EVMS support?

Typical channels include web portals, Android/Linux POS (including Sunmi-class handhelds), mobile apps, USSD/SMS, and APIs. Omnichannel only counts if the same inventory and fraud rules apply across those paths.

Can it run hybrid physical + electronic stock?

Yes—many programmes still mix scratch cards and digital PINs. The requirement is one control framework for batches, status, expiry, and audit so physical logistics are optional, not mandatory.

What should telecom operators evaluate before buying?

Operating model fit, a concrete charging/BSS approach, proven POS families and offline behaviour, lifecycle completeness through reconcile, security review posture, commercial clarity (licensing, hosting, transaction economics), and references that explain how reconciliation works on a normal day—not vanity rankings.

Does MoboGage EVD System support Android/Linux POS (e.g. Sunmi)?

Yes. EVD System deployments commonly include Android and Linux POS applications for shop and street sales, including Sunmi-class terminals, alongside web portals and APIs. Exact device fleets and offline sync behaviour are confirmed in project discovery.

How does reconciliation work at day-close?

Sales, float movements, redemptions, and exceptions should roll into packs finance and fraud can use: volumes by region/dealer/product/channel, remaining wallet balances, and clear owners for mismatches. If sales and charging disagree, you have a dispute factory—not a finished EVMS.

Next step

If physical vouchers still carry too much of your prepaid volume, start with a blunt assessment: where does stock disappear, where do denomination changes stall, and where do channel sales disagree with charging? Map that pain to hierarchy, channels, security, and reconciliation before you argue about UI colours.

Talk to MoboGage about EVD System

• Contact: https://evdsystem.com/voucher-management-system-mobogage/
• About MoboGage
• Email: projects@mobogage.com
• Phone: +91-9928 366 889

Deep dive on distribution concepts: What is electronic voucher distribution (EVD)? — including EVD vs VMS vs eTopup.

Last updated: 19 Sep 2026 (IST)