myPay Quick Split UX Design
Henryjr. Osuji
Like this project
Posted Dec 5, 2025
Designed the 'Quick Split' feature for myPay, enhancing user experience and transaction security.
Case Study: Designing the myPay “Quick Split” Flow
The Challenge: Bridging Chat and Finance
myPay’s vision is ambitious: to be a secure, chat-first financial ecosystem for the UK market. The core philosophy is to make financial transactions feel as simple and intuitive as sending a text message
The task was to design the “Quick Split” flow — a high-frequency social action — while adhering to two non-negotiable mandates:
Minimal Steps: No transaction should require more than 3 to 4 taps
Trust by Design: Financial clarity and security must be paramount
In short: How do we build a quick-tap shortcut without compromising financial security?
Solution Phase 1: The Home Screen Shortcut
The core mandate was speed: to deliver the entire “Quick Split” flow in 3 to 4 taps maximum. To meet this aggressive Minimal Steps requirement, we strategically had to elevate the initiation step, moving it directly onto the Home Screen instead of burying it in secondary menus.
Tapping a friend immediately starts the transaction flow. This is the crucial first step needed to keep the total tap count low.
Solution Phase 2: The Chat-FinTech Hybrid (Ensuring Trust)
The “chat-first” mandate required the transaction interface to feel conversational, but financial accuracy demanded structure. This created a critical trade-off — a design choice directly driven by the Trust by Design mandate.
The Trade-Off: Structure Over Flexibility
Instead of a free-form chat window, the design uses a Hybrid Interface
Aesthetic: The screen uses a familiar chat header and background (maintaining the brand).
Structure: The input area forces the user to fill in separate, defined fields for Amount and Message/Reason.
Rationale: I overrode the flexibility of chat to guarantee data accuracy. It is impossible to send a request without a valid, system-readable amount. This prevents transaction errors and upholds the Trust by Design mandate
The Result: The Transaction Card (Unambiguous Receipt)
Once sent, the request appears not as plain text, but as a Structured Request Card within the chat history.
This card serves as an unambiguous receipt for the sender, clearly displaying the Amount, Purpose, and Status (“Pending”). This constant visual confirmation is key to building user confidence post-transaction.
It is impossible to send a request without a valid, system-readable amount.
This card serves as an unambiguous receipt for the sender, clearly displaying the Amount, Purpose, and Status (“Pending”).
Conclusion: Fostering a Social Financial Ecosystem
The true strategic win for the “Quick Split” flow is how it helps myPay grow its social network. By making the transaction process incredibly fast to hit the Minimal Steps rule, I created a smooth system that users want to use for even the smallest debts.
This encourages friends to share money more often. The Structured Request Card then backs up these frequent social transactions by making them safe and clear, boosting trust and making friendship groups use the app more. Ultimately, this design turns a simple bill-splitting feature into the main engine for myPay’s social and financial growth.