Infrastructure for interoperable payments
Hub Finance Portal gives scheme operators and participating financial institutions one governed workspace to understand payment activity, coordinate operations, investigate risk, and account for every decision.
Participants
Banks, wallets & DFSPs
Scheme
Hub operator & oversight
JengaCore
A trusted operational view of the payment ecosystem
The project
Interoperable payment schemes connect many institutions, systems, and operating teams. The information needed to run them is often scattered across technical services, reports, and specialist tools.
JengaCore turns that fragmented context into a shared operational workspace. It is not the payment switch; it sits alongside the core, giving authorized teams a clearer way to observe, act, and govern.
Purpose-built access
Each portal provides the context its users need while keeping participant data and privileged scheme actions inside explicit boundaries.
A control room for the teams responsible for the health, integrity, and day-to-day operation of the payment scheme.
A focused workspace for banks, wallets, and other participating institutions to manage their own place in the scheme.
Operational lifecycle
JengaCore keeps investigation and operations connected to governance, so decisions retain their evidence, ownership, and history.
Bring transfers, participant positions, settlements, disputes, and risk signals into one operational view.
Give each team the tools and context to investigate issues, coordinate work, and take permitted actions.
Apply role controls, maker-checker approvals, tenant policy, and a durable audit trail to every sensitive decision.
Connected capabilities
Capabilities share context across the transfer lifecycle, helping teams move from monitoring to investigation without losing the thread.
Register and oversee DFSPs, inspect operational status, and keep every participant action within a clear scheme context.
Track positions, pre-funded balances, Net Debit Cap usage, and funding movements before they become operational issues.
Search and trace transfers across the switch, inspect their lifecycle, and give support teams a shared operational record.
Coordinate settlement windows, review obligations, and manage exception and dispute workflows with accountable decisions.
Review screening outcomes, investigate connected activity, and follow the movement of funds across related profiles and institutions.
Maintain tamper-evident operational history and produce scheme-wide reports for management, compliance, and supervisory review.
Architecture principles
The browser talks to the Next.js backend first. That backend owns policy, scoping, audit, and integrations, keeping external services away from client code.
All core and service calls pass through governed server routes.
Demonstrate safely with realistic data, then connect Mojaloop services through environment configuration.
Scheme policy, risk thresholds, participant context, and branding adapt without forking the application.
Correlation IDs, trace propagation, audit events, and an optional event outbox preserve operational evidence.
Integration, without dependency
JengaCore can combine Mojaloop administration, ALS, reporting feeds, and optional fraud signals from services such as Tazama. Integrations enrich the operational picture while remaining independently deployable and replaceable.
Explore the working project