UI/UX Fintech et Mobile Money en RDC | Wise Hustlers

# UI/UX Design for Fintech and Mobile Money Apps in DRC

Summary: Good fintech UX in DRC is judged first by whether it works over USSD and weak connectivity, whether it reassures a fraud-wary user, and whether it plugs cleanly into M-Pesa, Airtel Money and Orange Money flows — not by how polished its animations are.

A mobile money market unlike most others

Congolese mobile money is not a niche channel you bolt onto a fintech product as an afterthought. According to the Q4 2025 report of ARPTC (the national telecoms and postal regulator), the country had 34.3 million active mobile money subscriptions at the end of December 2025, and mobile financial services generated $147 million in transaction revenue in that quarter alone. Of that revenue, Vodacom's M-Pesa led with 43.77%, followed by Airtel Money (41.30%) and Orange Money (14.44%). Over 2025 as a whole, Airtel Money's revenue jumped 42% to $194.8 million, while Orange Money's active customer base grew 50.4% to reach 7.7 million (ARPTC figures reported by Bankable).

That's not a market you win with a standalone app reinventing how payments work. It's a market where three telecom operators have already built habits with tens of millions of Congolese users, and where a new entrant like Wave — which has incorporated a company in Kinshasa and operates in partnership with Ecobank RDC, according to its own terms of use — has to differentiate on experience rather than concept novelty. For a fintech startup, a bank, or an e-commerce business integrating a payment method, the real question isn't "how do we invent a new payment gesture" but "how do we fit into habits that already exist."

Design for the connectivity that actually exists, not the one in the brief

This is where most fintech briefs in DRC go wrong. According to ARPTC, the DRC had 73.9 million active mobile subscriptions at end-2025 but only 37 million mobile internet subscriptions, a 33% penetration rate. Roughly half of mobile subscribers therefore don't use mobile internet, and the GSMA notes that 4G reaches only 57% of the population and that device costs hold back adoption. In that context, USSD isn't a technical fallback channel: it's often the only channel available. ARPTC also notes that mobile financial services pay operators a commission for using USSD codes and messaging.

In practice, this changes how you design:

USSD flows (`*###` menus) need the same design rigor as an app: clear option hierarchy, short unambiguous labels in plain French, and the fewest possible key presses to reach transaction confirmation.
Where a mobile app exists, it has to work on degraded 2G/3G: no blocking loading states, screens that show something useful offline (a timestamped cached balance, a queue of transactions waiting to sync), and heavily compressed imagery.
Power cuts remain frequent in several provinces, which means designing short, atomic transaction flows — a transaction interrupted by a dead battery or dropped network should never leave the user unsure whether the money actually moved.

An ambiguous confirmation screen after a network drop is not a cosmetic detail in a country where the Airtel Money or M-Pesa confirmation SMS often serves as the user's proof of a transaction — it's a direct source of disputes and lost trust.

Trust is the feature you actually need to design

Mobile money fraud is a lived experience for the Congolese user you're designing for, not an abstract risk. Radio Okapi reported in July 2026 a wave of scams in which fake low-cost internet offers — notably Starlink subscriptions priced up to five times below market rate — circulate on WhatsApp and Facebook with links to fraudulent platforms built to collect victims' personal and financial information, then empty their Mobile Money accounts. SIM swap fraud is also documented by ENACT Africa (December 2025) as a problem worsened by insufficient law enforcement.

For a product designer, that translates into concrete decisions rather than vague "security" promises:

Never let an in-app screen resemble a third-party PIN request — the visual distinction between "this comes from the official app" and "this is an external message" should be immediate and redundant (color, copy, context).
Always show the recipient's name and number before confirming a transfer, with a forced moment of review rather than a single reflexively tappable "Confirm" button.
Write security alerts that explain the risk in one plain-French sentence, free of banking jargon — the typical user has no fintech vocabulary, and a poorly worded alarming message is ignored as often as a poorly worded reassuring one is believed.
Make it visible, at every sensitive step, that the app will never ask for a PIN through an external channel — that line belongs on the screen, not buried in the terms of service.

An interface that treats security as a module bolted on at the end loses the trust battle before launch.

Interoperability and compliance: regulatory constraints that shape the UX

On September 4, 2024, the Banque Centrale du Congo (BCC) issued Instruction n°58 on the interoperability of card and electronic payment systems and participation in the National Payment Switch: banks, microfinance institutions, and BCC-licensed payment system operators must connect to the switch so that a payment method issued by one institution is accepted everywhere. An IMF report published in January 2026 expected an interbank electronic payment group to launch by the end of March 2026 (we found no public confirmation of that launch at the time of writing), and cited the September 2025 launch of a Visa Pay platform alongside promotion of the national Mosolo card. On the ground, bridges between banks and mobile money are already in use: in March 2025, with bank branches closed in Goma and Bukavu, Rawbank and Equity BCDC credited teachers' accounts, and teachers could then move their salary through the banking app to an Airtel Money, M-Pesa, or Orange Money wallet — with agent cash-out fees of up to 10%, according to Bankable.

For a fintech or banking app, this means designing flows now that don't assume a single mobile money operator as the final destination. A poorly designed operator selector, unclear fee labeling that varies by operator, or a lack of status feedback while an interbank transaction is in transit will all become visible friction points as full interoperability goes live. Anti-money-laundering and know-your-customer (KYC) obligations also require identity verification during onboarding — a flow that needs to stay as short as possible without cutting corners on compliance, in a country where a large share of the population is still discovering digital financial services: financial inclusion, at 38.5% in 2022 according to the 2023–2028 National Financial Inclusion Strategy (target: 65% by 2028), is estimated at around 58% by the BCC governor in 2026, while the banked rate hovers between 25% and 30%.

Language, literacy, and interface readability

French is the official language and the one used across most existing mobile money interfaces, but a significant share of users in Kinshasa, Lubumbashi, or the eastern provinces communicate day-to-day in Lingala, Swahili, or Tshiluba, with widely varying literacy levels. A fintech UI built for this context benefits from leaning more on universal pictograms — an arrow for "send," a receipt icon for "history" — than on text labels alone, and from keeping each transactional screen down to a single obvious action. It's a discipline closer to designing an ATM interface than a chart-heavy Western banking app full of financial jargon.

What this means for your product

Designing a fintech or mobile money app for the Congolese market means treating degraded connectivity, fraud wariness, and operator fragmentation as core design constraints — not problems the infrastructure will eventually solve on its own. This is the kind of trade-off — USSD flows, anti-fraud confirmation screens, interoperability — that our UI/UX design service covers, starting from real conditions on the ground rather than a generic template.

FAQ

Should a fintech in DRC prioritize a mobile app or a USSD menu?

The two aren't interchangeable: USSD remains the channel reaching the majority of the population without a smartphone or reliable data, while a mobile app targets a more connected urban segment. A serious fintech product in DRC designs both journeys with equal rigor rather than treating USSD as secondary.

How do you design trust into a payment app in DRC?

By making the information that protects users visible and redundant — recipient name shown before confirmation, a reminder that the PIN is never requested through an external channel, and a clear visual distinction between official communications and third-party messages — rather than relying on generic security badges.

Does BCC interoperability change how a payment flow should be designed?

Yes. With 2024's Instruction n°58 on the National Payment Switch and the announced interbank payment group, a payment flow needs to anticipate transfers between different operators, with clearly displayed fees and a reliable transaction status while money is in transit between systems.

What language should a fintech app interface use in DRC?

French remains the reference language for existing interfaces, but designing around universal icons and single-action screens reduces dependence on text — which matters in a multilingual country where literacy levels vary significantly by region.

UI/UX Design for Fintech and Mobile Money Apps in DRC