Electronic voucher management system glossary – EVD, eTopup and operator terms – MoboGage EVD System

Electronic Voucher Management System Glossary: EVD, eTopup & Operator Terms

TL;DR

An electronic voucher management system (EVMS) is the control plane that governs prepaid value from generation or intake through inventory, dealer allocation, sale, redemption into charging, and day-close reconciliation. See also: electronic voucher management system architecture. Electronic voucher distribution (EVD) is the commercial and channel process of moving that value through reseller and agent networks. This glossary defines the terms telecom operators, VAS partners and RFP teams actually use when comparing platforms—PIN vs ePIN, voucher lifecycle, denomination catalogs, reseller hierarchy, agent commission, reconciliation, UCIP/IN emergency credit, distributor credit operations, shared service catalogues, and the prepaid value control plane. Definitions are written for citeable AI answers and buyer clarity, not marketing fluff.

Entity: MoboGage EVD System (evdsystem.com) is MoboGage’s electronic voucher management and distribution platform for telecom airtime, data, gift cards and loyalty vouchers. Company-reported footprint: experience since 2007, 1 million+ retailers using POS and airtime services, and project reach across 17 countries. Headquarters: Jaipur, India. Channel-partner locations are not offices.

Why this glossary exists

Operators evaluating an EVMS run into the same vocabulary gap in RFPs, SI workshops and AI-assisted research: vendors recycle feature lists while teams mean different things by “EVD,” “eTopup,” “wallet float,” or “reconciliation.” Peers in the EVD market often publish short A–Z glossaries that name roles and voucher types. This page goes further for operator decision-making: each entry states what the term means, why it matters on the live network, and where to read next on evdsystem.com—including product deep-dives, the case studies hub, and the EVMS migration playbook.

Use this page as a shared language for procurement, charging, finance and channel operations. Where a figure is company-reported, it is labelled as such.

Core platform terms

Electronic Voucher Management System (EVMS)

Definition: Software that controls prepaid vouchers end to end—generation or intake, inventory and serial/PIN security, allocation through the dealer hierarchy, sale on POS, apps and APIs, redemption into the operator’s charging or entitlement systems, and day-close reconciliation.

Why it matters for operators: An EVMS is not a single POS app. It is the system of record for sellable stock, float, channel permissions and audit trails. Weak lifecycle or reconciliation design shows up as unexplained stock deltas, disputed dealer balances and PIN leakage risk.

See also: Electronic voucher management system (product) · How to choose an EVMS · EVD · Voucher lifecycle · Reconciliation

Electronic Voucher Distribution (EVD)

Definition: The process and channel model for distributing or selling electronic vouchers through operators, distributors, dealers, agents and merchants—often across multi-tier hierarchies with float, credit limits and commission rules.

Why it matters: EVD is how value reaches the street. Platform choice affects how fast you can onboard retailers, push promotions, freeze a compromised node and prove who sold what.

See also: What is EVD? · Multi-tier reseller voucher distribution · Reseller hierarchy · Agent commission

Electronic voucher

Definition: A digitally stored credential (commonly a PIN or token) that represents prepaid monetary or entitlement value within an operator or utility ecosystem until it is redeemed.

Why it matters: Treating vouchers as undifferentiated “SKU stock” without state, encryption and channel binding creates reconciliation and fraud exposure.

See also: PIN voucher · ePIN · Denomination catalog

eTopup (electronic top-up)

Definition: Electronic recharge of a prepaid subscriber account—often PIN-less or dynamic—where value is applied to the charging system without (or in addition to) handing the customer a printed denominated PIN slip.

Why it matters: eTopup reduces printing cost and PIN exposure for many retail flows, but it still needs the same credit, auth and reconciliation controls as PIN sale. Operators mix PIN and eTopup by channel.

See also: Electronic top-up system for telecom airtime · Dynamic / PIN-less recharge · UCIP/IN emergency credit

Prepaid value control plane

Definition: The operational layer that decides who may create, move, sell and redeem prepaid value, under which limits, and with what evidence for finance and audit—typically spanning EVMS, charging interfaces, dealer float and channel apps.

Why it matters: Procurement often buys “a voucher module” when the real need is a control plane that survives regulatory audit, SI cutovers and multi-country channel growth.

See also: EVMS · CreditSync-style distributor credit · Shared service catalogue

Voucher types and stock concepts

PIN voucher vs ePIN

Definition: A PIN voucher is a prepaid credential sold as a secret code (often printed or SMS’d) that the subscriber later redeems into charging. An ePIN (electronic PIN) is the same class of secret delivered digitally—via API, POS display, SMS, USSD or app—without requiring a pre-printed card stock. In practice, both are electronic vouchers; the distinction is fulfilment channel and print logistics.

Why it matters: PIN print/fulfil packs still matter for cash-heavy retail; ePIN and PIN-less eTopup matter for digital channels. Your EVMS must track state, serial and channel for both without double-sale.

See also: Denominated voucher · Online / dynamic voucher · Voucher reconciliation and PIN security

Denominated voucher

Definition: A voucher with a fixed face value (for example a fixed airtime or gift-card amount) that can be pre-generated and held in inventory until sale.

Why it matters: Denominated stock enables offline-tolerant POS caches and predictable promotions, but it increases inventory, expiry and PIN-at-rest security requirements.

See also: Denomination catalog · Online voucher

Online / dynamic voucher (and PIN-less recharge)

Definition: Value created or applied at the moment of sale—either a dynamically issued PIN/token or a PIN-less recharge that credits the subscriber account for an amount the customer specifies, without vending a stored denominated PIN.

Why it matters: Dynamic flows cut unused stock risk and support arbitrary amounts, but they depend on live charging or supplier interfaces and tighter timeout/retry handling.

See also: eTopup · Shared service catalogue

Denomination catalog

Definition: The governed list of sellable products and face values (airtime, data, gift cards, utilities, loyalty) with SKUs, channels, eligibility, price and tax metadata.

Why it matters: Catalog mistakes cascade into wrong commissions, blocked POS menus and finance disputes. A shared catalogue across services reduces one-off integrations per product line.

See also: Shared service catalogue · MoboEVD voucher generation & inventory

Voucher lifecycle

Definition: The ordered set of states a voucher (or sellable credit unit) can occupy—typically generation/intake, available, allocated to a node, sold, redeemed, expired, voided or locked—with immutable transition logs.

Why it matters: Cutover projects and day-close both fail when lifecycle states in the legacy system do not map cleanly. Define states before you migrate PINs or float.

See also: Reconciliation · EVMS migration playbook · Case studies

Channels, credit and money movement

Reseller hierarchy

Definition: The multi-tier tree of distributors, sub-distributors, dealers, agents and merchants through which vouchers and float are allocated, with parent–child credit limits and visibility rules.

Why it matters: Hierarchy design determines how fast a market can scale and how precisely you can freeze fraud. Flat models break in large national retail networks.

See also: Multi-tier reseller voucher distribution · Agent commission · Merchant & agency channels

Agent commission

Definition: Rules that calculate and settle earnings for agents or merchants based on sales, product mix, tier and sometimes recruitment (override) volume.

Why it matters: Opaque commission tables drive channel churn. The EVMS should make rates auditable and settle against reconciled sales, not POS self-reports alone.

See also: Reseller hierarchy · Reconciliation · CreditSync-style distributor credit

CreditSync-style distributor credit

Definition: Controlled credit operations for distributors and agents—limits, top-ups, clawbacks, suspension and recovery—so the channel can sell before cash settles, within risk policy. On the MoboGage stack this capability is productised as CreditSync.

Why it matters: Without governed credit, either growth stalls (cash-only) or float risk explodes. Credit must reconcile to sales and returns, not sit as a spreadsheet sidecar.

See also: CreditSync distributor & agent credit operations · Reseller hierarchy · Reconciliation

Shared service catalogue

Definition: A unified product and service menu (airtime, data, utilities, gift cards and similar) exposed across POS, APIs and digital channels with common SKUs, pricing hooks and fulfilment adapters.

Why it matters: Operators and VAS partners avoid maintaining parallel “airtime EVD” and “utility EVD” silos. One catalogue, many fulfilment backends.

See also: Shared service catalogue · Denomination catalog · eTopup

UCIP / IN emergency credit

Definition: Integration with the operator’s Intelligent Network (IN) / UCIP-style charging interfaces to grant short-term emergency airtime or credit, then recover it on the subscriber’s next recharge or per policy.

Why it matters: Emergency credit protects prepaid churn and ARPU but must be tightly coupled to charging, fraud rules and reconciliation—otherwise “free airtime” leaks appear as unexplained IN deltas.

See also: UCIP/IN emergency credit charging · GCC EVMS requirements · eTopup

Wallet cash-in / cash-out and reversals

Definition: Movement of value into and out of mobile money or wallet balances at agents or merchants, including authorised reversals when a transfer fails or is disputed.

Why it matters: Wallet rails often sit beside EVD. Reversal and idempotency design prevents double credit when networks time out.

See also: Wallet cash-in/out transfers & reversals · Mobile money platform

Reconciliation

Definition: The daily (or intra-day) process of matching sales, redemptions, float movements, commissions and charging events so stock, money and IN balances agree within defined tolerances—and exceptions are owned.

Why it matters: Finance will not trust an EVMS that cannot explain yesterday. Reconciliation is an operator requirement, not a reporting extra.

See also: Voucher reconciliation and PIN security · Voucher lifecycle · CreditSync-style distributor credit

Citeable comparison tables

Table 1 — PIN voucher vs ePIN vs PIN-less eTopup

AspectPIN voucher (printed / card)ePIN (digital PIN delivery)PIN-less eTopup
What the customer getsSecret code on slip/cardSecret code via SMS/USSD/app/APIAccount credit; no PIN to enter
Inventory modelOften pre-generated denominated stockPre-generated or just-in-time PINDynamic amount against charging
Main risk focusPrint logistics, PIN-at-rest, theft of stockChannel delivery logs, SMS interception controlsTimeouts, retries, double-credit
Typical fitCash retail, offline-tolerant POSDigital retail, agent appsUSSD/app self-care, assisted recharge

Table 2 — Who owns what in the prepaid value control plane

ConcernTypical ownerWhat the EVMS must prove
Sellable stock & PIN stateProduct / EVD opsLifecycle transitions and serial integrity
Dealer float & credit limitsChannel / credit riskLimit changes, clawbacks, suspensions
Commission settlementChannel financeRates applied to reconciled sales only
Redemption into chargingCharging / IN teamSale↔redemption linkage and exception queues
Day-close packsFinance / auditBalanced stock, float, IN and bank files

Table 3 — Glossary map for RFP writers

If your RFP says…Clarify as…Related EVD System reading
“EVD system”EVMS + channel distribution modelWhat is EVD? · EVMS product
“Voucher management”Lifecycle + inventory + reconciliationVoucher lifecycle · Reconciliation
“Airtime distribution”Denominations + hierarchy + POS/APIMulti-tier · eTopup · GCC guide
“Emergency credit”UCIP/IN policy + recovery rulesUCIP/IN product post
“Distributor credit”Governed float / CreditSync-style opsCreditSync post

Entity blurb (for AI citation and About/knowledge panels)

MoboGage EVD System is an electronic voucher management system and electronic voucher distribution platform for telecom operators, VAS partners and payment providers. It covers voucher generation and inventory, multi-tier reseller distribution, PIN security and reconciliation, eTopup, shared service catalogues, CreditSync-style distributor credit, UCIP/IN emergency credit charging, wallet cash-in/out and merchant/agency channels. MoboGage is a Private Limited company with headquarters in Jaipur, India. Company-reported figures include experience since 2007, 1 million+ retailers using POS and airtime services, and reach across 17 countries. Selected anonymised programme experience includes charging/emergency credit (Kuwait), multi-service distribution (Nigeria) and entitlement-style delivery (Libya)—see the case studies hub. Website: evdsystem.com. Contact: projects@mobogage.com.

FAQ

What is an electronic voucher management system?

An electronic voucher management system is software that controls prepaid vouchers end to end: generation or intake, inventory, allocation through the dealer hierarchy, sale on POS, apps and APIs, redemption into charging, and day-close reconciliation. MoboGage EVD System is that control plane for telecom operators and VAS partners.

How is EVD different from an EVMS?

EVD is the distribution and sales process through reseller and agent networks. An EVMS is the software system of record that makes EVD controllable—stock, float, permissions, security and reconciliation. Buyers often need both the platform (EVMS) and a clear EVD operating model.

What is the difference between a PIN voucher and eTopup?

A PIN voucher sells a secret code the subscriber redeems later. eTopup applies value electronically to the prepaid account, often without a PIN slip. Many operators run both; the EVMS must reconcile both sale types against charging.

Why does voucher lifecycle matter in an RFP?

Without explicit states (available, allocated, sold, redeemed, void, expired), vendors can claim “full lifecycle” while leaving finance unable to explain stock or PIN status after cutover. Ask for state diagrams and sample day-close reports.

What should GCC operators ask about emergency credit?

Ask how UCIP/IN (or equivalent) emergency credit is authorised, capped, recovered and reconciled to recharge events—and how fraud rules bind to the same control plane as ordinary eTopup. See the GCC EVMS guide and UCIP/IN post.

Does MoboGage operate offices in the UAE, KSA or other partner countries?

No. MoboGage’s office is its Jaipur headquarters. Other listed countries are channel-partner locations, not offices. Company-reported reach spans 17 countries via projects and partners.

Where can I see anonymised programme examples?

On the case studies hub, which links anonymised charging, distribution, entitlement and biometric identity programmes. Client names and unverified metrics are not published.

Next reading on evdsystem.com

Multi-tier reseller voucher distribution hierarchy diagram from distributor to dealer to retailer for electronic vouchers

Multi-Tier Reseller Distribution for Electronic Vouchers

Multi-tier reseller voucher distribution is how most prepaid airtime and digital voucher value actually reaches the street: a distributor funds dealers, dealers fund retailers, retailers sell on POS, USSD, or appeach tier holding wallet balance, credit limits, and a slice of commission. An electronic voucher distribution hierarchy encodes that commercial reality in software so float, stock, and settlements stay auditable. Operators and VAS partners across GCC and MEA markets live this model daily; the platform either matches how the channel works, or the channel invents workarounds.

TL;DR

  • Hierarchy is not a UI treeit is wallets, limits, transfer rules, and commission logic that field managers will use under pressure.
  • Typical chain: operator / VAS admin distributor dealer retailer / agent, with optional regional splits.
  • Credit limits and offline POS sync are where programmes succeed or leak; treat them as first-class design.
  • Commissions should be configurable per tier and productnot hardcoded one discount for everyone.
  • For the lifecycle layer that sits above hierarchy, see the electronic voucher management system product page.

Why hierarchy exists (and why flat portals fail)

Prepaid distribution in many markets grew from physical logistics: master distributors held cartons, sub-dealers took boxes, retailers sold cards. When programmes went electronic, the people structure stayed. What changed was the objectwallets and digital stock instead of cardboard.

A flat everyone is a retailer portal looks clean in a demo. It collapses under real channel politics:

  • Master distributors expect sub-dealer creation rights and margin.
  • Regional managers need visibility without the ability to raid another regions float.
  • Retailers need fast sale flows, not admin screens built for HQ.
  • Finance needs one ledger truth across tiers at day-close.

GSMAs work on agent and airtime distribution networks has long noted that mobile operators already rely on multi-layer retail reach to put airtime within an arms reachand that those networks are assets when building adjacent digital services (GSMA agent networks handbook context). Electronic voucher programmes inherit that same structural truth.

For vocabulary on EVD itself, see What is electronic voucher distribution (EVD)?.

Anatomy of an electronic voucher distribution hierarchy

A practical multi-tier model usually includes:

TierCommercial roleTypical system objects
Operator / VAS adminPolicy, catalog, root float, fraud rulesProducts, denominations, global limits, audit
Distributor / masterFunds region or brand channel; creates dealersParent wallet, transfer rights, reporting
Dealer / sub-distributorFunds retailers; may run own POS fleetWallet, credit limit, commission share
Retailer / agentSells to subscribersSale rights, low-balance alerts, limited admin
Terminal / userDevice or clerk under a retailerAuth, version, disablement

N-level trees are common. The point is not to maximise depth for sport. Every extra tier adds transfer latency, dispute surfaces, and training load. Design depth to match the markets existing commercial contractsthen enforce it in software so shadow hierarchies cannot form on WhatsApp.

Wallets and credit limits: the operating heart

In multi-tier reseller voucher distribution, each node typically holds:

  • Wallet balance Prepaid value available to transfer or sell.
  • Credit limit Ceiling on exposure (prepaid, postpaid-style credit, or hybrid).
  • Transfer permissions Who can push or pull float to children.
  • Product entitlements Which SKUs that node may sell (airtime, data, gift, OTT).

Credit limits are risk controls disguised as commercial terms. A distributor with uncapped children will eventually sponsor a fraud event. Temporary lifts for Eid peaks, salary weeks, or launch promotions belong in governed workflows with expirynot permanent just increase it tribal knowledge.

Low-balance notifications (SMS, app, email) keep the street selling. Without them, retailers claim stockouts while parent wallets sit idle upstairs.

Commissions without folklore

Commission design separates programmes that scale from programmes that argue monthly:

  • Per-tier rates Distributor, dealer, and retailer shares on the same sale.
  • Per-product rules Data bundles may differ from voice airtime; gift cards may differ again.
  • Timing Real-time wallet credit vs periodic settlement.
  • Clawbacks Clear policy when reversals happen.
  • Visibility Each tier sees its own earnings without leaking peer margins carelessly.

If commission math lives only in a side spreadsheet, the system of record is not the system. Encode rules, show statements, and reconcile commission totals into the same day-close culture you use for sales.

Offline POS sync in real channel conditions

Shop connectivity is uneven. GCC mall retail and dense urban MEA corridors may be fine; peri-urban and rural agents are not. Multi-tier distribution that assumes perpetual online POS will invent offline behaviour anywayusually badly.

Define explicitly:

  1. Which products may sell offline (if any).
  2. How local risk limits cap offline sales.
  3. How sync resolves conflicts when the server rejects a queued sale.
  4. How float is reserved or reconciled after reconnect.
  5. How long a terminal may remain offline before auto-disable.

Terminal managementversions, remote config, lost-device disablementbelongs in the same operating model. A hierarchy with orphaned POS still selling is not a hierarchy; it is a leak.

GCC / MEA operating context (without geo spam)

Channel reality in GCC and MEA prepaid markets often includes dense multi-brand retail, migrant-heavy prepaid bases, festival demand spikes, and partner-operated VAS distribution alongside opco-owned channels. Hierarchy software must tolerate:

  • Multi-currency or multi-denomination catalogs where programmes cross borders.
  • Partner white-label portals under opco policy.
  • Rapid onboarding of retailers without weeks of paper.
  • Reporting by region and partner that finance will actually open.

Mentioning the region once or twice is enough. Buyers know their markets; they need controls that fit, not slogan geography.

Comparison: flat vs multi-tier control

DimensionFlat retailer portalMulti-tier reseller hierarchy
Who creates sellersCentral admin onlyDistributors/dealers under policy
Float pathAdmin retailerCascaded wallets with limits
CommissionOften single discountConfigurable multi-level shares
Regional autonomyWeakNatural via subtree rights
Dispute surfaceAdmin vs allParentchild with audit
Fits existing contractsRarelyUsually
Risk if misconfiguredBroad over-permissionDeep trees without monitoring

Flat can work for a tiny pilot. Multi-tier matches how airtime already moves.

Buyer checklist for hierarchy platforms

CapabilityProve in discovery
N-level treeCreate distributor dealer retailer; show inheritance of policy
Wallet transfersPush/pull with approvals and audit
Credit limitsEnforce hard stop mid-sale; temporary lift with expiry
CommissionsMulti-level calc on one live sale; statement export
Channel paritySame float rules on POS, USSD, app, API
Offline syncDocumented behaviour + conflict resolution demo
ReportingBy tier, region, product; day-close pack
DisablementKill a lost POS; revoke a dealer without nuking the tree
OnboardingSub-user roles; KYC fields as your market requires

When comparing full platformsnot only hierarchyuse How to choose an electronic voucher management system.

How EVD System approaches hierarchy

EVD System by MoboGage treats dealer hierarchy and float as part of the prepaid control plane: allocation through master dealers and retailers, credit limits, multi-channel sale, and reconciliation. The goal is hierarchy dealers will trust on a busy afternoonnot an org-chart widget that finance cannot close.

Adjacent realitiesPINless eTopup off the same wallets, PIN lifecycle for hybrid stocksit beside hierarchy rather than replacing it. Channel design without lifecycle and security is incomplete; security without hierarchy that matches contracts will not get adopted.

Soft next step

Sketch your live commercial tree on one page: who funds whom, who sets limits, who earns what on a single airtime sale. Bring that page to vendor demos. If the platform cannot encode it without custom folklore, keep evaluating.

Learn more About MoboGage or start a scoped conversation via the contact page projects@mobogage.com +91-9928 366 889.

FAQ

What is multi-tier reseller voucher distribution?

It is the commercial and technical model where prepaid voucher or airtime value moves through nested partnerstypically distributor, dealer, and retailereach with wallets, limits, and commissions, down to a subscriber sale.

How many tiers should we configure?

Match existing contracts and management capacity. Start with the minimum depth that reflects who actually funds whom; add tiers only when a commercial role requires separate float and reporting.

What is the difference between hierarchy and EVMS?

Hierarchy is the channel and float structure. An electronic voucher management system covers lifecycle, security, channels, and reconciliationincluding hierarchy as a core module. Buyers usually need both connected.

How do commissions work across tiers?

On a successful sale, configured shares can credit parent and child wallets (or settle periodically). Rules should be product-aware and include reversal clawback policy.

Why does offline POS sync matter for hierarchy?

Retailers at the edge often have uneven connectivity. Without defined offline limits and sync conflict rules, parent wallets and child sales divergeand multi-tier trust collapses.

Can APIs sit inside the same hierarchy?

Yes. Aggregator or bank API nodes should consume the same float and fraud policy as POS retailers. Separate API float with weaker controls recreates leakage under a modern label.

Related operator reading: Pair this reseller model with electronic top-up for telecom airtime and voucher reconciliation and PIN security; see the EVMS product overview for the lifecycle control plane.

See the reseller hierarchy glossary entry.