The intermediary problem
A typical prepaid electricity payment crosses five or more system boundaries: the customer’s mobile money wallet, the payment aggregator, the utility’s billing platform, the STS key management system, and the vending system that generates the 20-digit token. Each boundary is a potential point of failure. An SMS delay, a token entry error, a third-party platform outage — any one of them means the customer has paid but has no electricity.
Backend digitisation has attempted to patch this chain. Mobile apps now auto-submit tokens. USSD shortcuts reduce keystrokes. But every patch adds another software layer to a process whose fundamental architecture has not changed since the 1990s. The chain gets longer, not shorter. The failure points multiply.
Settlement at the device
EdgeMeter’s payment architecture moves settlement to the meter itself. The meter functions as a bank-affiliated payment terminal — settling the financial obligation at the point of consumption rather than routing it through intermediaries. The payment confirms. The meter credits. One transaction. No chain.
This does not replace mobile money. Mobile money remains the customer’s interface. What changes is the settlement path: direct from payment rail to device, with the bank sitting at the point of every electricity transaction rather than downstream of a mobile money intermediary.
Three things at once
This is where the three capabilities converge. The payment settles at the meter. The consumption event records simultaneously. The structured credit datum generates automatically. One device producing three outputs from a single event — a financial settlement, an energy measurement, and a credit record — because the architecture treats them as inseparable rather than as three separate systems bolted together after the fact.
Every enterprise that continues to treat metering, payment, and credit as separate infrastructure is maintaining three systems to do the work of one. Since the advent of the internet, Moore’s law, and now AI, the cost of maintaining legacy architecture is no longer just operational — it is competitive. Organisations that build on yesterday’s protocol are buying obsolescence at production scale.