Teardown: sending money with a mobile wallet
Mobile money lets hundreds of millions of people send money with a phone number, many of whom never had a bank account nearby. This lesson applies the teardown method from pm-40 to three systems: M-Pesa in Kenya, bKash in Bangladesh, and the UPI payment apps in India. You will see how the money actually moves, why agents mattered more than the app, who pays when sending is free, and how trust and fraud shape every screen.
By the end you can
- Explain how e-money, agents and a bank trust account turn cash into a phone balance and back
- Compare a telecom-led wallet, a bank-led wallet and an open bank-to-bank network
- Explain where a wallet's money comes from when sending is cheap or free, and why UPI apps struggle to earn
- Name the main trust and fraud risks and the product controls against them
- Write copy, adapt and avoid lessons for a business that collects cash and pays riders
The everyday picture
Two shopkeepers trust each other: one in the city, one in a village a day's bus ride away. A factory worker hands the city shopkeeper $50 in cash. The shopkeeper writes it in his notebook and phones his friend in the village, who hands $50 from his own drawer to the worker's mother. No cash travels. Once a month the two shopkeepers settle up.
That is most of a mobile wallet. The notebook became a computer, the phone call became a text message, and thousands of corner shops became the shopkeepers. Notice what the hard parts are. Writing in the notebook is easy. Making sure the village shopkeeper has cash in his drawer when the mother arrives, and making sure nobody lies about what the notebook says, are the problems the whole system is built around.
Users and jobs: the job was sending money home
Start the teardown with the decision question. Imran's is: "What should Mangrove copy from mobile wallets to move cash-on-delivery customers to digital payments, and should it ever build its own wallet?" About 35% of Mangrove's app orders are paid in cash at the door.
Then the sides and their jobs. A mobile wallet has at least five: the sender, the receiver, the agent who swaps cash for balance, the merchant who accepts payments, and the operator who runs the ledger under a regulator's rules.
The most useful finding comes from history. Safaricom and Vodafone piloted M-Pesa in Kenya in October 2005, funded through a UK government challenge fund, to handle loan repayments for customers of a microfinance lender. When it launched fully in March 2007, the job people hired it for was sending money to family. Before M-Pesa, many people sent cash with a friend or a bus driver; a postal money order cost roughly US$3 to US$6 and was slow; and only about 30% of adults in East and Southern Africa had a formal bank account (Mbiti and Weil, 2016). The product found its real job after launch, a reminder that a teardown should look at what people do with a product, which may differ from what it was built for.
bKash, launched in July 2011 as a subsidiary of BRAC Bank, served the same job for a different crowd. The GSMA's 2013 case study describes workers who moved to cities sending money to rural families. UPI, India's Unified Payments Interface, launched as a pilot on 11 April 2016 with 21 banks. Its job was wider: pay anyone with an account at any bank, instantly, including a shop, by scanning a QR code.
Quick check
M-Pesa's pilot was built for microfinance loan repayments, but people used it to send money to family. What does this teach a teardown?
The useful lesson is about method: the behaviour you observe tells you the real job. Calling it a mistake misses that the pilot is how they found out. Nothing here shows loan repayment is a bad use, and "design for everything" is how products end up doing nothing well.
How the money actually moves
In agent wallets such as M-Pesa, the balance on your phone is e-money. When you hand an agent $50 in cash, nothing is created: $50 of the agent's e-money balance, called float, moves to your wallet, and your $50 goes into the agent's drawer. When you send money, two numbers change in the operator's ledger. When the receiver cashes out, her e-money moves to the village agent, who gives her cash from his drawer, minus a fee.
The real money behind all that e-money sits in a bank. The GSMA's case study says the central bank required bKash to hold the full value of customer balances in a designated BRAC Bank account that the central bank monitors. So the total never changes when people send money to each other; only the names next to the numbers change.
Now look at the agents. City agents keep receiving cash and giving out float, so they end up with full drawers and no float. Village agents keep giving out cash and receiving float, so they end up with the opposite. Both must rebalance, usually by depositing or buying cash through a bank or a larger agent. This is called liquidity management, and it is an operations product in its own right: alerts when an agent is running low, routes for the people who move cash, and rules about who can rebalance with whom. The details of each operator's rebalancing are not public; the imbalance itself follows from how the ledger works.
UPI works differently, and the difference explains its business model. There is no e-money. Each user's UPI ID is tied to a bank account and a mobile number checked against the bank's records, and money moves from one bank account to another over a network run by the National Payments Corporation of India (NPCI). Any UPI app can reach any bank account, and one app can hold several accounts. So an app like PhonePe or Google Pay is a front end: it shows you the screens, but your money stays in your bank. That makes switching apps easy, which matters for how they earn.
| Design | Example | Who holds the money | Who can join |
|---|---|---|---|
| Telecom-led e-money | M-Pesa, Kenya, 2007 | The operator, backed by bank trust accounts | Customers of one mobile network at the start |
| Bank-led e-money | bKash, 2011 | A bank subsidiary, backed by a monitored bank account | Customers of several mobile networks |
| Open bank-to-bank network | UPI apps, India, 2016 | The user's own bank; the app holds nothing | Anyone with a bank account, through any app |
Quick check
Thousands of workers send money home from a city at the end of the month. What problem does this create for agents, and where?
Money flowing from city to village means cash goes into city drawers and comes out of village drawers. Village agents give out cash and receive float, so they run short of cash. E-money moves without cash only inside the ledger; cash-out still needs real notes in a real drawer.
Agents: the branch network nobody had to build
A bank branch costs a lot to open. An agent is an existing shop that adds a phone, a notebook and some float. M-Pesa's agent network grew from about 450 outlets in mid-2007 to more than 18,000 by April 2010 (Mbiti and Weil). By the year to March 2025, Safaricom reported about 299,000 M-Pesa agents in Kenya and about 35.8 million customers who had used M-Pesa in the last month. bKash had about 30,000 agents after 17 months, almost one for every two rural villages according to the GSMA in 2013; it now reports more than 350,000 agents, more than 83 million registered customers and more than 900,000 merchants.
The agents create the product's main loop. More agents near people make cash-in and cash-out easy. Easy cash makes people trust the wallet, so more people use it. More users mean more transactions per agent, so each agent earns more commission, and more shops want to become agents. The same loop explains why a late copycat struggles: the first wallet already has an agent on every street, and its users can send to everyone they know.
The loop has one weak point, and it is physical. If a customer walks to an agent and the agent has no cash, the wallet has failed her, whatever the app looks like. That is why liquidity, agent training and agent fraud controls take as much product work as the customer app. For PMs who build internal tools, the agent's menu is a frontline tool used all day by shop staff, with the same needs as a store scanner: speed, clarity, working on a cheap phone and on patchy signal (Designing for frontline work). Customers of the bank-led wallet used a numbered USSD menu that worked on handsets costing about $15 in 2013.
Fees, and who pays for "free"
Follow the money. In 2013 the GSMA recorded bKash's prices as: registration and cash-in free, sending money a flat Tk 2 (about 2 US cents) whatever the amount, and cash-out 1.85% of the amount. The pattern is common: putting money in is free, moving it is cheap, and taking it out costs the most, because cash-out pays the agent for keeping cash. Customers notice. A 2018 study reported by The Daily Star found that 53% of the households surveyed named high charges as a major disadvantage of mobile money. In October 2021 it cut the cash-out price to Tk 14.90 per 1,000 (1.49%) for up to Tk 25,000 a month from a customer's chosen "favourite" agent, which also gives each customer a reason to stick to one agent.
M-Pesa's prices push the other way at the small end. Since January 2021, Safaricom's tariff makes transfers of KES 100 and below free; sending KES 101 to 500 costs KES 6. Small payments are where cash is hardest to beat, so the first ones are free. Larger transfers, cash-out and business payments carry the fees. In the year to March 2025, M-Pesa earned KSh 161.1 billion, 44.2% of Safaricom's service revenue in Kenya, with about 38 chargeable transactions per active customer by Safaricom's measure. Credit sits on top: Fuliza, an overdraft on M-Pesa, launched in January 2019. A wallet that sees every payment a person makes can judge small loans, the same pattern you will see in Square's loans in pm-43.
UPI apps face the hardest version of the question. Since 2020, merchants have paid no fee on most UPI payments, and users pay nothing to send. Volume exploded: about 20 billion UPI transactions in August 2025 alone. In July 2025, a month of about 19.5 billion, PhonePe processed about 46% by number and Google Pay about 36%. But PhonePe reported a net loss of about ₹1,727 crore (roughly US$200 million) for the year to March 2025, on revenue from operations of about ₹7,115 crore. Its lending and insurance distribution, while small, roughly tripled. The public summaries we read don't explain fully where its payments revenue comes from; likely sources include merchant payments by card and wallet, bill payments and payment devices for shops (inference). NPCI also plans to cap any app's share of UPI volume at 30%, with the deadline pushed to the end of 2026.
Rules can change the model overnight. On 14 September 2026, India's finance ministry notified that a merchant fee may be charged on UPI and RuPay debit payments above ₹2,000; payments up to ₹2,000 stay free, and NPCI is to decide the rate and which merchants pay. When this lesson was written, those details were not yet set. For a teardown, this is the moat lens in action: when the network is public infrastructure and the price is set by regulation, apps compete on reach and design, and they earn from what they sell on top.
Quick check
Why do wallets often make cash-in free and cash-out the most expensive step?
Agents must hold real notes, and the cash-out fee is how they are paid for it. The price also nudges people to pay a shop or a bill from the wallet instead of withdrawing, which keeps money in the system. Nothing in the sources says regulators require it, and data use is the same for both.
Trust, fraud and why wallets beat banks
A wallet has to be trusted by people who have never had a bank, so trust is a product feature. Three mechanisms show up in all three systems. Identity: M-Pesa checked customers against Kenya's national identity cards at registration, and UPI ties each ID to a bank account and a mobile number the bank has checked. Confirmation: both sides get a message for every transfer, and well-designed flows show the receiver's registered name before you confirm, so a mistyped number is caught. Limits: smaller limits for lightly checked accounts reduce what a thief can take.
Fraud follows the easiest path, so controls change as fraud does. Common patterns include messages claiming money was "sent by mistake, please return it", fake agents, stolen SIM cards and requests that trick people into approving a payment. UPI shows a control being removed because fraud kept using it. A UPI "collect request" let anyone ask you to pay; you approved it with your PIN. NPCI capped these pull requests at ₹2,000 in 2019, fraud continued, and from 1 October 2025 NPCI ended person-to-person collect requests entirely. Every person-to-person payment is now started by the payer, typically by scanning a QR code. A useful feature died because its fraud cost was higher than its value.
Why did wallets win where banks had not? Read through the lenses: distribution (agents in existing shops instead of branches), the account (a phone number instead of forms and a minimum balance), access (menus that work on the cheapest phones), price (cheap or free for the small amounts people send most), and rules (Kenya's regulators gave M-Pesa a special licence, since the banking law did not cover non-banks). The outcome was large. Suri and Jack (2016) estimated that access to M-Pesa lifted about 194,000 Kenyan households, about 2%, out of extreme poverty; a 2019 paper disputes the finding, so treat the number as contested.
The moat follows from the loop. The two agent wallets have network effects (everyone you pay is already there) and agent networks that took years to build. UPI apps have neither on their own, because the network belongs to everyone; their defence is habit, merchant relationships and the products they sell on top.
Do it
Write a payments teardown that ends in copy, adapt and avoid for a business that handles cash.
Write the decision question
For example: "How do we move cash-on-delivery customers to digital payments?" or "How should we pay riders daily?"
Trace the money for every side
Draw where cash and balances go for the payer, the payee, any agent or bank, and you. Mark where cash piles up.
List the fees and who pays them
For each step, who pays, how much, and who earns it. Find the free steps and ask who pays for them.
List trust and fraud controls
Identity checks, confirmations, limits, cooling periods, and which features were removed because of fraud.
Name the rules
Which licences and rules shape the product, and what is changing this year.
Decide and test
Copy, adapt, avoid, each with the reason, then one pilot with a metric and a guardrail.
Markdown# Teardown: mobile wallets, for Mangrove's cash-on-delivery orders Owner: Imran · Date: 15 Oct ## Decision question How do we move cash-on-delivery (COD) customers to digital payment, and should we ever build our own wallet? ## Sides and jobs (in wallets) - Sender: get money to family, fast and cheap - Receiver: get cash near home, or spend the balance - Agent: earn commission, keep enough cash and float - Operator: run the ledger, stay within the licence, stop fraud ## How money moves (facts) - M-Pesa, bKash: e-money backed 1:1 by bank trust accounts - UPI: bank to bank over NPCI; the app holds nothing - Side effect in agent wallets: cash piles up in cities, float in villages ## Fees (facts, with years) - bKash 2013: cash-in free, send flat Tk 2, cash-out 1.85% - M-Pesa since Jan 2021: KES 100 and below free; KES 101-500 costs KES 6 - UPI: no merchant fee since 2020; Sept 2026 rule allows one above Rs 2,000 - Pattern: free to put in, cheap to move, cash-out pays the agents ## Trust and fraud - ID checks at sign-up; name shown before confirming; limits - UPI ended person-to-person collect requests on 1 Oct 2025 (fraud) ## For Mangrove (21,000 COD orders a day) - Copy: payee name before confirming; receipt to both sides - Copy: rider shows a payment QR at the door - Adapt: first wallet payment waives the delivery fee - Avoid: our own wallet (licence, trust account, fraud ops) ## Test 4 weeks, 20 stores in one city: QR at the door plus fee waiver. Metric: share of COD customers who pay digitally on their next 3 orders. Guardrail: order cancellations at the door do not rise.
Bring it to your team
Ask these when a payments or payout feature is proposed.
- Where does real cash sit at each step, and who is short of it at the end of the day?
- Who pays each fee, who earns it, and who pays for the steps we make free?
- What does a person see before they confirm, and would it catch a mistyped number?
- Which licence or partner lets us hold or move this money, and what rule changes this year?
- What is the fraud cost of this feature, and what would make us switch it off?
Red flags
- "We'll build our own wallet" with no licence, trust account or fraud team in the plan.
- A payout flow where staff can change a rider's payout number with no second check.
- Success measured by sign-ups instead of repeat digital payments.
- No plan for what happens when a payment is stuck between "sent" and "received".
Practice
Trace one transfer
A worker in a city sends 2,000 (in your local currency) to her mother in a village, using an agent wallet with these prices: cash-in free; sending costs a flat 5; cash-out costs 1.85% of the amount, of which the agent keeps three quarters and the operator one quarter. The mother cashes out everything. (a) What does the whole transfer cost the family, as an amount and a percentage? (b) Who earns what? (c) Which agent ends the day with a liquidity problem, and of what kind? (d) Name two things that would let the mother keep some money in the wallet instead of cashing out, and say why the operator wants that.
- You compute the cost correctly: 5 plus 37 is 42, about 2.1%
- You split earnings: agent about 27.75, operator about 9.25 plus the 5 sending fee
- You say the village agent runs short of cash and fills up with float
- Your two ideas are places to spend the balance, and you link them to fees the operator earns or cash-out costs it avoids
Show a model answer
(a) Sending 5, cash-out 1.85% of 2,000 = 37, total 42, about 2.1% of the amount. (b) The village agent keeps about 27.75, the operator about 9.25 from cash-out plus the 5 sending fee, about 14.25. The city agent earns nothing on a free cash-in, which is why agents care about the mix of customers. (c) The village agent paid out 2,000 in notes and received 2,000 in float, so he is short of cash and long on float, and must rebalance. (d) If the village shop and the school accept the wallet, the mother can pay them directly. The operator then earns a merchant fee or keeps money in the system without paying an agent to hand out cash, and the village agent needs less cash on hand.
Make rider payouts safe
Mangrove wants to pay its 600 riders daily into their mobile wallets instead of weekly in cash. Using what wallets do, list three ways this could go wrong through fraud or mistakes, and one product control for each. Then name the metric and the guardrail you would watch in the first month.
- Your risks include at least one outside attack (such as a stolen SIM) and one inside risk (such as staff changing payout numbers)
- Each control is specific: a check, a delay, a confirmation or a limit
- At least one control borrows directly from wallets (name shown before paying, confirmations to both sides, or limits)
- Your metric and guardrail measure both success and harm
Show a model answer
1. A thief takes over a rider's SIM and changes the payout number: any change needs confirmation from the old number and the rider in person at a hub, plus a 48-hour delay before the first payout to a new number. 2. A staff member edits payout numbers to their own wallet: a maker-checker rule, so two people approve any change, with an audit log a manager reviews weekly. 3. A mistyped number pays a stranger: show the wallet's registered name to the rider in the Rider app and require them to confirm it once before payouts start. Metric: share of payouts received the same day. Guardrails: payouts sent to a wrong or changed number, and rider support tickets about missing pay, per 1,000 payouts.
Check yourself
A UPI app has the best design in the market, yet users switch to a rival app easily. Which teardown finding explains this best?
In UPI the network and the money belong to the banks and NPCI, so an app is a front end you can swap without moving money. Sending is free in every app, so fees don't explain it. UPI has no agents. Design still matters, but it can't create a switching cost on its own.
A new wallet launches in a city where an established wallet already has an agent on most streets. It offers cheaper sending. Why might it still fail?
The established wallet's moat is its agent network and the fact that everyone you pay is already on it. A small price cut doesn't make cash easier to reach or bring your family onto the new wallet. Lower prices can work, but only with a plan for agents and the people at the other end.
NPCI ended person-to-person collect requests on UPI from October 2025. What product lesson does this teach?
A 2019 limit didn't stop the scams, so the feature went. Requests from merchants and other designs can still be safe; the lesson is to weigh a feature's value against what fraud costs. PIN approval is a control, and fraud affects old systems as well as new ones.
Flashcards
Key takeaways
- In agent wallets only numbers move between people; cash stays local, so agents' liquidity is the real operations problem.
- The agent network is both the distribution and the moat, and it breaks when an agent has no cash.
- Wallets make small or first steps free and charge for cash-out, larger transfers, merchants and credit.
- UPI apps are front ends on a public network, so they compete on reach and design and earn from what they sell on top.
- Trust is designed: identity checks, names before confirming, limits, and removing features when fraud wins.
Sources and further reading
- Mobile Banking: The Impact of M-Pesa in Kenya, Isaac Mbiti and David N. Weil, NBER and University of Chicago Press, 2016
- M-Pesa, Wikipedia (2005 pilot, 2007 launch, ID checks, licence, Fuliza, Suri and Jack 2016), read October 2026
- FY25 results press release, Safaricom, 2025, and M-PESA tariff reduction, Safaricom (prices from January 2021)
- Case study: bKash, GSMA Mobile for Development, 2013, and About, bKash, read October 2026
- Customers complain of high charge: study, The Daily Star, 2018, and Cash Out charge cut, Prothom Alo, 2021
- Unified Payments Interface, Wikipedia (launch, how it works, volumes), and PhonePe tops UPI in July, Business Standard, 2025
- PhonePe FY25 revenue and loss, MediaNama, 2025, and PhonePe's updated DRHP risk factors, MediaNama, 2026
- NPCI to stop UPI P2P collect requests from Oct 1, The Week (PTI), 2025, and MDR on UPI: what it means, Business Today, 2026