We are excited to announce the latest Mojaloop release! With this release, support for organizations managing bulk disbursements and using non-Latin-based characters in names is available. Additionally, the implementation of Financial Service Provider Interoperability (FSPIOP) API v1.1 improves flexibility for financial institutions to conduct two-phase commits on funds, further reducing reconciliation risk.
This release, packaged in Helm and committed to the Helm GitHub repository, includes a set of core and supporting services that make up a Mojaloop Hub implementation. To learn more about what a Helm release means, versioning methodology, and its usage in the Mojaloop program, check out this blog. For additional information about Mojaloop versioning conventions, you can find helpful documentation on mojaloop.io.
Below, we highlight some of the significant changes implemented in this release. For details, including breaking changes, new features, bug fixes, and more, check out the Mojaloop release notes for Mojaloop v10.4.0.
This release was the first to utilize Mojaloop Simulator postman collection (v10.4.0) with JWS signing enabled, to validate the Helm release and corresponding deployments. The new changes fall into three main categories: support for FSPIOP API v1.1 changes, Bulk Transfers, and other maintenance updates.
The FSPIOP API v1.1 changes included: Notifying a payee’s FSP upon a successful commit in the switch, adding ExtensionList fields to existing data structures, and clarified usage of the “ABORTED” transfer state in a PUT /transfers/<ID>. For details regarding these changes, please read this blog post.
Bulk Payments is a very critical use case for countries, markets, and payment systems. This is especially true during emergencies, or pandemics like the world is experiencing now. During Program Increment 10, the team implemented changes to support various error scenarios and querying the bulk transfer status along with tests to validate them. With this change, all primary resources in the FSP Interoperability API and all types of use cases have been successfully implemented. The community will now shift its planning and design toward easing the burden on Financial Service Providers around bulk processing.
Support for “on-us” transfers and “accented” characters
The current Mojaloop Hub implementation supports “on-us” transfers. These are transfers in which the Payer and Payee of funds belong to the same FSP. With this release, Mojaloop schemes now have the option to choose whether or not to support “on-us” transfers in their system, as this is a configurable option. This has been a frequent request from the Mojaloop Community as it represents substantial cost savings to many FSPs who prefer to simplify their implementations.
Coming up next
The Mojaloop Community adopted a pure semantic versioning model beginning in Program Increment 11 (PI-11), which officially began during the Community Event that took place July 20-24. The community is now working on PI-11 objectives and maturing the platform. The releases for each service will be included in the upcoming Mojaloop release (v11.0.0).
You can learn more about this project on our Mojaloop overview page or by visiting our Mojaloop Partner Program. You’ll find additional information about how to get involved in the Mojaloop community, advantages of the Mojaloop Lab, and you can sign up for our courses.