Blinqpay - Payment gateway, Widget

Designing a Trusted, Localised Payment Experience for African Markets

Designing a Trusted, Localised Payment Experience for African Markets

Product Design | Web | UX/UI | Widgets

UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech

CONTENT

Introduction

Introduction

Introduction

Overview

Overview

Overview

Problem

Problem

Problem

Users and Audience

Users and Audience

Users and Audience

Scope and Constraints

Scope and Constraints

Scope and Constraints

Process and What You Did

Process and What You Did

Process and What You Did

Design Outcome

Design Outcome

Design Outcome

INTRODUCTION

INTRODUCTION

INTRODUCTION

In Africa’s rapidly growing digital economy, businesses are scaling online, but friction at checkout continues to cost them revenue. Customers frequently abandon transactions due to limited payment options, confusing flows, or unbranded pages that fail to inspire confidence.

As the Lead Product Designer on Blinqpay Checkout, I was responsible for designing a localised, multi-payment experience that helps African businesses and customers increase conversion and build trust at the point of payment. My role was to design a checkout that not only integrates multiple gateways seamlessly but that reflects how customers in Nigerian and broader African markets actually pay.

The goal was to create an experience that is reliable, intuitive, and builds trust for both users and merchants, while simplifying the operational complexity for businesses managing multiple payment methods.

Year

2025

Year

2025

Year

2025

Industry

Fintech

Industry

Fintech

Industry

Fintech

Role

Lead designer

Role

Lead designer

Role

Lead designer

Contributors

1 Product Manager and 3 Software Engineers

Contributors

1 Product Manager and 3 Software Engineers

Contributors

1 Product Manager and 3 Software Engineers

View Live Product

View Live Product

View Live Product

OVERVIEW

OVERVIEW

OVERVIEW

Blinqpay Checkout is a payment layer that lets African businesses accept digital payments across multiple gateways and methods. It simplifies complex integrations into a single, reliable flow.

The goal was to design a checkout that matches local payment habits, reduces failed transactions, and builds trust for customers and merchants. In Africa, users mix bank transfers, mobile money, USSD, and cards based on reliability and urgency, making a localised experience essential. For merchants, a smooth checkout protects revenue, reduces support load, and reinforces brand trust.

Hands counting euro banknotes and dollar banknotes
Hands counting euro banknotes and dollar banknotes
Hands counting euro banknotes and dollar banknotes

PROBLEM & GOAL

PROBLEM & GOAL

PROBLEM & GOAL

When I dug into the checkout experience across multiple African merchants, it became clear that the core issue wasn’t just technology, it was trust and clarity. Customers were abandoning payments for a few key reasons: payment failures, OTP friction, confusing confirmation messages, and a lack of payment options they actually preferred.

Existing checkout solutions were built for infrastructure, not the local user. They assumed users would follow card-first flows and accept opaque “pending” statuses, which didn’t match how Nigerian and broader African users behave. Users needed reassurance, choice, and a seamless path to completing their payment otherwise, they’d drop off.

The goal

The goal with Blinqpay Checkout was to solve this. I aimed to design a checkout experience that reduced friction, reflected real-world payment behaviour, and gave both users and merchants confidence that payments would succeed and be transparent.

a person holding a credit card and a cell phone
a person holding a credit card and a cell phone
a person holding a credit card and a cell phone

USERS AND AUDIENCE

USERS AND AUDIENCE

USERS AND AUDIENCE

Users & Audience

We designed Blinqpay Checkout for three main groups: everyday mobile consumers who need clarity and trust, small and medium businesses managing multiple payment methods, and digital merchants across Africa seeking transaction visibility and easy reconciliation. Research showed Nigerian users prefer bank transfers or mobile money, are sensitive to unclear confirmations, and drop off at small friction points.

SCOPE & CONSTRAINTS

SCOPE & CONSTRAINTS

SCOPE & CONSTRAINTS

For Blinqpay Checkout, we focused on the parts of the experience we could directly influence:

In scope

  • Designing the end-to-end checkout flow, including payment method selection.

  • Defining clear confirmation and status states for payments.

  • Creating error handling and fallback flows for failed or pending payments.

  • Incorporating trust signals and reassurance messaging to improve user confidence.

Constraints we had to work within

  • Regulatory requirements around KYC and payment processing that shaped what could be automated.

  • Limitations of third-party gateways, including inconsistent responses and OTP delays.

  • Variable network reliability and low-bandwidth environments that affected mobile users.

  • Dependency on external providers for transaction confirmation, meaning the design had to account for uncertainty rather than assume perfect conditions.

WHAT WE DID

WHAT WE DID

WHAT WE DID

Process
  • Conducted merchant interviews and analysed support tickets
  • Audited competitor African gateways

  • Mapped user flows to identify friction points

Key insights: Users abandon when uncertain, not just on failure; bank transfers/mobile money are trusted; merchants value clarity and traceability.

Design decisions: Payment-method-first flows, human-readable statuses, fallback flows for failures, prioritisation of local methods, reduced steps and interruptions.

FINAL DESIGN

FINAL DESIGN

FINAL DESIGN

Mobile money

The Mobile Money Payment Method lets customers in supported African countries pay via their mobile money operators. At checkout, users select Mobile Money, enter their phone number, and authorise payment on their device. After confirming, the system shows success or failure. Sessions timeout after 10 minutes if not completed.

UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech
Mobile Responsivenes UI/UX fintech
Mobile Responsivenes UI/UX fintech
Mobile Responsivenes UI/UX fintech
Card Payment

The Pay With Card option lets customers pay using a debit or credit card. At checkout, users enter their contact details, card number, expiry date, and CVV, then click “Pay.” They authenticate the transaction by entering an OTP sent to their phone

UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech
Mobile Responsivenes UI/UX fintech
Mobile Responsivenes UI/UX fintech
Mobile Responsivenes UI/UX fintech
Pay with Bank transfer

The Pay With Bank Transfer method lets customers pay by direct transfer. At checkout, users enter their contact details, select the option, view a one-time bank account and amount, then transfer the exact sum and confirm by clicking “I have made Payment.”

UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech
UI/UX Dashboard Design/ Fintech
Mobile Responsivenes UI/UX fintech
Mobile Responsivenes UI/UX fintech
Mobile Responsivenes UI/UX fintech
Outcomes

The final Blinqpay Checkout experience delivered a clearer, more trustworthy payment flow for both users and merchants.

For users, the checkout reduced confusion and anxiety by making payment states explicit and guiding them through failures instead of leaving them at dead ends. Prioritising locally trusted payment methods helped users complete transactions with more confidence, especially on mobile.

For merchants, the experience improved visibility into transaction outcomes and reduced the guesswork around pending and failed payments.

Lessons Learned

This project reinforced a few key lessons for me as a product designer:

  • In payments, clarity beats speed. Users prefer slower but transparent flows over fast, opaque ones.

  • Designing for African markets means designing for uncertainty, including network instability and delayed confirmations.

  • Payment failure is not an edge case, it is a core user journey that must be intentionally designed.

  • Checkout is not a single screen, it is a system that spans users, merchants, and third-party infrastructure.

Create a free website with Framer, the website builder loved by startups, designers and agencies.