1. Designing for Trust, Not Just Usability
At Karla, a tap-to-pay fintech designed to simplify merchant payments across Africa, we quickly realized that users weren’t judging us by how innovative we were; they judged us by how safe they felt.
During our early campaigns, especially live demos at events and parties, we saw how friction could kill excitement. People wanted to try Karla instantly, but our onboarding took too long. Multiple forms, ID verification steps, and vague loading states led to over 60% drop‑offs.
So we redesign everything around momentum and trust. Onboarding was reduced to three steps, with real‑time feedback and human microcopy guiding users through each action.
After launch, onboarding completion jumped to 85% and repeat usage grew by 40%. It proved a simple truth: in fintech, trust isn’t only about security, it’s about how confidently users move through each step.
2. Working Around Infrastructure Gaps
Designing for the African fintech user means designing with a range of infrastructural gaps in mind, such as low‑bandwidth connections, poor electricity supply, and devices that could be five years old. Leading design at HostFi (a crypto app that allows users to save, invest, and settle transactions using stablecoins), I quickly learnt that the startups that solve these challenges for everyday users win and retain users more than startups that do not.
So we reimagined onboarding from the ground up. Instead of forcing users through a complex sign‑up process, we let them create an account with just an email address, no waiting, no forms, no photo uploads. The goal was to get users into the product instantly, even on weak networks. From there, they could deposit fiat or crypto to explore how the platform worked, with every action cached locally in case of disconnection.
But to ensure security and compliance, we designed a tiered KYC system. Users could browse and deposit freely at Level 0, but to make larger transactions or withdrawals, they needed to complete KYC 1 verification – uploading ID and proof of address.
3. Respecting Culture and Context
Africa isn’t one market; it’s a collection of unique cultural systems, behaviors, and languages that shape how people use money. Designing for this landscape isn’t about copying what works in one market (e.g. Lagos, Nigeria) and pasting it on to the next market (e.g. Nairobi, Kenya); it’s about tweaking the same tools to fit the context, user needs and cultural realities of the local market so that it feels familiar, yet more efficient.
With Karla, we understood that bank transfers were already the dominant payment habit. Instead of trying to replace them, we built on top of that trust, adding features like tap‑to‑pay and QR scan‑to‑pay that made the experience faster without significantly changing user behavior. The design goal wasn’t disruption; it was extension, making something old feel new again.
At HostFi, we applied the same thinking. Many crypto products looked intimidating or overly technical, which alienated everyday users. We chose a relatable, finance‑first visual language, clean layouts, simple flows, and accessible copy while keeping all the crypto capabilities beneath the surface. This balance helped users, from casual savers to experienced traders, feel at home in a space that usually feels exclusive.
What I’ve learned is simple: in Africa, meaningful design isn’t about radical change. It’s about meeting users where they already are, then quietly moving them forward.
4. Keeping It Simple, Always
Complexity is exclusion. Most fintech teams underestimate the intimidation factor of financial jargon, especially for first‑time digital users.
At Karla, we initially described one feature as “Make payments with NFC.” It made sense to us, but in user interviews, only 2 out of 10 people understood it.
We rewrote it as “Tap to pay from your phone.” Suddenly, comprehension surged.
We applied the same approach to HostFi, where crypto terminology often alienated users. “Convert stablecoins to fiat” became “Exchange your Dollars for Naira.” The insight was simple: clarity builds confidence, and confidence drives conversion.
We also used visual storytelling, onboarding screens with relatable analogies, short explainer animations, and real‑world use cases (“Send money to your cousin in Ghana instantly”). Those changes reduced drop‑offs and made the products feel more approachable and relatable.
5. What Design Really Means for Inclusion
When people think of accessibility, they often picture color contrast or font size. In African fintech, accessibility is deeper; it’s economic inclusion.
See also: “We found out that Opay operates from China”‑ Lawmakers flag gaps in Nigeria’s fintech regulation
At HostFi, we realized that the fastest way to build trust wasn’t through motivational language; it was through visibility. We introduced a feature that lets users see the real‑time value of their portfolio across multiple currencies: Naira, Dollars, and stablecoins. No hidden conversions, no guesswork. Whether the market moved up or down, users could always see their exact worth in a currency they understood.
That small shift helped users, especially new users, see themselves as part of the system. When design translates complexity into clarity, it gives people the courage to participate; whether that’s sending money abroad, paying bills online, or investing for the first time.
Closing note:
Across different leading fintech apps, I’ve seen design do what technology alone couldn’t: help people trust money they can’t touch.
Designing fintech for Africa has taught me that progress doesn’t come from innovation alone; it comes from understanding. Trust isn’t built by encryption protocols or sleek UI. It is built on small, thoughtful moments that make users feel safe, capable, and in control.
If we can design fintech that works in chaos, speaks in local language, and earns trust one tap at a time, we’re not just moving money, we’re moving belief.
That’s how accessibility scales. That’s how design drives inclusion.