Fintech · Nigeria · Product Design
💳 Fintech · B2C · Payment Infrastructure

Making Money Transfers
as Simple as Sending
a Text

Designed Paymack a money transfer and bills payment gateway that removes friction from everyday financial transactions, built for the Nigerian mobile first market.

3in1
Merchant Platform
30%
Faster Flows
B2C
Consumer Fintech
Mobile
Web + App
My Role
Lead Product Designer
Product
Paymack
Type
Fintech · B2C
Team
UX/UI · Backend Dev · QA
Tools
Figma · Maze · FigJam
01 The Problem

Sending money in Nigeria was still too complicated, too slow, and too stressful.

Despite Nigeria having a growing fintech ecosystem, most payment apps were either too complex for everyday users or too limited in what they could do. Paymack aimed to be the app that could handle transfers, bill payments, and merchant payments in one seamless interface.

The central design challenge was integrating three payment platforms into one experience without making the UI feel overwhelming while keeping every core action achievable in 3 clicks or fewer.

Three Payments. One App.
💸
Money Transfers
Bank to bank, wallet to wallet, instant and scheduled
📱
Bills Payment
Airtime, data, electricity, subscriptions in one place
🏪
Merchant Payments
QR code and link-based payments for small businesses
02 My Contribution

What I personally designed end to end

Unified
three separate payment products into a single information architecture without losing the distinct mental models users already had for each payment type
Reduced
average transaction flow from 7 steps to 4 steps through progressive disclosure and smart defaults validated in usability testing with real users
Designed
the merchant payment QR system from scratch the most novel interaction pattern in the product, requiring new mental models for both senders and receivers
03 Design Process

Understand, Define, Design and Ship

Fintech design demands an extra layer of rigour around trust, error states, and recovery flows. Every edge case in a payment flow is a potential moment of panic for the user I mapped all of them before designing the happy path.

🔍
Research
User interviews and payment audits
🎯
Define
Jobs to be done framework
✏️
Ideate
IA and flow architecture
🔨
Prototype
Hi-fi with full error states
🚀
Ship
Web + mobile delivery
04 Research Findings

What stood between users and their money

😰
Persona 1 The Anxious Sender
Regular remittance users, 25 to 45, sending money to family or paying vendors. Their biggest fear: sending to the wrong account and not being able to get it back. Every confirmation step needed to feel reassuring, not bureaucratic.
"I always double-check the name, then the number, then check again. I'm terrified of sending to the wrong person."
🏪
Persona 2 The Small Business Owner
Market traders, freelancers, and food vendors who needed to receive payments easily. Didn't want complex POS hardware. Needed a QR or link solution they could share on WhatsApp and collect payments instantly.
"My customers are always asking if I accept transfer. I need something I can show them in 2 seconds."
Trust Signal
Name Preview
Showing the recipient's full name before final confirmation reduced "wrong transfer" anxiety significantly users felt safe to proceed with confidence
Flow Win
Smart Defaults
Pre-populating frequent recipients, common bill amounts, and recently used payment methods cut average transaction time by 30% in testing
Key Insight
Receipts Matter
Users shared payment receipts on WhatsApp as proof of payment more than any other action post-transaction. Designed a shareable receipt as a first-class feature
05 Key Design Decisions

Three calls that made Paymack feel different

01
Progressive disclosure for transfers
Rather than showing all fields upfront, the transfer flow revealed fields in sequence amount first, then recipient, then confirmation. Reduced cognitive load and errors in usability testing.
02
Merchant QR with instant link fallback
QR codes work for face-to-face. But merchants also needed a shareable payment link for remote customers. Both were designed as one feature with two delivery modes.
03
Shareable receipts as social proof
Designed a receipt format specifically for WhatsApp sharing clear, branded, with all essential transaction details visible at a glance. Turned a functional screen into a viral growth loop.
06 · UI Design

Fast, trusted, and built for Nigeria.

Every screen in Paymack was designed around one principle — every user should feel in control of their money, whether they're sending ₦500 or ₦500,000.

📱 Mobile App iOS & Android · Send, receive & pay bills
P
Paymack
Smart payments for everyone
Personal
Business
Email address
dayo@gmail.com
Password
••••••••
Log In
Login
Welcome back 👋
Dayo
Available Balance
₦1,000.00
Quick Actions
💸
Send Money
📱
Airtime
⚙️
Setup
💡
Bills Payment
Recent Transactions
No recent transactions
Home Dashboard
←
Send Money
Who are you sending to?
Choose a recipient type
Myself
Transfer between your accounts
Someone Else
Send to a bank account
Amount
₦5,000
Continue
Transfer — Recipient
←
Payment Method
Choose transfer type
How would you like to pay?
🏦
Bank Transfer
From your bank account
💳
Debit Card
Visa or Mastercard
🟡
Credit Card
Pay later
Confirm Transfer
Payment Method
9:41
Transaction Receipt
✓
Transfer Successful
Transaction completed
Amount Sent
₦5,000.00
Recipient
John Adeyemi
Bank
GTBank
Reference
PAY-20240402
Share Receipt
Done
Transfer Receipt
📱 Final Screens

The app, screen by screen

Paymack's final UI — a clean, friction-free money transfer and bill payment experience built for everyday Nigerians.

Paymack Screen
Paymack Screen
Paymack Screen
Paymack Screen
Paymack Screen
Paymack Screen
07 · Reflection

What Paymack taught me about fintech design

What worked well
Trust-first design paid off
Every decision to add a confirmation step, name preview, or receipt was questioned by the dev team as "unnecessary clicks." The usability testing data proved each one reduced anxiety and increased completion rates making the case for UX as a conversion tool.
What I'd do differently
Map every error state before the happy path
We designed error states reactively. In fintech, an error during a payment is a trust-breaking moment. I'd now require a complete error state map as a deliverable before any high-fidelity design begins.
Senior level insight
Shareable receipts as growth
The shareable receipt started as a UX feature. Post-launch analysis showed it was also Paymack's most effective organic growth driver people sharing receipts introduced the app to new users passively. Design decisions can be growth strategy.
What I'd measure next
Transaction abandonment by step
With more analytics instrumentation, I'd track drop-off at each step of the transfer flow to find where anxiety or confusion is highest then redesign those specific moments first rather than the full flow.
Next Case Study
Tracka Civic Technology for Government Accountability
View Next Project →