Grace Ikpang

Product Designer · 3+ years designing experiences

Abuja ·

Product design · Payments & logistics

KIPA

Helping people pay with confidence and manage everyday deliveries in one app.

Role
Product designer
Timeline
4 months
Platform
Mobile
Status
Live
Three KIPA app screens: the home screen with an available balance, the KIPA splash screen, and an errand request with a delivery route.

In short

Buying from strangers on social media in Nigeria often means paying first and hoping the item arrives. KIPA holds the payment in Kipa Protect until the buyer confirms delivery, and adds rider booking for errands and deliveries in the same app.

I designed the mobile experience around one idea: people should know where their money stands, not have to guess. That meant making every stage of a protected payment explicit, from confirming before paying, to a visible window before funds are released, to a dispute path that freezes the money straight away. KIPA launched in August 2026.

The problem

Paying first, and hoping it arrives

This project started with complaints. Our client had collected social media posts from people across the board who had been scammed by online vendors. The client had been through it too, and so had I: I once lost ₦40,000 trying to buy a pair of jeans online.

Public data shows how common this is. In Visa’s 2026 Stay Secure study, 51% of consumers in Nigeria said they had experienced a financial scam in the past 12 months, and 57% of them said it happened on social media, the same place 83% had bought products directly.

The trust problem runs both ways. Buyers need confidence that their order will arrive as described. Sellers need to know when they will be paid. Arranging delivery adds another layer of coordination.

51%

of consumers in Nigeria reported a financial scam in the past 12 months, most often on social media.

Visa Stay Secure study, 2026

Approach

Designing for the moments of doubt

The client was on a short timeline, so we worked from what we already had: the complaints, our own experiences, and a review of existing escrow applications. Escrow wasn’t new in Nigeria, services like Vesicash already offered it, but buying through social media still meant paying a stranger first.

I approached the experience through two starting points: someone who wants to transact and someone who needs something picked up or delivered. Separating those intentions gave the flows a clearer purpose. For the payment journey, I brainstormed with stakeholders around the moments where doubt builds:

  • What does the buyer need to know before paying?
  • What does the seller need to know while waiting?
  • What happens when delivery is complete, or when something is wrong?

We set the escrow rules together, and I designed how each one is shown, explained and confirmed. I worked with the product lead and engineers over 4 months.

People should know where their money stands, not have to guess.

Decision 1

Confirm before the money moves

Scams start with paying first, so the buyer’s screens focus on what happens before money leaves their account. Opening a payment link shows the item, the fee and the total together, the seller’s details with a way to call them, and how long the seller has to dispatch. If the item isn’t sent in time, the buyer is refunded.

Before paying, the buyer confirms two things: that the item description is what they are ordering, and that the funds will be held in Kipa Protect until they confirm delivery. Reassuring copy alone isn’t enough when someone is deciding whether to commit money, so the rules become part of the action.

The buyer’s screens: pasting a payment link, the transaction status with the item, fee and total, and the payment screen with the seller’s details, the processing time and two confirmations before paying.

Decision 2

One timeline both sides can read

Sellers had the opposite worry: when will I be paid? The seller creates a payment link with the rules up front, including that funds are held until delivery is verified and that dispute windows apply after delivery. Then they follow the same transaction timeline as the buyer: link created, payment received with funds in Kipa Protect, rider booked, item picked up.

Once paid, the seller sees exactly what they will receive and a processing window: a maximum of 3 days to send the package, or the money is refunded to the buyer automatically. Both sides read the same state, so neither has to message the other to find out where things stand.

The seller’s screens: creating a payment link with the important rules up front, the link created and ready to share, and the transaction status with the amount received, the 3 day processing window and the shared timeline.

Decision 3

Make releasing and disputing clearly different

Confirming delivery and opening a dispute carry very different consequences, so they needed to look and feel different. After delivery, the seller sees a dispute window counting down: the buyer has 1 hour to raise a problem before funds are released automatically. If the buyer releases early, a final check tells them the release is irreversible.

Opening a dispute does the opposite. It freezes the funds in Kipa Protect straight away and starts an investigation, and the dispute stays visible next to live chat and call support.

Three steps of a protected payment. 01, Protection you can see: the item, fees and total stay together. 02, Delivered, with time to review: delivery status and the dispute window, in view. 03, A deliberate release: a final check before the buyer releases payment.
The dispute screens: opening a dispute with a notice that funds will be frozen, a reason and a description, and the support screen with live chat, calling and the active dispute.

Decision 4

Keep errands just as visible

Errands have a simpler job: request a rider and follow the task. From the home screen, people can request riders for deliveries, pickups and errands. Once a rider is assigned, they see who is coming, when they will arrive and the delivery route, so the request stays connected to what is happening beyond the screen.

The result

Live since August 2026

KIPA launched on the App Store and Google Play in August 2026. It’s early, and the first App Store reviews are short; one user wrote that it “makes buying and selling so easy and comfortable.”

What I’d measure next: how many transactions end in a dispute, how quickly disputes are resolved, and how long buyers take to release funds after delivery.

What I’d do differently

Trust is built through understandable states and clear consequences. A polished payment screen matters, but the explanation before a commitment and the feedback after it matter just as much.

With more time, I would have tested with real buyers and sellers before launch; the short timeline meant we relied on complaints and our own experience. Next, I would check whether people can explain the payment status in their own words, and whether the release and dispute paths are easy to tell apart when a delivery goes wrong.