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

Client-level APIs to enable client with permissions and data scoping as authenticated users

Supports following use cases:

Self-Service Portals: web-based online banking interface, SMS/USSD information portal for inbound SMS & pull notifications, client-facing direct banking smartphone app
USSD/SMS interfaces for initiating transactions
Agent-based models: agent banking, PAYG

Customer	Location	Description	USSD Interface	Self Service - Mobile	Self Service - Web	Mobile Wallet	Agent
Financial Institution Name	Country	Overview of Requirements	Processes to be supported	Processes to be Supported		Processes...	Processes...
Musoni Services				Android-based client being built by JP Morgan
Grooming MF	Nigeria
Upscale Consultancy Services		For the NBFC, they need to do a lot of pre-boarding for their client (lead generation) via self-service channels.		Self Service Mobile App - direct sales app which will allow for clients to apply for and upload KYC documents for loan applications.	Self Service Web App - direct sales web app which allow clients to apply for loans.
ePay Kenya	Kenya
PayGoSol (Ensibuuko)	Uganda
Omexit	Kenya	Building USSD application and front and back-end for one of clients. Too steep of learning curve to understand all of Mifos X so just started building apps. Plans to port over to Mifos X/LF	Front-end USSD application that communicates to back-end service for Checking loan status Checking what need to pay Reminders/SMS Client can choose from menu of loan products
CashCare India	India	E-commerce credit services		Access to customers to view their basic details and do a lot of self service activities from their machines.
Elevate Africa		Inbound SMS		Self-Service via USSD or SMS, i.e. send shortcodes to number to retrieve account balances, etc.

#	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

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

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

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