View Source

Target release	Mifos X 16.xx
Epic	Link to related JIRA epic or feature
Document status
Document owner	Ed Cable
Designer	Lead designer
Developers	Lead developer
QA	Lead tester

Goals

Integrate Mifos with mobile money platforms so data can be synchronized with the disbursements, repayments, and deposits being initiated through the mobile money platform.
It can enable financial institutions to go completely paperless once mobile money is rolled out and integrated with the core banking system.

Background and strategic fit

Mobile Money is in high demand across Mifos users worldwide yet it still has not been as widely adopted by our customer base because of the need for access to Open APIs from the mobile money providers and hence our ability to integrate with their mobile money systems.

Integration from a technical standpoint once the API is made available from the mobile money provider isn't a large amount of work but getting the specific use cases and requirements needed for mobile money integration is critical and we can only move forward if users and partners in the community express the specific requirements they have. Musoni Services has integrated with various mobile money providers throughout Sub-Saharan Africa via Musoni System which is built on top of the Mifos X platform

The following provides good background on mobile money integration:

CGAP on Open APIs - http://www.cgap.org/blog/can-open-apis-accelerate-digital-finance-ecosystem
- http://www.cgap.org/blog/partnership-missing-ingredient-mobile-money-apis
Safaricom M-Pesa API Guide & Documentation: http://www.safaricom.co.ke/business/m-pesa/api
Specs for Mifos 2 Mobile Money Integration (File-Level API integration for M-Pesa)
- MPESA Loan Repayments and Savings Deposits Functional Spec v2
- MPESA Loan Disbursals Functional Spec
Mobile Money Providers by Region (spreadsheet research led by GCI students)
- https://docs.google.com/spreadsheets/d/1j1YPXP_Cy1g8YTIjnAXBflGYdPRiug7MlWlw8Zhky8I/edit?usp=sharing
Notes from on M-Pesa Requirements
- /wiki/spaces/~dharp@harpcreek.com/pages/90898481

Assumptions

Requirements must be driven by implementation by a specific customer or partner
Preference is to do API-level integration if available, will only do file-level integration if that is the option.

Customers

Customer	Location	Description	Status	Mobile Money Provider	API or File-Level	USSD Gateway
Financial Institution Name	Country	Overview of Requirements
Intrasoft Technologies	Kenya			M-Pesa (Safaricom)	File-Level but access to APIs is now available
Digamber Finance
Nuru International
Esperanza				Required		Required
Valee SACCO	Uganda		In Development by Omexit	Airtel Money MTN Money	API but only through integrators - working with Beyonic. Alternatives are Yo Pay.
Cameroon - Emmanuel Nganyu	Cameroon		In Discussion		API but access is slowly opening up.
World Relief	Rwanda			TigoCash
	Tanzania

Requirements

#	Title	User Story	Importance	Notes
1	Short identifier for the story	Describe the user and what they are trying to achieve	Must Have	Additional considerations or noteworthy references (links, issues)
2

User interaction and design

Include any mockups, diagrams or visual designs relating to these requirements.

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
(e.g. How we make users more aware of this feature?)	Communicate the decision reached

Not Doing

List the features discussed which are out of scope or might be revisited in a later release.