A country must be able to understand, govern, operate, improve, and adapt the technology beneath its National Payment Switch without asking permission from a single vendor.

01

A national economic nervous system

A National Payment Switch is not merely another government technology project. It becomes part of a country’s economic nervous system.

Every transfer between a bank account and a mobile wallet, every merchant payment, every remittance received by a family, and every digital payment made by a small business depends on the switch operating securely, reliably, and fairly.

That is why the technology beneath a National Switch matters enormously.

The country must be able to understand it, govern it, operate it, improve it, and—when national priorities change—adapt it without asking permission from a single technology vendor.

This is where Mojaloop offers something strategically important.

02

From disconnected networks to one national ecosystem

Many countries already have successful banks, mobile money operators, microfinance institutions, fintech companies, and payment service providers. The problem is that these services often operate as separate islands.

A customer may be able to send money instantly to another customer on the same network, yet encounter friction, high fees, or complete failure when paying someone using a different provider.

Mojaloop is designed to remove those walls.

It is an open-source instant-payment platform that enables different financial institutions to participate in a shared, interoperable network. The platform provides capabilities for beneficiary discovery, payment quotation, transfer processing, transaction finality, participant positions, liquidity controls, and settlement orchestration. A settlement partner—often the country’s RTGS or another approved settlement mechanism—completes the movement of funds between institutions.

For citizens, the result should feel beautifully simple. Behind that simple experience is a carefully coordinated national ecosystem.

Operating principleSend money to anyone, using any participating provider, and know before confirming who will receive it, how much it will cost, and whether it succeeded.
03

Why Mojaloop is relevant to a National Switch

Mojaloop is particularly suited to markets where banks and non-bank financial institutions must coexist within one inclusive payment system.

Mojaloop also supports controls such as participant liquidity balances and Net Debit Caps, helping a scheme limit exposure while allowing institutions to transact throughout the operating day. Its risk-management model is designed around ensuring that cleared obligations are backed by sufficient liquidity.

But Mojaloop should not be mistaken for the entire National Switch.

The software provides a powerful clearing and interoperability engine. The country must still define the scheme around it: membership rules, pricing policy, operating hours, dispute processes, settlement cycles, participant responsibilities, fraud governance, consumer protections, regulatory reporting, service levels, and sanctions.

Operating principleThe code can execute the rules. It cannot decide the rules for the country.
  • Interoperability between banks, mobile money operators, fintechs, microfinance institutions, and other licensed providers.
  • Alias-based beneficiary discovery using identifiers such as telephone numbers or account references.
  • Confirmation of the receiving party before funds are committed.
  • Agreement on payment terms and applicable fees before execution.
  • Real-time clearing with an unambiguous final transaction outcome.
  • Participant position management and liquidity controls.
  • Settlement orchestration through the national RTGS or another settlement partner.
  • Standard interfaces and connectivity tools that reduce the difficulty of onboarding participants.
04

Protect the core, localize the scheme

The strongest implementation model is to keep the Mojaloop core aligned with official releases while building national requirements around it through clear, versioned interfaces.

In my independent Mojaloop evaluation, this principle is explicit.

This separation is crucial.

If every local requirement is implemented by modifying Mojaloop’s core, the National Switch may eventually become difficult to upgrade, secure, and maintain. If national functionality is implemented through stable adapters and well-defined services, the country can benefit from future Mojaloop improvements without repeatedly rebuilding its own platform.

  • Mojaloop owns discovery, quotation, transfer preparation, fulfilment, finality, duplicate control, clearing records, operational positions, and settlement-window processing.
  • Evaluation-owned companion services manage local fraud policy, direct and indirect settlement relationships, sponsor-bank mappings, business dates, settlement cycles, reconciliation, approvals, and RTGS instruction generation.
  • Participant-facing interfaces can remain stable even when the underlying Mojaloop version evolves.
  • Settlement services consume committed transaction events rather than depending directly on Mojaloop’s internal database.
  • Fraud and settlement integrations remain replaceable components instead of permanent modifications to the payment engine.
05

Why open source matters

The most common argument for open source is cost. That argument is valid, but incomplete.

The real value is national agency.

Digital sovereignty

A country should not have to ask permission to improve the payment rails of its own economy.

With open-source infrastructure, the operator can inspect the code, retain its institutional knowledge, select different implementation partners, and continue operating even if a supplier changes direction.

This does not eliminate the need for vendors. It changes the relationship with them. Vendors compete on implementation quality, security, operations, support, innovation, and service—not on exclusive control of the underlying platform.

Freedom from permanent vendor lock-in

A proprietary switch can create deep dependency on one supplier’s licensing model, roadmap, specialist knowledge, and commercial priorities.

An open-source core enables competitive procurement. One company may deploy the platform, another may provide security assurance, and a local operations team may run it. Over time, the operator can change these arrangements without replacing the entire national payment system.

The objective is not a switch without commercial partners. It is a switch that remains bigger than any one partner.

Transparency where trust matters most

National payment infrastructure must earn the confidence of regulators, participants, operators, and the public.

Open code can be examined by authorized engineers, auditors, security researchers, and implementation partners. Design decisions and vulnerabilities can be discussed against evidence rather than treated as inaccessible vendor knowledge.

Open source does not make software automatically secure. It makes independent verification possible.

Local capacity becomes a national asset

When local engineers can study and operate the complete platform, expenditure on implementation can also become investment in domestic capability.

Knowledge stays within the country. Universities can teach relevant technologies. Local system integrators can build expertise. National operators can develop engineering and operational teams that understand the switch from the protocol boundary to settlement output.

Rwanda’s Mojaloop-based RNDPS 2.0 illustrates this potential: the implementation was led by RSwitch with support from a Rwandan systems integrator, and the platform operates under the local eKash identity.

Shared innovation without surrendering national control

Payment systems across different countries face many of the same challenges: participant onboarding, fraud, liquidity, merchant payments, settlement, interoperability, observability, and operational resilience.

An open-source community allows improvements developed in one market to inform others. Mojaloop’s roadmap is maintained collaboratively and focuses on making adoption easier, improving scale, strengthening security, and connecting with other payment systems.

A country can benefit from this shared engineering base while retaining authority over its own scheme rules and deployment.

06

Open source is not the same as free

There is an important warning for decision-makers: downloading Mojaloop does not create a production-ready National Switch.

A national deployment still requires substantial investment.

Mojaloop itself places responsibility for production fitness on the scheme operator and provides readiness guidance rather than claiming that a standard deployment is automatically production-ready.

Open source reduces dependency. It does not remove responsibility.

In fact, it makes the most important responsibility unmistakable: the National Switch belongs to the nation operating it.

  • Scheme design and legal frameworks.
  • Participant onboarding and certification.
  • Cybersecurity and independent assurance.
  • High availability and disaster recovery.
  • Fraud detection and case management.
  • Operational monitoring and transaction tracing.
  • Liquidity and settlement operations.
  • Reconciliation and regulatory reporting.
  • Capacity and performance testing.
  • Release management and controlled upgrades.
  • Skilled engineering and 24/7 operational support.
07

The strategic opportunity

A well-designed Mojaloop National Switch can become more than a transaction router.

It can become a shared foundation for bank-to-wallet payments, merchant acceptance, government disbursements, remittances, fintech innovation, regional interoperability, and future digital public infrastructure.

Its success, however, will not be measured by the number of services deployed or APIs implemented. It will be measured by outcomes.

That is the promise of Mojaloop when it is implemented well.

For a National Payment Switch, that means open infrastructure, transparent governance, competitive service delivery, strong national operations, and a payment ecosystem designed around the needs of the entire economy—not the limitations of a single network or vendor.

Operating principleOpen source is not the absence of ownership. It is the opportunity to place ownership where it belongs.
  • Can a citizen pay anyone, regardless of provider?
  • Can a small institution join without prohibitive integration costs?
  • Can a merchant receive an affordable instant payment?
  • Can participants trust transaction finality?
  • Can the operator manage liquidity and systemic risk?
  • Can the country change suppliers without losing control of its infrastructure?
  • Can local engineers operate and evolve the platform?
Field conclusion

A National Payment Switch should remain bigger than any supplier: open at its core, national in its governance, and locally owned in its operating capability.

Public evidence ledger

Inspect the basis for this note.

These links point to public implementation evidence or authoritative documentation used for the claims above. The interpretation is mine; institutional code and ownership remain with their respective owners.

  1. 01
    Mojaloop feature catalogue

    The official product documentation describes the platform capabilities behind an Inclusive Instant Payment System.

    Open source evidence
  2. 02
    Risk management and liquidity

    Mojaloop documents participant liquidity balances, Net Debit Caps, and the controls used to limit clearing exposure.

    Open source evidence
  3. 03
    Rwanda RNDPS 2.0 and eKash

    The Mojaloop Foundation describes the locally led RSwitch implementation and its collaborative delivery model.

    Open source evidence
  4. 04
    Public Mojaloop roadmap

    The community roadmap makes the platform’s adoption, scale, security, and interoperability direction visible.

    Open source evidence
  5. 05
    Deployment and production readiness

    The deployment guidance distinguishes a software baseline from the scheme operator’s responsibility for production fitness.

    Open source evidence