A full UPI product built on BlackBuck’s wallet — familiar enough for everyday payments, considered enough for the edge cases.
BlackBuck’s fleet operators already use apps like GPay and PhonePe. Opening the wallet to UPI meant meeting those expectations while working with different balances, limits and technical constraints. M2P’s headless SDK handled the infrastructure; BlackBuck owned the experience.
The brief was to add UPI to the existing wallet. The harder question was how to make a technically different system feel familiar — especially when money is pending, a mandate fails or a user needs to stop an autopay.
The initial proposal showed FASTag, UPI and combined balances. At the moment of payment, that raised a question: which money can I actually use? I showed only the UPI balance on the payments screen, and surfaced the combined wallet limit contextually during recharge.
Before designing the history screen, I mapped transaction patterns across GPay, PhonePe and Paytm. Each card needed to answer what happened without a second tap: status, direction, amount and counterparty. Secondary detail stays one tap away.
Autopay is a trust decision. Mandate decline, timeout, insufficient balance and a failed pause or cancellation are different situations. I designed a distinct response for each, and kept pause, resume and cancel visible so users could stay in control.
The initial release assumed a high-intent user who had already worked to gain access. When access broadened, that onboarding tone carried too much implicit context. Next time, I would design the gated and open onboarding experiences in parallel, so the wider release is ready from the start.