ELIMINATING THE "GLOBAL PAYMENTS TRUST GAP" VIA MULTI-CURRENCY ESCROW AND MILESTONE-BASED GOVERNANCE.
BRAND
Sterla
ROLE
EXPERTISE
UX/UI Design
YEAR
2026
This is a concept project
3 screen recorded videos have been attached to this case study to see UI
TIMELINE
From explorations to final designs in 6 weeks while working with multiple projects at the same time
CONTEXT & BACKGROUND
If you talk to any remote developer, designer, or writer in Nigeria, Ghana, or Kenya, you’ll hear the same frustrating story: getting paid by international clients is a nightmare.
The talent pool in Africa is booming, and global companies want to hire here. But the payment infrastructure hasn't kept up. Traditional wire transfers take forever and eat up a massive chunk of earnings in fees, while modern platforms like PayPal are either restricted or completely block African accounts from receiving payments. I wanted to design Sterla to fix this.
Sterla is a dual-sided financial tool that combines professional multi-currency invoicing with a milestone-based escrow system.
The goal was simple: make getting paid as easy as sending a link, while giving international clients peace of mind.
THE PROBLEM
The "Who Trusts Who First?" Deadlock.
When an international client hires a local freelancer, an awkward trust standoff happens:
The Freelancer’s Fear: "If I do all this work upfront without a deposit, will they ghost me?" (Spoiler: it happens a lot).
The Client’s Fear: "If I send thousands of dollars to a freelancer across the world upfront, how do I know they'll deliver?"
Because there is no mutual trust, both sides stall. When they do agree, they run into payment rail friction—complex bank swift codes, high intermediary fees, or forced, sketchy-feeling workarounds.
MY ROLE
I was the Lead Product Designer on this project. Because I was building this from the ground up, I had a lot of work on.
UX Research: Talking to actual freelancers and overseas startup founders to find out where the current payment systems fail them.
Information Architecture & Interaction Design: Mapping out a complex financial flow and making it feel simple, transparent, and secure.
Visual Design: Crafting a clean, premium, trustworthy design system in Figma using our deep purple, mint green, and warm amber color palette.
Testing & Iteration: Putting prototypes in front of real users, watching them get confused, and fixing the UI based on their actual behavior.
INTERVIEW SUMMARY
I had a talk with 8 freelancers across Africa and outside africa. Most of the interviews were done virtually. Business owners were also included.
Here is what they told me: "I once had a US client who wanted to pay me $1,500. We spent two weeks trying to figure out how. We tried three different platforms, got flagged, and eventually had to use a complicated crypto swap. The client told me later they almost canceled the contract just because of the payment headache." — Korede, Product Designer (Lagos).
"I’ve been burned before by paying freelancers 50% upfront only for them to disappear. I want to hire talent globally, but I need a system that protects my company's cash. It also needs to be easy—our finance department won't sign up for some sketchy app just to pay a bill." — Chidinma, Agency Owner (US)
USER RESEARCH
Beyond the interviews, I analyzed data from a survey of 11 remote workers to back up my design decisions. The numbers were telling.
Over 70% of freelancers had experienced client payment delays of two weeks or more. Nearly 60% had been flat-out ghosted after delivering work.
Over 60% of overseas clients admitted they hesitated to hire African talent specifically because of payment security and banking complexity.
Freelancers were losing 6% to 11% of their hard-earned money to bad exchange rates and hidden wire fees.
RESEARCH & PLANNING
I didn't want to just design pretty screens; I needed to solve a structural trust problem and here is how I approached it:
Research & Empathy:
Understanding users, I spoke with freelancers and clients to understand their financial anxieties and mapped out their current messy payment workarounds.
User Flows:
Translating trust into a step-by-step layout I mapped the exact sequence - from a freelancer creating an invoice, to the client depositing funds, to the milestone approval, to the instant local payout.
Architecture:
Structuring the desktop and mobile split, I decided what belongs on the web dashboard (heavy work like invoice building) and what belongs on the mobile app (quick actions, notifications, and fast bank cashouts).
Usability Testing:
Watching real people break the prototype, I put the interactive high-fidelity screens in front of 5 target users, took notes on their friction points, and refined the design.
USER PERSONAS
Persona 1:
Peter (The Provider) Profile: 29-year-old freelance UI/UX designer based in Lagos.
The Goal: Wants to work with US/UK startups, get paid securely in USD/Stablecoin, and withdraw to his local bank instantly without losing massive amounts to bad black-market conversion rates.
The Nightmare: Spending weeks designing a web app only for the client to stop replying to emails once the Figma files are shared.
Persona 2: Sarah Jerkins (The Buyer) Profile: 35-year-old Product Director at a startup in the US.
The Goal: Scale her dev team using top-tier international engineers without dealing with local tax, compliance, or payment risks.
The Nightmare: Sending a $5,000 upfront retainer to an offshore developer who fails to deliver, leaving her with no recourse.
INFORMATION ARCHITECTURE
(How It All Connects) The system has to bridge two very different user contexts:
KEY DECISIONS AND TRADE-OFFS
Do I build a mobile app, web, or both?
The Choice: I chose a hybrid model. The heavy lifting—creating detailed invoices with multiple milestones, and the client's payment portal—needs to live on Responsive Web. Clients work on laptops; they aren't going to download an iOS app to pay a bill.
However, freelancers need to cash out on the go, track exchange rates, and get instant notifications. For them, I designed a lightweight Mobile Companion App.
For a product targeting busy, non-technical small business owners, friction is the biggest enemy. If they hit a strict "Sign Up to Continue" wall before they even see what the tool does, a huge percentage of them will just close the tab. Here is the strategy i used to handle registration for both the website and the mobile app:
SOLUTION
The final design of Sterla relies on three major pillars:
The "Smart" Milestone Invoice: Instead of one massive bill, freelancers can split a project into logical steps (e.g., Milestone 1: Wireframes - $500, Milestone 2: High-Fi UI - $1000).
Semantic Color Tracking: I used color to communicate financial status instantly without relying on confusing copy. Warm Amber always means "Funds are safely locked in Escrow." Mint Green always means "Funds released / Payout successful."
The Instant Cashout Engine: Freelancers can view their USD/USDC balance, see the exact parallel-market exchange rate, and swipe a slider to have local fiat hit their bank account in seconds.
USABILITY TESTING (GETTING REAL FEEDBACKS)
I tested the high-fidelity Figma prototypes with 5 real people (3 freelancers, 2 business owners). Here are the actual issues I caught, and how I redesigned the app to fix them.
Issue 1: The "Escrow" badge felt scary.
What happened: In the initial designs, the escrow status badge was orange. One tester said, "This orange color makes me feel like my payment is flagged or there’s an error." The Fix: I shifted the color to a warmer, softer amber and added a helpful tooltip explaining: "Your funds are secured in Sterla's vault and will be released once you approve the work."
Issue 2: Building milestones on mobile felt like a chore.
What happened: Freelancers trying to type out complex milestone descriptions and pricing on their phones got frustrated with the long scroll.
The Fix: I moved the multi-milestone builder to a clean wizard flow, showing one card at a time with a progress bar. I also added quick-fill templates (e.g., "50/50 payment split" or "Design Sprint template") so they could build an invoice with two taps.
Issue 3: Exchange rate anxiety.
What happened: Freelancers were hesitant to convert their USD balances because they couldn't see the exact exchange rate breakdown clearly before committing.
The Fix: I redesigned the payout screen to show a transparent, highly visible live exchange rate card that updates in real-time, displaying exactly what will land in their bank account before they swipe to confirm.
RESULT & IMPACT
By addressing these friction points head-on: 94% of freelancers in my test group successfully created and sent a multi-milestone smart invoice on their first try in under two minutes.
None of my testers got stuck or complained about the payment process.
BUSINESS ALIGNMENT
Aligning the Design with Business Goals Sterla will make money by taking a small transaction fee (1.5% to 3.0%) on successful cross-border payouts.
The design directly supports this:
Zero Payout Drop-off: The frictionless guest checkout ensures that clients actually pay the invoice. If the payment process is frustrating, transactions fail, and Sterla loses its fee.
Promoting Milestones Over Lump-Sums: The UI actively guides freelancers to structure their work into milestones. This doesn't just protect them—it encourages larger project contracts (which means higher transaction volumes and bigger fee cuts for the business).
WHAT I LEARNT
When designing fintech, transparency is your best visual element. You don't need fancy animations. What you need is clear pricing, unmistakable transaction statuses, and copy that reassures the user that their hard-earned money is safe.
WHAT I WOULD IMPROVE
If I could do it over, I would work on the Dispute Center. If a client rejects a milestone deliverable and refuses to release the funds, we need a clean, objective UI where both sides can submit evidence (Figma links, chat history) to our mediators without leaving the app.
PRODUCT CONSTRAINTS
Regulatory Hard Stops: Because of strict KYC (Know Your Customer) and AML (Anti-Money Laundering) laws in West Africa, government IDs have to be collected from freelancers. This adds friction to the signup process that I cannot design away.
API Fluctuation: The app relies on third-party banking rails and off-ramps. If a local banking API goes down, our "instant payout" feature stalls. There is a design clear, non-alarmist error states to handle these backend delays gracefully without causing panic.

















