Mifos Payment Hub-EE (PH-EE)
Digital PaymentsMifos Payment Hub EE is an open-source payment orchestration layer that routes transactions between core banking systems and payment networks using BPMN workflows on the Zeebe engine, with connectors for mobile money, bulk disbursements, P2P and QR payments. It is in the collection as payments infrastructure: new payment systems are added through connectors and workflow definitions rather than code changes.
- DPG Profile: https://www.digitalpublicgoods.net/r/mifos-payment-hub-ee-ph-ee
- Website: https://payments.mifos.org
- Source code: https://bit.ly/ph-ee
All DPGs in the DPGs for DPI Collection are assessed by the DPGA Secretariat against the DPGs for DPI criteria v2.0. Assessments use publicly available documentation and link to their evidence below. Assessed September 2026.
14 of 18 checks met
4 partially met
Layer 1
Recognised DPG
Layer 2
DPI Relevance
Layer 3
DPI Architecture Alignment
Layer 1 Recognised Digital Public Good
Listed in the DPG Registry.
Layer 2 DPI Relevance
Does it provide a foundational DPI function, reusable across sectors, at population scale?
It is a payment orchestration hub connecting core banking to payment networks, in the Digital Payments domain. The same routing serves mobile money, government-to-person transfers, P2P and merchant payments, and it is built for financial service providers at scale, integrating with Mojaloop and other national payment schemes.
- Business overview: https://mifos.gitbook.io/docs/payment-hub-ee/business-overview
- Mifos payments: https://payments.mifos.org/welcome/
Layer 3 DPI Architecture Alignment
How the solution's architecture reflects the principles that distinguish DPI from conventional digitisation.
A · Interoperability
3/3Can other systems connect without modifying the core, using documented open standards?
Payment Hub REST APIs are documented on the Mifos documentation portal. It supports ISO 20022, the GSMA Mobile Money API and BPMN 2.0 workflow definitions, exchanging JSON over REST with an open workflow standard.
- Payment Hub APIs: https://mifos.gitbook.io/docs/payment-hub-ee/overview/payment-hub-apis
- Overview: https://mifos.gitbook.io/docs/payment-hub-ee/overview
- Data architecture: https://mifos.gitbook.io/docs/payment-hub-ee/overview/data-architecture
B · Minimalist & Reusable Design
3/3Is it a modular building block that does one thing well, rather than a monolithic platform?
Microservices are orchestrated by the Zeebe workflow engine, with independent, pluggable workers. The orchestration layer is clearly distinct from the connectors to backend systems, and new payment systems are added by writing connectors and BPMN workflows rather than modifying the core.
- Overview: https://mifos.gitbook.io/docs/payment-hub-ee/overview
- Benefits of Payment Hub EE: https://mifos.gitbook.io/docs/payment-hub-ee/business-overview/benefits-of-payment-hub-ee
C · Ecosystem Enablement
3/3Can other public and private actors build on top of it?
The connector model lets anyone build workers for any account management or payment scheme, with BPMN making flows configurable. Existing connectors cover Mojaloop, Fineract and the GSMA Mobile Money API across multiple financial service providers, and the open-source stack (Zeebe, Kafka) carries no proprietary lock-in.
- Overview: https://mifos.gitbook.io/docs/payment-hub-ee/overview
- Business overview: https://mifos.gitbook.io/docs/payment-hub-ee/business-overview
- Source documentation: https://github.com/openMF/mifos-documentation/blob/master/payment-hub-ee/overview/README.md
D · Federation Readiness
1/3Can it run in distributed or federated deployments suited to national infrastructure?
Self-hosted deployment means each institution controls its own data and payment flows. The model is one hub per institution with no explicit hub-to-hub federation, and while Zeebe provides workflow resilience, explicit multi-instance high-availability documentation is limited.
- Overview: https://mifos.gitbook.io/docs/payment-hub-ee/overview
E · Security & Privacy at Scale
1/3Does it meet the security and privacy bar for population-scale infrastructure?
Financial-grade protections apply, with TLS and authentication for API access. There is no dedicated vulnerability disclosure policy for Payment Hub EE — reporting relies on the wider Mifos community — and cross-jurisdictional privacy documentation is limited.
- Overview: https://mifos.gitbook.io/docs/payment-hub-ee/overview
- Source code: https://github.com/openMF
Criteria: DPGs for DPI Collection criteria v2.0 · Co-stewarded by CDPI, Co-Develop and the DPGA Secretariat.
Spot something out of date? Contact the DPGA
