Mojaloop Community Central: Paul Makin

Workstream Status Updates

Paul Makin — Mon, 06 Oct 2025 14:00:52 +0000

Following in-depth updates at the Workstream Leads call last Thursday, 2nd October, the latest, detailed statuses of all of the workstreams can be reviewed at https://community.mojaloop.io/active-workstreams

You can also view a brief, summary version of these statuses by clicking here.

PI 28 Workstreams

Paul Makin — Thu, 14 Aug 2025 13:45:45 +0000

I've updated the list of workstreams for PI 28 - you can see them here: https://community.mojaloop.io/active-workstreams

One change is that I'm not using the airtable to give an indication of future roadmap. So not all of the workstreams are currently active. One the left hand side each has one of the following classifications:

"Active - High Priority". These are the workstreams that we need to complete with some urgency. Together they define the standard set of functionality Mojaloop deployments need in order to achieve their potential.
"Active". These are important workstreams, but we can afford to complete them at a more leisurely pace.
"High Priority Candidate". The first roadmap category, these workstreams are needed with a greater or lesser degree of urgency, but we don't currently have capacity to begin them.
"Not Yet Begun". This is the second of our roadmap categories. A workstream in this category is something we know needs to be done, and is reasonably well defined, but we do not currently have an adopter asking for it.

When you're viewing the rather crowded spreadsheet, don't forget to click on the "View Larger Version" button at bottom right.

Mojaloop Roadmap for PI 27

Paul Makin — Thu, 08 May 2025 15:47:34 +0000

The updated Roadmap for PI 27 is available in the Product Council repo in SVG format (with a link to the DrawIo source in the ReadMe file). The micro version is here:

Adapting for Impact: Strategic Shift for vNext

Paul Makin — Mon, 23 Dec 2024 09:57:09 +0000

The Mojaloop Foundation has been diligently working to make vNext a potential release candidate, as outlined in Paul Makin's "Process Towards vNext Adoption”. Significant progress has been made since the release of the Beta code, thanks to the dedicated efforts of ThitsaWorks in addressing tasks from the structured list created to guide vNext toward release candidate status. Their contributions include improving definition documents, unit testing, and the deployment process.

Why the change?

At the same time, challenges have surfaced:

Resource Constraints: Despite ThitsaWorks’ efforts, advancing vNext has been constrained by a scarcity of dedicated resources.
Refinement of vNow: In the intervening time since the inception of vNext, the previously identified limitations of the vNow codebase, such as in the area of performance, have largely been addressed, strengthening vNow’s foundations.
Momentum of vNow: With deployment projects under way with the vNow codebase, and many potential adopters showing strong interest in deploying Mojaloop—evidenced by the participation of 15 Central Banks at the recent Mojaloop convening in Kigali—the reality is that new features are being developed for vNow. This further compounds the functional gaps between vNow and vNext, with features like ISO 20022, foreign exchange and interscheme support being planned for migration to vNext, further impacting timelines for vNext’s readiness for production beyond the previously-identified issues around code readiness and documentation.
TigerBeetle’s Integration: Initially envisioned as a key benefit of vNext, this integration has not been completed, and the TigerBeetle team has now committed to integrating TigerBeetle directly into vNow.

Taken together, these factors have prompted a re-evaluation of the strategy for vNext.

What’s the new strategy?

To ensure resources are used effectively and align with customer needs, the Foundation is introducing a revised approach:

Feature, Component, and Principle Migration: vNext itself is not being abandoned, instead its strengths will be incorporated into vNow over time. Features, technical components, and principles incorporated into vNext will be analyzed for their potential to enhance vNow. For example, security improvements and concepts from the various portals will be prioritized for migration. This ensures that vNext’s innovations continue to inform and improve Mojaloop. Two dedicated workstreams have been established to oversee this process:
- “Mojaloop Evolution” will focus on identifying those vNext elements that would most benefit Mojaloop, and refactor them for the vNow codebase. This workstream will comprise members from the Mojaloop Community.
- “TigerBeetle Integration” will be dedicated to integrating TigerBeetle into the Mojaloop central ledger, and exploring new approaches to settlement. As well as members from the Mojaloop Community, this workstream will be supported by the TigerBeetle team.

All analyses and implementations will be reviewed by the Design Authority (DA) before coding begins.

Continuous Reference Architecture Review: Insights from the vNext development process have underscored the importance of evolving the approach to reference architecture reviews. Moving forward, each impactful new feature implemented in Mojaloop will prompt a re-evaluation of the reference architecture to identify opportunities for improvement. A catch-up process will also address recently implemented features like foreign exchange to assess their architectural implications.

The Mojaloop Community will continue to operate a stable roadmap and release programme which adopters can rely on and plan around, while focusing available resources on the most impactful changes. This strategy has been approved by both the Mojaloop Technical Governance Board (TGB) and the DA.

The Foundation is actively seeking community members eager to contribute to strengthening Mojaloop and driving continuous improvement of the platform.

If you are interested in joining either of the new workstreams, please refer to the details below:

For any questions or to explore opportunities to contribute, please contact James, Paul, or Julie.

Product Council Schedule for PI 28

Paul Makin — Wed, 27 Nov 2024 17:24:12 +0000

The schedule for Product Council meetings during PI 28 is under development, and will be shared here soon.

Workstreams Selected for PI 26

Paul Makin — Wed, 27 Nov 2024 16:02:39 +0000

The following workstreams have been chosen by the Community for PI 26. Note that these will be subject to monitoring, and any workstreams that have been deprioritised or have hit some form of roadblock will be removed from this list.

Workstream	Lead	Mojaloop Slack Channel
Participation Tools	@James Bush	#ws-participation-tools
Participation Tools for Fintechs	@alain Kajangwe	#ws-participation-pisp
Deployment Tools - Maintenance	@James Bush	#ws-deployment-tools
Dispute Management	@Promesse Ishimwe	#ws-dispute-management
PISP 2.0	@Paul Baker	#ws-pisp2_0
Payments Addressing	@Arunjay, Clare Rowley	#ws-payments-addressing
FX Refinement	@Paul Baker	#ws-fx-refinement
Non-Mojaloop Interscheme	@Julie Guetta	#ws-interscheme
ISO 20022 Refinement	@Julie Guetta	#ws-iso20022
Refactor Bulk Payments	@Paul Baker	#ws-bulk
Settlement 3.0 and TB Integration	@James Bush	#ws-tb-integration
Timezone Localisation	@Luis Roy Zulu	#ws-localization-pi24
Mojaloop Evolution: Integrating the Outputs of the vNext Program	@James Bush	#ws-mojaloop-evolution
Performance Optimisation	@Julie Guetta	#ws-performance-characterisation
Platform Quality and Security	@Sam	#ws-pqs-pi26
Core and Releases	@Sam	#ws-ml-core-and-releases-pi26

Mojaloop Roadmap

Paul Makin — Tue, 26 Nov 2024 16:37:44 +0000

The Mojaloop Roadmap has been updated for PI 26, following a review of the PI 25 work streams and feedback from the recent Convening/Community Meeting, which included the identification of emerging requirements and their prioritisation and placement on the roadmap.

You can download the roadmap from here in SVG or PNG format, and the source file can also be viewed here.

PISP SDK: New Sub-Workstream

Paul Makin — Mon, 23 Sep 2024 09:45:33 +0000

After the recent Product Council session discussing the proposal for an Open Banking SDK for use by fintechs and others wishing to use Mojaloop’s PISP interface, a new sub-workstream has been initiated as part of the overall “Participation Tools” workstream.

This sub-workstream is being led by Alain Kajangwe of WiredIn, and I hope that anyone with an interest in promoting the use of PISP will join the workstream. Alain will be scheduling regular update calls, and I imagine he’ll be publishing details in due course.

Given that we are now halfway through the PI, we do not expect that this new workstream will be able to fully deliver on its objectives by the time of the Convening in November!

PI 25: Mid PI Review

Paul Makin — Thu, 19 Sep 2024 15:05:38 +0000

Next week's Product Council, scheduled for Tuesday 24th September at 11:00 UTC, will be the venue for the PI 25 Mid PI Review. The leads of all of the PI 25 workstreams are asked to attend, and give an update on the progress of the workstream against the stated objectives for the PI, to give an indication of what they think the workstream will achieve by the end of the PI (mid November), and to highlight any roadblocks they are facing.

The proposed running order is:

Workstream	Lead
Participation Tools	James Bush
Merchant Payments	Karim Jindani
Interscheme	Julie Guetta, Paul Baker
On Premise Deployments	Sam Kummary, James Bush
ISO 20022	Julie Guetta, Michael Richards, Paul Baker
FX	Paul Baker, Michael Richards
Localisation	Luis Roy Zulu
vNext	Julie Guetta
Performance Optimisation	James Bush
Platform Quality & Security	Sam Kummary
Core & Releases	Sam Kummary

You'll find joining instructions on the #product-council channel on the Mojaloop Slack.

Look forward to seeing you all there.

Updated Workstream Dashboard

Paul Makin — Mon, 16 Sep 2024 14:53:26 +0000

I've updated the workstream dashboard as below, to reflect the changes in the roadmap.

Updated Roadmap

Paul Makin — Mon, 16 Sep 2024 14:49:46 +0000

I've updated the roadmap, removing those workstreams that haven't attracted contributions during this PI and moving them to a "candidates" list for consideration for adoption in a future PI.

Should the need for these workstreams become more urgent, they will be reinstated in the roadmap.

The roadmap is available in the Mojaloop GitHub, in the Product Council repo.

The Process Towards vNext Adoption - An Update

Paul Makin — Thu, 12 Sep 2024 08:09:19 +0000

To provide clarity on the Mojaloop Foundation's vNext release, the Foundation would like to outline the progress made since Paul Makin detailed the adoption plan. As a reminder, vNext is a technical rewrite of the Mojaloop platform, designed to further enhance scalability and maintainability through the use of TypeScript, and reduce operating costs. It is the practical implementation of the Mojaloop Reference Architecture.

Alpha Release: The first alpha version, released mid 2023, was feature-incomplete and intended strictly for evaluation by the Mojaloop Community. It was not suitable for Proof of Concept (PoC) or production use.
Beta Release: A beta version released December 2023 was reviewed by the Mojaloop team, with feedback documented in the Mojaloop vNext Path to Release Candidate Report (Feb 2024). This version remains incomplete, lacking critical use cases like Request-to-Pay, Third Party Payment Initiation, and security features. As a result, it will not be used for PoC deployments managed by the Foundation.
Release Candidate: A list of tasks required to make vNext a release candidate for PoC and production has been established, and a snapshot can be viewed here. These tasks include achieving feature parity and completing all Mojaloop release quality checks.

The Mojaloop Foundation is fully committed to advancing vNext. A dedicated workstream, led by James Bush, was launched in late 2023, and a transition manager (initially Jane Stroucken, followed by Julie Guetta) was hired in March 2024. to organize efforts and guide contributors in completing the critical tasks.

While the Foundation’s Engineering Director and Technical Director are focusing on key tasks, additional engineering resources are urgently needed to finalize vNext. If you’re interested in contributing, please join the conversation on:

Mojaloop Slack: #vnext-build

Zenhub board: Here

For any questions on deployment strategies, please contact Steve Haley, responsible for Mojaloop Foundation deployments or Julie Guetta, Transition Manager for vNext to provide guidance to potential adopters.

(Thank you to Julie for drafting this post)