POTAir — one wallet for a fragmented telecom retail ecosystem
Telecom retailers serving customers across multiple networks had to maintain working balances across different operator-specific recharge systems. Money could be tied up in separate balances, while the retailer had to move between different operator workflows to serve customers.
POTAir consolidated that retailer experience into one web platform and one wallet. Retailers funded a single balance, selected the customer's service, and the platform routed transactions through the appropriate direct or aggregated integration.
Context
POTAir — short for Pay Over The Air — was a joint product with MobeePay, engineered by AnayaWorld starting in 2013. MobeePay provided an aggregation and API layer connecting multiple telecom services; AnayaWorld engineered the web product and the operating and business systems built around those integrations.
Retailer problem
Before POTAir, a retailer serving customers across several telecom networks had to carry separate working balances for each operator's own recharge system. That fragmentation meant capital sitting idle across disconnected balances, and a retailer switching between different operator workflows just to complete ordinary customer transactions.
Product concept
POTAir's premise was to give that retailer one place to work from: a single web platform, backed by a single funded wallet, able to serve a customer regardless of which telecom network they needed.
Unified wallet
A retailer funded one wallet balance on the platform. When they served a customer, they selected the requested service, and POTAir routed the transaction through the appropriate direct or aggregated integration — debiting that same wallet no matter which network the transaction ultimately reached.
System engineered
AnayaWorld built the full system behind POTAir: the web application and backend, a retailer portal, the API/integration layer connecting to MobeePay and direct services, the wallet itself, a commission engine, transaction and reporting systems, administration tooling, and sales-team tools for top-ups and reporting, together with transaction safeguards and business-rule logic. POTAir was a web-only product — no Android or other mobile app was built.
Transaction flow
A retailer logged into the POTAir web platform, selected the customer's requested service, and initiated the transaction. The platform determined whether that service was reached through a direct integration or through MobeePay's aggregation layer, processed the transaction, and adjusted the retailer's wallet accordingly.
Commission engine
The wallet accounted for retailer commission at the point of transaction rather than as a separate reconciliation step. As one configured example: a ₹100 recharge carrying a 2.5% retailer commission could debit ₹97.50 from the retailer's wallet — the commission the retailer earned was reflected directly in what left their balance, not settled afterward. This is a specific configured example, not a fixed platform-wide commission rate.
Safeguards
POTAir included configured business-rule safeguards against transaction misuse and failure states. One confirmed example: if a transaction failed or entered a failure state, the same mobile-number-and-denomination combination could be blocked from an immediate retry for approximately 30 seconds — a deliberate control against rapid repeated attempts on the same failed transaction.
Integration model
POTAir connected to telecom services through two integration paths: two to three connections were direct, and the remaining services were reached through MobeePay's aggregator/API layer. Which specific services used which path isn't published here pending further confirmation.
Launch
Development began in September 2013, and POTAir went live in November 2013.
Reach
POTAir operated in Jammu and Chandigarh.
Product lifecycle
The platform operated for approximately two and a half years. Further expansion would have required additional investment.