Multi-Network Payment Gateway

Paycraft is a mobile-first payment platform that helps small businesses in Tanzania accept and manage payments across all major mobile money networks. I collaborated with their team to design a simple, powerful tool that makes daily transactions easier and gives business owners better control over their finances.

role

UX Research & Analysis

Wireframing & Prototyping

Design System Development

UX Research & Analysis
Wireframing & Prototyping
Design System Development

team

1 pM and 2 engineers

1 pM and 2 engineers

industry

fintech

fintech
problem

Business owners had no tools to track payments o

Business owners had no tools to track payments o

Business owners had no tools to track payments o

Most relied on mobile paybill numbers but lacked tools to track performance, manage revenue, or even send flexible payment links. Business owners had little visibility into their income and couldn’t offer customers modern, seamless payment experiences.

my process

Designing for both patients and hospitals

Designing for both patients and hospitals

Designing for both patients and hospitals

I started by talking to real users—freelancers, shop owners, and small business admins to understand how they handled payments. I mapped out their workflows, documented pain points, and studied how mobile money is used day-to-day. These insights guided the product strategy and helped define what the MVP needed to solve from day one.

user challenges

What users told us and what it meant

What users told us and what it meant

What users told us and what it meant

After interviewing 12 business owners and freelancers, I uncovered three major themes:

  • They had no way to track payments across different networks.

  • Customers wanted to pay however was most convenient with their current mobile carrier.

  • Most users had never used tools beyond basic mobile money apps, so simplicity was key.

user personas

Understanding the users

Understanding the users

Understanding the users

We designed for a single, focused persona: A small business owner juggling sales, customers, and cash flow someone who needed simple tools to get paid fast and see where the money was going. This persona guided everything from screen layout to the wording of key actions.

ideation

Designing for everyday business owners

Designing for everyday business owners

Designing for everyday business owners

With clear user needs in mind, I shaped a feature set that made everyday transactions faster and more flexible

  • One-click payment links

  • Integration with all major mobile networks

  • Real-time reporting

  • Auto-saved contacts for repeat payments


I also made sure the most important tasks sending and receiving money were always just two taps away.

information architecture

A structure built for speed and clarity

A structure built for speed and clarity

A structure built for speed and clarity

To translate user needs into actionable flows, I created the information architecture for both business owners and end customers.

  • Business dashboard IA prioritized key actions: send/receive payments, generate links, and view analytics all accessible from the homepage.

  • Payment recipient flows were kept minimal and responsive to accommodate mobile users with limited data access.

brand identity

Designed for the business owner

Designed for the business owner

Designed for the business owner

I created a visual identity system that felt approachable and reliable just like the businesses we designed for. From color choices to button styles, every element reinforced clarity, trust, and ease of use.

design execution

Built for merchants collecting payments across networks

Built for merchants collecting payments across networks

Built for merchants collecting payments across networks

The dashboard focused on what business owners do most: send money, request payments, and check transactions. I also designed a slimmed-down mobile flow for customers, keeping it data-light and easy to use—even on older phones or patchy networks.

user feedback

Real-world testing shaped key product pivots

Real-world testing shaped key product pivots

Real-world testing shaped key product pivots

Throughout the design process, we partnered closely with hospitals to ensure the solution reflected real-world needs.

Here’s how user feedback shaped a key feature:

  • Many hospitals preferred assigning patient numbers instead of time slots.

  • This preference came from the unpredictability of doctors' schedules—numbers gave them more flexibility.

In response, I introduced a dual-mode option: hospitals can now choose between time-based appointments or number-based queues. This change gave hospitals more control and aligned the system with how they actually work.

Let’s build

something great

Let’s build

something great

Let’s build

something great

Let’s build

something great