Case Study
2026
MaxPay: Safer Bulk Transfers
and Scheduled Payments
A business-payment concept that helps Nigerian small businesses send bulk transfers, schedule recurring payments, and recover safely from failed or delayed transactions.
Role
Product Designer
Duration
8 weeks
Tools
Figma, Miro, Notion, Maze

01
Overview
Reducing manual effort and payment risk
for Nigerian small businesses
Small-business owners regularly pay employees, suppliers, landlords, and service providers under time pressure. Repeating transfers manually increases effort and raises the risk of incorrect payments. MaxPay combines bulk transfers and scheduled payments with row-level validation, transparent fees, secure confirmation, and clear recovery actions.
02
Problem Statement
Problem Statement
Business owners often repeat manual transfers when paying multiple people. One wrong account detail or delayed payment can disrupt the entire batch, with limited ways to fix individual issues.
Recurring payments such as rent, salaries, and subscriptions also rely on manual reminders, creating a risk of missed payments or insufficient funds.
Research on Moniepoint Business, Nomba, and Kuda Business revealed common needs: reliable processing, clear payment status, visible charges, less repetitive entry, and easy recovery when payments fail. These became core requirements for the product.
03
Solution Provided
Solution Provided
MaxPay simplifies bulk payments while keeping users informed and in control. Users can upload a CSV file or add recipients manually, while the system checks each entry for missing information, invalid account details, duplicates, and account-name mismatches.
Before confirming, users review the recipients, total amount, fees, source account, and any rows requiring attention. After secure authentication, the results screen clearly shows the status of each payment and the safest action to take next.
04
Target Users
Three archetypes, one underlying need
1
The small-business owner
Pays several employees or suppliers at the end of the day or month, in a single batch.
2
The merchant or agent
Makes repeated transfers throughout the day while managing customer payments under time pressure.
3
The freelancer or small-team operator
Schedules rent, subscriptions, payroll, and recurring expenses that must not be forgotten.
All three share the same underlying need: confidence that money will move correctly, and clarity the moment it does not.
05
Research
Research
I conducted secondary research by reviewing a focused sample of Google Play feedback for Moniepoint Business, Nomba, and Kuda Business. I treated the reviews as directional signals because they covered different app versions and user contexts. Common concerns included delayed payments, unclear charges, repeated verification, weak transaction search, network errors, account restrictions, and difficult support access.
Research collection was supported by Manus AI. Research interpretation, product direction, user flows, interaction design, and interface design were completed independently.
What I learned
Payment failure was only part of the problem. The deeper issue was uncertainty: users could not always tell whether money had moved, whether they had been charged, or what action was safe to take next.

06
Design Decisions
From research to design response
Each decision trades a small amount of speed for a meaningful reduction in risk or confusion.

How the design supports the business
Saved lists and schedules encourage repeat use
✓
Clear statuses can reduce avoidable support requests
✓
Visible fees support reconciliation
✓
Row-level recovery prevents duplicate payments


07
User Flow
User Flow: Bulk Transfer
The flow branches at two points where a single path would hide risk: validating recipients before anything is sent, and interpreting batch results once payments have processed.

08
Wireframes
Results screen logic
The results screen is designed to answer four questions immediately:
View in Figma
1
Did the batch go through?
2
Which recipients were paid?
3
Which payments need attention?
4
What can I do next without creating a duplicate payment?









Why the layout is organised this way
1. Overall batch outcome
2. Successful, processing, and failed counts
3. Amount and fee summary
4. "Do not resend" warning
5. Status filter tabs
6. Row-level recovery actions
7. Download report and retry-failed actions


09
Error States
Error States and Recovery Messaging
Every failure state names what happened, whether the user's money moved, and what to do next — instead of showing a generic error.

10
Scheduled Payments
Scheduled Payments
Scheduled payments show the recipient, amount, frequency, next payment date, fee, source account, and insufficient-balance conditions. Each execution is marked as upcoming, processing, successful, failed, skipped, or paused. MaxPay explains why a payment was not sent and never retries automatically without informing the user.
11
Constraints
Constraints I Designed Around
The constraints
Payment-network responses may be delayed
Account verification may depend on external services
Compliance controls may restrict transactions
Unstable connections can make payment status uncertain
Led to
Status timelines
Row-level validation
Safe retry guidance
Support cases that preserve transaction details
12
Next Steps
What I Would Validate Next
Test tasks
T1
Correct invalid and duplicate recipient rows
T2
Interpret mixed payment results without resending successful payments
T3
Respond to an insufficient-balance warning on a scheduled payment
Proposed measures
Duplicate-submission rate
Time to identify failed rows
Valid-batch completion rate
Time to find receipts
Payment-status support requests
13
Reflection
Reflection
The biggest change in my thinking was moving from "How can I make bulk transfers faster?" to "How can I make bulk transfers safe to understand?" The research showed that financial products are judged most harshly when something becomes uncertain: the payment may be delayed, the account may be restricted, the fee may be unclear, support may not respond. In those moments, a polished interface is not enough.
For MaxPay, the most important design decision was to make recovery part of the main experience. The product does not assume every payment will succeed immediately. Instead, it helps the user understand the result, avoid a duplicate action, and move toward resolution. That is the difference between designing a screen that sends money and designing a product that people can trust with business money.
References
[1]
Moniepoint Business Banking
— Google Play (accessed September 2026)
[2]
Nomba – Mobile Banking
— Google Play (accessed September 2026)
[3]
Kuda Business Banking App
— Google Play (accessed September 2026)
Interested in connecting?
Let's talk projects, collaborations, or anything design!
Book a call
Tope Olorunfemi
Product Designer

