Scheme rules and participation
Who can join, on what terms, and with what obligations. Tiered participation lets banks, mobile money operators, MFIs and SACCOs connect at the level their size and risk allow.
Pillar 01 · Payments
Inclusive instant payment systems.
An inclusive instant payment system (IIPS) lets anyone pay anyone, instantly, at low cost, whichever bank or wallet they use. We help central banks, switch operators and schemes design and build them on Mojaloop and ISO 20022, and we build the tools that keep them safe.
Why it matters
Instant is easy. Inclusive is the hard part.
Most countries now have some form of instant payments. Far fewer have one that a market trader with a feature phone, a rural SACCO, or a social-transfer programme can actually use. Closed wallets that cannot pay each other keep people in silos and keep costs high.
An inclusive system is designed around the people at the edge of the network: open participation, low-cost push payments, alias-based addressing, agent networks and channels that work without a smartphone.
Building blocks
What an inclusive rail is made of.
ISO 20022 and open APIs
Rich, structured messages and published interfaces, so every participant integrates once and data survives end to end.
Alias directory
Pay a phone number or an ID instead of an account number. The alias layer is what makes a rail usable by everyone.
Fraud and AML hooks
Screening built into the flow of the rail, not bolted onto each participant. Instant payments need instant defences.
Inclusion channels
USSD for feature phones, agent cash-in and cash-out, and bulk government-to-person transfers designed in from the start.
Cross-border readiness
Hooks for regional systems such as PAPSS, so a national rail can connect to its neighbours without a rebuild.
G2P payments
The everyday test of an inclusive rail.
Government-to-person payments, such as social transfers, pensions and relief, are where a rail proves it is inclusive. They need identity to find the right person, data exchange to confirm eligibility, and a payment system that pays into the account each beneficiary chooses, addressed by phone number or ID.
Designing G2P onto an interoperable rail, instead of a single contracted provider, gives beneficiaries choice, gives programmes real-time status for every payment, and keeps the last mile, agents and cash-out, part of the design.
How we deliver
Gated, testable, handed over.
Each phase ends with something the operator can verify: an agreed design, a conformance report, a rail that its own team can run. Nothing moves forward on a promise.
- 01
Design
Scheme rules, participation model, use cases and target architecture, agreed with the operator and the regulator before a line of code. - 02
Build on open source
Mojaloop as the switching core, deployed on Kubernetes with infrastructure as code, observability and CI/CD, on-premise or in-country cloud. - 03
Sandbox and conformance
Participants integrate in a sandbox and are validated with the Mojaloop Testing Toolkit, alongside load and failure testing. - 04
Pilot-ready and handover
Operational runbooks, security hardening and training, so the operator's team can run the rail itself.
Mojaloop
Active in the Mojaloop community.
Mojaloop is the open-source software for inclusive instant payment systems, backed by the Mojaloop Foundation and used by national and regional switches. It is the core we build on.
We contribute to it as well as use it. Here is what that means in practice.
Listed Mojaloop service provider
Jengacore is listed in the official Mojaloop Service Provider Directory, connecting SACCOs, MFIs and national payment switches across Africa.
Leading the localisation workstream
We lead the Mojaloop documentation localisation workstream. The French translation of the documentation was delivered, peer-reviewed and published on the official site.
A running reference deployment
We operate a Mojaloop stack on Kubernetes with infrastructure as code, observability and CI/CD, exercised with the Testing Toolkit. It is a reference and demonstration environment, not a national production switch.
Contributing since 2019
Our co-founder Elijah Okello has worked with Mojaloop since 2019: open-source contributions to Mojaloop vNext, automated Kubernetes deployment of Mojaloop with Payment Hub EE and Apache Fineract (Mifos Gazelle), and, in previous roles, participant integrations for the COMESA regional payment system.
- Mojaloop
- Mojaloop Testing Toolkit
- Payment Hub EE
- Apache Fineract
- ISO 20022
- FSPIOP API
- Kubernetes
Keeping the rail safe
Screening built for instant payments.
A payment that settles in seconds cannot wait for a batch review. Mulisa, our transaction monitoring platform, screens Mojaloop and ISO 20022 traffic in real time and returns an advisory decision. It never blocks a payment: the institution decides.
Designing or upgrading a national rail?
From scheme design to conformance testing, we can take on a workstream or the whole build, with your team alongside.