WSO2 middleware, mobile banking and USSD for a commercial bank in Somalia
Our team, with a delivery partner, connected a Somali commercial bank's core banking to the national payment switch, mobile money and billers through WSO2, and built its mobile and USSD banking.
- Commercial bank, Somalia
- Somalia
- 2025
Status at a glance
Which parts are live, which are in pilot, and which are built and awaiting activation.
| Part of the system | Status |
|---|---|
| WSO2 middleware connecting core banking, the payment switch, mobile money and billers | Live |
| Android and iOS mobile banking apps | Live |
| USSD banking channel | Live |
The starting point
The bank's core banking system (Oracle Flexcube) sat on its own. Every new partner, from the national payment switch to mobile money operators and billers, meant another point-to-point link that was slow to build and hard to secure and monitor. New digital services waited on integration work, and the bank needed mobile and USSD banking its customers could use every day.
What we delivered
- WSO2 API Manager and WSO2 Micro Integrator deployed as the bank's middleware, with API security, rate limiting and monitoring in one place
- 50+ core banking APIs from Oracle Flexcube unified behind one managed layer, covering accounts, transactions, loans and customer data
- A real-time connection to the national payment switch for interbank payments
- Integrations with two mobile money operators and with billers for bill payments
- Android and iOS mobile banking apps, published in Google Play and the App Store
- A USSD banking channel for customers without a smartphone
In numbers
Each figure comes from the project's own records and shows the month we verified it.
50+
core banking APIs unified behind one managed integration layer
6
months to deliver the core integration project
The client
Our client is a commercial bank in Somalia offering retail and corporate banking. Our team delivered this project with a delivery partner; the client is not named.
The problem with point-to-point links
The bank runs Oracle Flexcube as its core banking system. Each outside party it had to reach, whether the national payment switch, a mobile money operator or a biller, needed its own connection. Each one took time to build, had its own security arrangements and was hard to monitor. Launching a new digital service meant waiting for yet another integration.
What we built
One managed integration layer. We deployed WSO2 API Manager and WSO2 Micro Integrator as the bank’s middleware. More than 50 core banking functions, covering accounts, transactions, loans and customer data, now sit behind one layer with OAuth2 security, rate limiting, threat protection and API analytics.
Connections to the outside world. Through that layer the bank reaches the national payment switch for interbank payments, two mobile money operators and its billers.
Channels for customers. We built Android and iOS mobile banking apps, now in Google Play and the App Store, and a USSD channel for customers on basic phones. Loans and term deposits run through the same APIs, so every channel offers the same products.
Delivery and support
The core project was delivered in about six months and went live in production in 2025. The bank has an ongoing support agreement covering maintenance, support and upgrades. Card payments are a separate workstream and are still in testing.
Why it matters
A bank that connects once, to a managed layer, can add a new partner or channel in weeks rather than months, and it can see and secure every call in one place. We bring the same approach to banks, microfinance banks and SACCOs in Kenya and across East Africa.
What it runs on
- WSO2 API Manager
- WSO2 Micro Integrator
- Oracle Flexcube
- Android
- iOS
- USSD
What is taking too much time in your business?
Tell us about one task. We reply within one working day and suggest the simplest way to handle it.