BlinqCheckout - Payments, Settlements & Collection
Fintech | Product Design | Web | UX/UI
Merchants across Nigeria and Africa rely on digital payments to keep their businesses alive. Whether it’s a small boutique in Lagos or a growing online store in Nairobi, cash flow is often tied directly to how fast they can accept payments and receive settlements.
Our journey began with a simple, yet ambitious question:
What if paying online could feel effortless, for both customers and merchants?
Digital payments are the backbone of modern African businesses. Blinqpay provides tools that allow merchants to accept payments and track settlements across channels.
Context matters because Africa’s payment environment is complicated: fragmented bank systems, inconsistent rails, API downtime, and settlement bottlenecks affect both merchants and providers. This project set out to understand how these realities shape the daily experience of merchants who depend on Blinqpay.
African merchants face a challenging landscape. Payments fail for reasons they don’t understand. Settlement timelines shift depending on bank performance. Reconciliation becomes a daily puzzle. And the dashboards meant to help them feel more in control often deepen confusion.
Across interviews and usability reviews, one thing stood out: managing payments is harder than it should be. Merchants feel uncertain, overwhelmed, and often in the dark. A small delay in settlement can halt business operations. A failed transaction without explanation becomes a customer support nightmare.
The core problem is not just technology, it’s a combination of unclear communication, scattered information, and system-wide inconsistencies. The result is a high cognitive load placed on merchants who already manage inventory, customer service, and daily operations.
Defining Our Audience
The primary audience consists of small and medium businesses, online sellers, and operations teams who handle daily payments. Many of these users are not technical, yet they depend on accurate information to run their businesses. A reliable payment flow with real clarity around settlements has a direct impact on their cash flow and ability to deliver services. The redesigned experience focuses on supporting these groups with simple navigation, clear information, and tools that reduce the stress of managing payments in Africa’s complex financial environment.

Research Strategy
Our research combined qualitative and analytical methods to understand how merchants experience payments, settlements, and day-to-day financial operations across Nigeria and Africa. The goal was to uncover the real challenges behind slow settlements, poor visibility, unreliable dashboards, and operational bottlenecks that affect merchants using providers like Korapay, Monnify, and smaller PSPs.
Key Research Insights
Merchants don’t know which documents are required or why certain steps take long. The uncertainty feels like a black box
Many merchants assume any failed payment is a platform issue, even when it’s bank-side. Lack of clear status explanations deepens frustration.
Merchants often check their dashboards several times a day because they’re unsure when money will drop.
When money is delayed or information is unclear, merchants feel anxious. Even if the issue is caused by infrastructure or a partner bank, the merchant blames the provider.
Growing merchants struggle as volume increases
Research methodology: Our approach combined conversations with real merchants, competitive benchmarking, and ecosystem analysis to understand how payments and settlements work in practice. We spoke with merchants, finance teams, and operations leads to uncover their daily routines, pain points, and expectations.
Our team began with a simple question, how do we make day to day work easier for the merchants who rely on Blinqpay? Many of them run lean operations. They handle sales, deliveries, staff, customer complaints and accounting in the same day. Payments and settlements should not add stress on top of that.
Instead of rushing into wireframes, we brought the entire team together for a series of short collaborative workshops. Product, engineering, design and support all came in with what they had seen in the wild. Support tickets, ser messages, onboarding data, even personal notes from conversations with merchants. This mix helped us see the problem from more than one angle.
Opportunity Themes (How Might we)
Reduce friction in merchant onboarding: How might we simplify onboarding so merchants get verified and start collecting payments faster?
Build clarity and trust at key decision points: How might we help merchants understand fees, settlement, verification, and what is required of them?
Improve cross border flow experiences: How might we let merchants receive international payments with less complexity?
How might we help merchants understand their payouts, performance, and risk in a simple and intuitive way?
Once we understood the core problems merchants faced, we realised the product needed more than surface level improvements. The foundation itself needed to support clarity, consistency and long term scale.
We began by mapping every part of the merchant experience, from onboarding to payments to settlements to reporting. This helped us see which areas were overloaded, which were underdeveloped and where information naturally belonged.
We introduced an atomic design approach, starting with a clean library of tokens, colours, grids, typography and spacing. From there we built reusable components for form fields, tables, cards, status badges, alerts and navigation. Each component was tested across real merchant tasks to make sure it felt simple and dependable.

Onboarding: A clear and calm introduction to the platform
Onboarding was built to ease merchants into the platform without the stress they often face when joining a new payment provider. Instead of long forms or unclear steps, we shaped the flow into small tasks with simple explanations, real examples and a visible sense of progress. Each stage covered a key requirement like account setup, business details, document upload, bank verification and compliance checks.
Product tour
The product tour was designed to give merchants a quick, confident introduction to the platform before they settled into daily use. Instead of throwing them straight into a dense dashboard, we walked them through the core areas that matter most: how payments flow, where settlements appear and how to track activity in real time.
Dashboard: A calm starting point
The dashboard became a quick snapshot of business performance. Merchants could see recent transactions, upcoming settlements, compliance notices and urgent alerts all in one place. If something needed attention, it surfaced clearly. If everything was in order, they could keep running their business without worry.
Payments: Tools for getting paid
Payments brought all the essential money-collection tools into one place so merchants could manage everything without jumping between sections. They could create payment links, issue invoices and track every transaction with clear filters, deep search and detailed timelines. Settlements also sat within this flow because payout visibility is a major trust driver. Merchants could easily see when funds were due, what each payout contained and whether any action was needed.
Customers: A simple directory for context
This section gave merchants a clean view of customer profiles and history. It wasn’t meant to replace a CRM, just serve as a helpful reference during day to day operations.
Business Section
The Business section gave merchants clear control over how they manage and move money. The wallet served as a central hub where they could view balances, top up through a virtual account number or withdraw to any bank account. Each action came with detailed logs that showed references, recipient info and before-and-after balances.
We also added Sub Accounts so merchants could split incoming payments automatically. They could route fixed amounts or percentages to different accounts, and setup was simple: enter the bank details, choose the currency and define the split rules.
Setting & Team and Access
Merchants could add team members, assign permissions and view activity logs. It supported collaboration while protecting sensitive financial actions. This included profile updates, security, notifications, bank accounts and developer tools. Grouping them here kept the experience predictable.
By grounding the work in merchant research and real system constraints, we improved how merchants moved from sign up to getting paid. Onboarding became smoother, with fewer drop offs at verification, and merchants reached their first successful payment faster. Clearer transaction states and settlement expectations reduced confusion.
Impact and Metrics
15 to 22% increase in onboarding completion, simplified verification flows and clarifying requirements reduced abandonment during KYB and account setup, which is a common drop off point for PSPs.
20 to 28% reduction in settlement related support tickets, most PSP support volume comes from “where is my money” questions. Clear transaction states and settlement timelines reduced these queries significantly.
30% reduction in time to first successful transaction, Merchants reached activation faster once blockers were removed.
20% reduction in design to engineering clarification cycles, clearer architecture and documentation reduced back and forth during implementation.
How We Measured This
onboarding funnel analysis
support ticket categorisation
settlement and payout logs
internal retrospectives across product and engineering
merchant follow up interviews
These metrics reflect a shift from reactive problem solving to a more predictable, trust led merchant experience.











