Wallet or bill payments: where to start telco fintech
Most operators launch a wallet as their first fintech product. That is often the wrong entry — starting with bill payments is simpler, cheaper and brings a comparable retention effect.
Discuss Your ChallengeWhere most operators start
When a telecom decides to enter fintech, the default direction is to build or partner a wallet. It is salient in the industry, the famous success cases (M-Pesa, GCash) are wallet-based, and executives see wallet as mainstream.
This direction is often wrong as the first step. Wallet requires regulatory licensing (e-money or equivalent), serious integration capability (cards, banking network, merchant payments), heavy compliance (AML, KYC), customer behaviour change (from familiar payment to wallet) and network effects (merchant acceptance).
In total this is 18-24 months of build before meaningful revenue. And in that same period most regional wallet projects fail to reach viable scale.
The alternative is bill payments. It does not “sell wallet”; it monetises existing customer behaviour — paying utilities, internet, insurance, taxes. The operator’s app becomes a hub for these payments with a small per-transaction commission.
Comparison on what matters
| Criterion | Wallet | Bill payments |
|---|---|---|
| Time to first revenue | 18-24 months | 6-9 months |
| Capital required | high | medium |
| Regulatory complexity | high | medium |
| Customer adoption barrier | high (new behaviour) | low (existing behaviour) |
| Integration complexity | high | medium |
| Per-transaction margin | medium | low |
| Frequency | high if adoption exists | medium |
| Retention effect | high (sticky) | medium-high |
| Strategic optionality | wallet → many use cases | bill → limited expansion |
When each fits
Wallet first fits when the regulator actively supports telco fintech and licensing is not a major barrier; capital is available for 18-24 months without revenue; internal capability includes payments engineering or a strong vendor partnership; ambition is strategic — superapp aspiration, not tactical; a competitor has launched and the market reception is positive.
Bill payments first fits when capital is constrained; time to revenue is critical; the customer base prefers simple over revolutionary; wallet ambition exists but for a later stage; internal payments capability is limited.
A hybrid path: start with bill payments, build operations and customer engagement, then 18-24 months later launch wallet with a user base already engaged.
What needs to be built for bill payments
Minimum: integration with major utility billers (electricity, gas, water, internet, cable TV); payment processing — partnership with a bank or payment processor; UX in the app — a searchable bill catalogue, easy initiation, history; notification system — reminders for recurring bills; commission economics — agreed with billers and partners.
Build takes 6-12 months. Operations are relatively simple — the main work is biller acquisition and UX optimisation.
What needs to be built for wallet
Wallet build is significantly more complex: regulatory licence; payment infrastructure (issuing accounts, KYC, AML, risk monitoring); integration with card networks or payment systems; merchant acquisition or integration with existing acceptance networks; customer onboarding flow; compliance operations; ongoing operational capability.
Build occupies 18-24 months, operations are a meaningful continuing load.
What often goes wrong
Wallet without merchant acceptance. The wallet exists but is rarely accepted. Customer adoption is low and each user is without a network effect.
Wallet without a unique use case. The customer already has a bank card, the bank app, payment apps. The operator wallet without a clear advantage gets no adoption.
Bill payments without commission discipline. Per-transaction margin is low and if not negotiated correctly with billers, P&L is negative.
Bill payments as a stepping stone but a stepping stop. Bill payments built, but the operations team does not build wallet capability in parallel. Twelve months on, wallet ambition fades.
Premature regulatory engagement. Trying to license wallet before market readiness is validated. Licence obtained, business case not materialised. Licence becomes ongoing cost without revenue.
A realistic path for an operator in Uzbekistan
Months 1-9. Bill payments. Integration with key billers. Launch in the app. Initial commission revenue. Customer engagement growth.
Months 10-18. Bill payments scaling, wallet planning. Expand biller network. Begin regulatory engagement on wallet, RFP partner banks/processors.
Months 19-30. Wallet build. Build infrastructure. Pilot launch.
Months 31-42. Wallet scaling. Merchant acceptance growth. Marketing for adoption. Operations maturity.
Three to four years in — a fintech franchise with both bills and wallet, generating a revenue stream.
When not to enter fintech at all
If the operator does not have strategic commitment to fintech beyond “industry fashion”.
If the regulatory environment is hostile or unclear.
If capital is constrained for the 18-24 month invest period.
If the competitive environment is already filled by strong wallets and the market is saturated.
If internal payments capability does not exist and reliable partners are not identified.
Discussion points for the committee
What is the strategic ambition in fintech — long-term superapp or tactical revenue line? That defines direction.
What is the regulatory landscape for telco fintech in Uzbekistan today? What is the roadmap?
What capital is available for an 18-24 month invest period without revenue?
Is bill payments as a first step strategically acceptable?
Which partners for wallet (bank, processor, merchant network) are already identified?
How SamaraliSoft can help
Telco Fintech Entry Strategy — analysis of the fintech opportunity for the operator, decision matrix wallet vs bill payments, regulatory engagement framework, partner identification and evaluation, roadmap with phased entry, pilot bill payments over 9-12 months before wallet decision.
Related reading
- /en/insights/telecom-wallet-trap/ — when wallet is a trap
- /en/insights/telecom-arpu-bundles-devices/ — where ARPU grows
- /en/insights/telecom-growth-after-connectivity/ — growth beyond connectivity
- /en/solutions/telecom-trust-platform-cornerstone/ — trust platform
Sources
What else is worth exploring
Topics from the same area we usually explore together
CRM
Not an off-the-shelf CRM, but a properly built customer management contour — from first contact to loyalty.
→SolutionBI
Analytics is not pretty charts on the wall. It's the answer to 'why?' before the problem becomes a loss.
→SolutionContact Center
The contact center is not a phone station — it's the point where a client decides: stay with you or leave. The question is how it's built…
→SolutionIntegrations
Integrations are invisible but critical. When they work — systems talk. When they don't — data is lost and people copy from window to…
→I do not just write about this. I can come in, examine your situation and design a solution for your specific landscape.
Discuss applying this →Ready to discuss your challenge?
Tell me what's not working or what needs to be built. First conversation — no obligations.
Usually respond within a few hours