What Is Mojaloop? Open-Source Payment Interoperability

In many markets, money is trapped inside silos. A customer on one mobile wallet cannot easily pay someone on a different wallet, and small banks lack the scale to build direct connections to everyone else. Mojaloop is an open-source software platform designed to solve exactly this problem: it provides the plumbing that lets many separate financial providers interoperate, so a payment can flow from any account to any other account regardless of which institution holds it.

Where Mojaloop came from

Mojaloop began as a reference implementation for real-time, interoperable digital payments, developed with support from philanthropic backers focused on financial inclusion and later stewarded by a dedicated foundation. The name blends Mojaloop from the Swahili word moja, meaning "one" — a nod to the goal of one connected payment fabric. Crucially, it is not a payment scheme you sign up to as a consumer. It is open-source code and a set of specifications that a country, a central bank, or a commercial switch operator can deploy to run their own interoperable network.

The core idea: a shared switch for DFSPs

The participants in a Mojaloop network are called DFSPs — Digital Financial Service Providers. A DFSP might be a bank, a mobile money operator, a payment fintech, or a microfinance institution. Instead of every DFSP building point-to-point links to every other DFSP (an arrangement that grows unmanageably as participants multiply), each connects once to a central hub, or switch. The hub routes payment instructions, coordinates the exchange, and keeps track of what each participant owes the others.

This hub-and-spoke model is what makes interoperability affordable. Adding the tenth or the hundredth participant does not require rewiring everyone else; it just needs one more connection to the hub.

How a payment flows

A typical Mojaloop transfer moves through a few well-defined phases, coordinated by APIs that every participant implements the same way:

1. Discovery / lookup. The payer's provider asks the hub to resolve an identifier — often a phone number or an alias — into the DFSP that holds the payee's account.
2. Agreement / quoting. The two sides agree on the terms of the transfer, including any fees, before money moves. The payer can be shown a firm quote.
3. Transfer. The instruction is executed using a reserve-then-commit pattern so that funds are earmarked and then confirmed, avoiding a state where money leaves one side but never arrives at the other.

Underneath, Mojaloop uses a conditional transfer mechanism inspired by the Interledger Protocol: funds are held against a cryptographic condition and only released when the correct fulfilment is presented. This gives the network a strong guarantee that a transfer either completes fully or not at all.

Settlement between participants

Moving a payment instruction is only half the story. The DFSPs still have to settle real value between themselves. Mojaloop keeps a running net position for each participant — the sum of what it has sent versus received — and participants typically prefund their positions by placing funds in a settlement account. The hub enforces that a DFSP cannot send more than its available position allows, which caps the network's exposure if a participant fails. Actual movement of the underlying funds between institutions then happens on a settlement cycle through the banking system.

Why builders care

For engineers and product teams, Mojaloop is interesting because it standardizes the hard parts of interoperability behind open APIs. You do not have to invent your own transfer state machine or negotiate a bespoke protocol with every counterparty. The specifications also increasingly align with ISO 20022 messaging, which eases integration with the wider financial world. Platforms that bridge multiple rails — for example, KibiPay connecting mobile money alongside domestic and card networks — often lean on Mojaloop concepts precisely because the reserve-and-commit model and net settlement map cleanly onto a ledger-backed system.

What Mojaloop is not

It is worth being precise. Mojaloop is not a currency, not a blockchain, and not a consumer app. It does not custody funds itself; the DFSPs do. It is infrastructure — deployed and operated by a scheme, often with regulatory involvement — that lets otherwise-disconnected providers behave as one interoperable market.

Takeaway

Mojaloop is best understood as an open-source blueprint for a national or regional payment switch. By giving every provider one connection, a shared transfer protocol, and a disciplined settlement model, it turns a fragmented set of wallets and banks into a single reachable network. That is why it is so closely tied to the financial-inclusion story: interoperability is what makes small accounts genuinely useful.