15mins
Simple UX That Drives Customer Trust to Opay Over Commercial Banks, Every Single Time.
Tools Used
Opay has earned customer trust through a simple but intentional user experience (UX) decision, one that commercial banks in Nigeria often overlook. This case study explores how a small yet powerful feature in Opay’s transfer flow builds user confidence and reduces friction, while traditional banks continue to suffer the consequences of not addressing the same pain point.
I’ll be using Wema Bank as a reference point - not because they failed, but because they almost nailed it - and in doing so, they reveal just how close commercial banks are to closing the trust gap, if only they pay closer attention to the right details.
Industry:
Banking & Finance
Project Duration:
4 days
My Role:
Product Design
Team:
Alone
The Problem
In Nigeria today, a failed transfer can do more than delay money - it can create tension, distrust, and unnecessary embarrassment.
A prospective Corp member shared how, just hours before leaving camp experienced a failed transfer to a trader which caused anxiety and blame. The trader, using Opay, assumed the sender’s commercial bank was at fault simply because the transaction hadn’t yet reflected. The user was left feeling rushed and helpless.
Or consider a traveler trying to buy food en route, only for their payment to remain stuck in "pending" status. These aren’t edge cases, they’re everyday pain points.
The Solution
Introduce real-time recipient bank status alerts into the transfer flow of commercial banks. This gives users foresight and agency - reducing failed transfers, guesswork, and reconciliation friction.
It’s a feature Opay already nails. And it’s one that users have come to trust without even realizing it.
Design Process
Strategy: Double Diamond Framework
Discover
Research was conducted through:
5 physical interviews with everyday Opay and commercial bank users
30+ Twitter/X comments expressing frustration over failed transfers and delays
Competitor benchmarking, with a focus on Opay’s mobile-first experience
During this research, I encountered repeated pain points:
Receipts that take too long to reflect
Users being blamed for what is often a systemic failure
Anxiety, embarrassment, and hesitation in making simple financial transactions
One traveler couldn’t buy food during a stop because their transfer wouldn’t go through.
Another Corp member shared how a failed transaction to a trader - just hours before leaving NYSC camp - triggered panic. The trader, using Opay as the recipient bank, instantly assumed the sender's commercial bank was at fault.
These real-life situations revealed one truth: pre-transfer transparency is a user need, not a luxury.
Interestingly, Alat by Wema Bank already includes a feature that allows users to manually check the recipient bank's network reliability from a list view - a step in the right direction.
Opay have same feature;
But Opay took it further - and smarter.
Instead of expecting users to check manually, Opay automatically detects the recipient bank’s network status during the transfer flow, and surfaces that status clearly before the user hits “Send/Confirm.”
This subtle design choice signals that Opay:
✅ understands user behaviour
✅ respects their attention and time
✅ values emotional trust in digital money movement
Define
Most commercial bank apps (e.g., Wema, Access, UBA) only inform users after the transfer fails - usually after funds are already deducted, forcing the user into a stressful waiting or refund process.
Refined Problem:
How might we surface the recipient bank’s real-time operational status before confirming a transaction, to provide users with the same trust Opay has mastered?
Develop
With a clearly defined problem, the next step was to design a system that inserts recipient bank status feedback into Wema Bank’s existing transfer flow - in a way that’s non-intrusive, intuitive, and trust-evoking.
Opay’s flow served as a benchmark for efficiency and clarity.
I mapped the ideal placement for status feedback within the bank transfer experience - choosing interaction points where users naturally pause or make decisions.
Design Goals:
Maintain the user flow rhythm familiar to Wema Bank customers
Use minimal UI weight - no clutter, just clarity
Respect the Wema brand, but elevate trust-building through copy and feedback tone
Key UX Explorations:
Conditional modals, triggered only if the recipient bank is unstable
Alert messages strategically embedded within the transaction flow
Fallback suggestions (e.g., cancel or continue)
Deliver
The final solution was designed in a mobile-first prototype inspired by Alat by Wema Bank - integrating the new feature into its native experience.
It was tested on two common scenarios:
Sending to a bank experiencing downtime
Sending to a flagged recipient account
Outcomes:
Users understood the warning message instantly
Many chose to delay transfers when flagged
Several said they felt more respected and “in control”
One quote stood out:
“This is what I expect from Opay. Seeing it in Wema felt like a game changer.”
The design was delivered as a mobile-first clickable prototype - showing how it can be layered into existing bank flows with minimal disruption.
This isn’t a reinvention. It’s a simple insertion of empathy - exactly where users need it most.
Reflection & Impact
Area | Result |
|---|---|
User Trust | Users feel informed and in control |
Experience Clarity | Less stress, fewer failed transaction complaints |
Brand Perception | Commercial banks seen as proactive, not reactive |
UX Predictability | Confidence in sensitive financial moments |
“Opay just gets it. When a bank network is misbehaving, they tell you before you get embarrassed.”
- User complains during failed airtime purchase
Summary
In digital banking, trust isn’t built after the transaction - it’s built before the user taps “Send.”
This case study shows how Opay has gained near-default trust in Nigeria’s financial space by focusing on small UX decisions with big emotional impact. And how commercial banks like Wema can close that gap without needing a full redesign.
Because sometimes, the most powerful UX is the one that saves users from saying: “I shouldn’t have sent that.”
Final Prototype
Here's an interactive prototype for the bank network service downtime
