Selected work02 / CASE STUDY

FairMoney / 2025

A phone number became a bank account.

Banking access at customer scale

For more than 10 million customers, the most memorable identifier was already in their pocket. The product opportunity was to make a registered phone number usable as an account number without making the transfer journey feel unfamiliar.

RoleSenior Android Developer
Reach10M+ customers
PlatformKotlin Multiplatform
Team26-member Android organisation
ABOUT THIS CASE STUDY

This account stays at the product and system level to respect customer, employer, and platform confidentiality.

01
THE PRODUCT

Use the identifier people already remember.

The Phone Number as Account Number feature allowed customers to receive transfers through the mobile number registered to their account. My work focused on implementing the feature with Kotlin Multiplatform so the underlying rules could be shared and maintained deliberately.

02
THE FRICTION

Reduce the number of decisions in a transfer.

I also built an account-number-based bank suggestion algorithm. Instead of asking customers to resolve every routing detail themselves, the experience could use the information already entered to improve bank selection accuracy and make the flow feel more direct.

03
THE ARCHITECTURE

Shared logic only pays off when ownership is clear.

The feature lived alongside shared KMP modules maintained by a large Android team. The engineering challenge was not simply reuse; it was keeping business logic testable, platform boundaries understandable, and future changes less likely to produce client-specific defects.

ENGINEERING PRINCIPLES

What guided the work.

  1. 01Start with the customer's existing mental model.
  2. 02Use shared logic to reduce behavioural drift, not to erase platform needs.
  3. 03Automate an avoidable decision when the input already contains the answer.
OUTCOME

A transfer capability designed for more than 10 million customers, combining a memorable account identifier with shared KMP logic and smarter bank suggestion.

NEXTOne codebase, many devices