Often, recovery leaves the app altogether. When the phone that holds a customer’s banking app and receives their codes can’t be trusted, they need another way to reach help: another device, a person, a phone line or a branch. That path decides whether they trust you again, so it deserves as much design attention as the everyday journey.
Why is a compromised phone so hard to recover from?
Because so much of the product assumes the phone is available, trusted and in the customer’s hands alone.
The phone receives verification codes. It stores the ways a customer proves who they are. It holds the app, and it’s where you send them for help. Lose control of it, and every one of those routes goes with it.
The idea that one phone means one person is shaky to begin with. IPA’s 2025 survey of digital finance users in Kenya (opens in a new tab) found that one in three people with a PIN or password on their phone said someone else knew it, usually a partner or someone in their household. One in ten used a SIM card registered in someone else’s name.
What does recovery involve beyond the app?
Support channels, operational processes, identity checks and clear communication, as well as the interface.
Customers feel the gaps there. The same survey found that a quarter of people had struggled to reach customer care when they needed it. Among people who lost money and asked for help, 36% spent their own money trying to resolve it, on airtime or travel. And people were less confident in their provider’s ability to help them resolve a problem than in its ability to keep their money safe from fraud.
How it ends matters. Of the people who asked for help, 31% of those unhappy with the outcome switched provider or used digital finance less, against 10% of those who were satisfied.
What should you look at in your own recovery?
The moments when your normal assumptions stop being true. A smooth everyday journey says little about recovery: the phone may be gone, and the customer may be stressed, far from home or using someone else’s device.
Your own data and support logs can show where recovery breaks:
- How many recovery attempts start in the app and finish somewhere else: a call, a branch, an agent?
- How long does it take a customer without their phone to stop money leaving their account?
- What happens to customers in the months after an incident? Do they come back?
A question for your next roadmap review: if a customer lost their phone tonight, how would they reach you, and how would you know it’s them? It’s one of the assumptions that break in emerging markets: one person, three users, one day.
Other questions we hear
What should a customer be able to do without their phone?
Reach you through a channel they know is genuine, report what happened, protect their accounts and find out what happens next, all without the phone that was lost, stolen or taken over.
How do you verify a customer’s identity when their usual device can’t be trusted?
The specifics depend on the product and its risk model. The design principle is the same: have a route that doesn’t depend on the compromised device, that a stressed customer can understand, and that still protects their identity and funds.
Why should product teams own recovery, not only security?
Because customers judge a financial product by how it treats them on their worst day as well as their best. Security work prevents incidents. The recovery experience decides whether someone trusts you again after one.
Sources
- Innovations for Poverty Action (2025). Financial Consumer Protection Survey: Kenya 2025 (opens in a new tab)

