Over the past several years, the use of API’s for inter-system access has proliferated. These have been provided as a means for one system to easily access resources in another system: often, the two systems are “legacy” systems, and the API’s are layers on top of those systems.
Today, newly written systems are designed to be “API First”. The Level One Project, recognizing the importance of this as an enabling factor in allowing DFSPs to participate in a Level One platform, worked with industry stakeholders to create the “Open API Specification”. This specification was written from the perspective of mobile money providers to enable the creation of a Level One-aligned payment platform.
The Mojaloop FSP Interoperability API Specification is publicly available at https://mojaloop.io/documentation/api/
Use Cases Supported by Mojaloop FSP
P2P: An individual End User initiates a transaction to send money to another individual End User who doesn’t belong to the same FSP of the sender.
Agent Initiated Cash-In: A customer requests an agent of different FSP to cash in his/her mobile money account.
Agent Initiated Cash-Out: A customer requests an agent of different FSP to cash out his/her mobile money account.
Agent Initiated Cash-Out Authorized on POS: A customer requests an agent of different FSP to cash in his/her mobile money account. In this use case, the agent initiates the transaction through POS or ATM.
Customer Initiated Cash-Out: A registered customer initiates a transaction to withdraw cash from an agent who doesn’t belong to the same FSP of him/her.
Customer Initiated Merchant Payment: An individual End User initiates a purchase transaction to pay a merchant who doesn’t belong to the same FSP of the customer.
Merchant Initiated Merchant Payment: A Merchant initiates a request to pay for the Customer, the Customer reviews the request for transaction amount and confirm the request by providing authentication on own handset.
Merchant Initiated Merchant Payment Authorized on POS: A Merchant initiates a request to pay for the Customer, the Customer review the payment request on Merchant device and authorize the payment by OTP or QR code on Merchant device itself.
ATM Initiated Cash-Out: An ATM initiates a cash-out request from a customer account; the customer confirms the request by providing authentication (OTP) on ATM device.
Bulk Payments: An organization or business is able to group individual transactions together into one bulk transaction. The organization can validate individual transactions before the bulk is executed and follow up on the result of the individual transactions.
Refund: The business flow for how to refund a completed interoperability transaction.
Next Topic in this Section: Mojaloop Community Business Documents