Payment Hub Enterprise Edition middleware and Payments Orchestration Engine for integration to real-time payment systems. Orchestrate & Streamline bulk G2P & P2G payements. Enable seamless participation of DFSPs into payments.
Payment Hub EE supports both DFSP and Government Functions (v1.13.0 awarded GovStack Level 1 Compliance) GovStack PH EE Compliance Statement.
- Connectorised approach allowing for easy payment rail and systems integration.
- BPMN Workflows supported.
- 2 Workflow Engines supported Zeebe or Netflix Conductor (DPG core)
The solution is a multi repo approach supporting modularity.
Version 2.0 renames the repositories to paymenthub-ee-* and reduces their number by combining
several of the old ones into a single repository, while keeping them as separate modules. Where a
repository has not been migrated yet it is listed under its ph-ee-* name and marked.
paymenthub-ee-core – The shared foundation: the platform BOM and the common library every Java component builds on (combines ph-ee-connector-common and the BOM). This repo.
ph-ee-dpg-core – DPG-compliant orchestration engine built on Netflix Conductor (alternative to the Zeebe-based flow). Not migrated yet.
ph-ee-dpg-template – Starter template for building components on the Conductor/DPG-core architecture. Not migrated yet.
paymenthub-ee-data-pipeline – Everything that moves workflow data out of the Zeebe broker and into a queryable store (combines ph-ee-exporter, ph-ee-importer-es, ph-ee-importer-rdbms and ph-ee-zeebe-ops).
paymenthub-ee-k8s-operators – Kubernetes Operators for deploying/managing PH-EE components.
paymenthub-ee-connector-channel – Front-door connector that receives requests from client channels.
paymenthub-ee-connector-bulk – Closed-loop bulk payment connector.
paymenthub-ee-connector-mojaloop – Connector to the Mojaloop Switch scheme.
paymenthub-ee-connector-mm-gsma – Connector for the GSMA Mobile Money API.
ph-ee-connector-gsma-mm-dpg – DPGA-compliant variant of the GSMA MM connector using Netflix Conductor workflow. Not migrated yet.
paymenthub-ee-connector-mpesa – Connector for Safaricom M-Pesa.
ph-ee-connector-mccbs – Connector to Mastercard Cross-Border Services (currently demo/non-production). Not migrated yet.
paymenthub-ee-connector-slcb – Connector integrating with SLCB.
ph-ee-connector-pch-java – Connector for a Payment Clearing House integration (gRPC based). Not migrated yet.
paymenthub-ee-connector-crm – CRM-facing connector microservice.
paymenthub-ee-connector-ams-mifosx – Account Management System (AMS) connector for MifosX core banking.
ph-ee-connector-ams-pesa – AMS connector for a Pesa-type core banking system. Not migrated yet.
paymenthub-ee-connector-ams-paygops – AMS connector for the PayGOps platform.
paymenthub-ee-bff – Backend for the Operations web app: monitoring and managing transactions and workflows, plus the G2P programs API (combines ph-ee-operations-app and ph-ee-operations-g2p-service).
paymenthub-ee-operationsui-angular – Front-end for the Operations web app (original in Angular).
paymenthub-ee-operationsui-react – React-based front-end for Operations (modernized replacement in React ShadCN).
paymenthub-ee-account-mapper – Maps external identities to account details for payment routing, with the account validator implementations as a module (combines ph-ee-identity-account-mapper and ph-ee-id-account-validator-impl).
paymenthub-ee-auth – Identity/auth provider service for PH-EE (was ph-ee-identity-provider).
paymenthub-ee-notifications – Notification delivery, works with the separate message-gateway project.
paymenthub-ee-vouchers – Voucher management/issuance system.
paymenthub-ee-p2g – Bill payment processing microservice, P2G (was ph-ee-bill-pay).
paymenthub-ee-bulk-processor – Bulk/batch transaction processing microservice (G2P).
ph-ee-nats-importer-rdbms – Consumes NATS events and writes business data to an off-site RDBMS. Not migrated yet.
ph-ee-acknowledgement – Placeholder repo for an acknowledgement service (README only, no code yet). Not migrated yet.
paymenthub-ee-e2e-tests – The end-to-end suite and the mock payment scheme it transacts against (combines ph-ee-integration-test and ph-ee-connector-mock-payment-schema).
ph-ee-testing-toolkit – Functional testing toolkit for PH-EE development/QA. Not migrated yet.
ph-ee-testing-toolkit-ui – Experimental UI for the testing toolkit. Not migrated yet.
ph-ee-ai-arch-test – Experimental AI-driven architecture testing. Not migrated yet.
ph-ee-env-template – Template environment/deployment configs. Not migrated yet.
ph-ee-env-labs – Actual lab environment configs — BPMN flows and Helm charts for a live lab deployment. Not migrated yet.
For detailed documentation check the documentation: PH EE Gitbook
The shared foundation for Payment Hub EE: the platform Bill of Materials (BOM) and the common library that every PH-EE Java component builds on.
This repo publishes two artifacts that the rest of Payment Hub EE depends on. It is not a runnable service. It has no main method and starts no server. It only produces libraries that other PH-EE components import.
- The BOM (
org.mifos:paymenthub-ee-bom) pins one agreed version for each dependency: Spring Boot, Apache Camel, Zeebe, Jackson, AWS SDK, and more. Each component imports it withenforcedPlatform, so every component lines up on the same versions and does not pin them by hand. - The core library (
org.mifos:paymenthub-ee-core) is the shared code, the migratedph-ee-connector-common. It holds shared DTOs, channel and Mojaloop model classes, Zeebe helpers, and small utilities that the connectors reuse.
bom— the Payment Hub EE Bill of Materials; pins the versions of Spring Boot, Camel, Zeebe, Jackson, and the other shared dependencies.core— the shared common library (the migratedph-ee-connector-common): shared DTOs, channel and Mojaloop model classes, Zeebe helpers, and utilities.bom:bom-verification— a small module that imports the BOM and resolves every declared dependency, so the build fails here if the BOM does not resolve correctly.
Every PH-EE Java connector depends on this repo twice: on the BOM for its dependency versions, and on core for the shared code it reuses. That makes paymenthub-ee-core the base of the PH-EE dependency graph. When its versions or shared classes change, all the connectors pick up the change from here.
Java 21, Spring Boot 3.4, Apache Camel 4, Jakarta EE 10, built with a Gradle multi-module setup. It publishes org.mifos:paymenthub-ee-bom and org.mifos:paymenthub-ee-core.
devis the active development branch — all PRs should targetdev.mainholds released versions.
See contributing.md, our Code of Conduct and the security policy.
For more developer specifics regarding Payment Hub EE please also refer to:
- Community Code of Conduct
- PH EE Contributing Guidelines
- Security Disclosure Policy
- Contributor Licence Agreement
More information about Mifos and our Mission can be found at mifos.org