Info | ||
---|---|---|
| ||
Mifos is applying to be a mentoring org for the tenth time. Applications are due February 19, 2021 and accepted orgs will be announced March 9, 2021. Please check this page for updates to our ideas list and mentor assignments for anticipated projects. Project will be of shorter duration this year and the ideas list reflects the new GSOC format. |
...
Mentor | Project | Location | Time Zone | ||||
---|---|---|---|---|---|---|---|
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | Afghanistan | IST (GMT+4:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Fineract CN | Cameroon | WAT (GMT +1:00) | ||||
| Platform | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Platform | India | IST (GMT +5:30) | ||||
| Platform | Mexico | CST (GMT -6:00) | ||||
Raul Sibija | Platform | Mexico | CST (GMT -6:00) | ||||
Karina Ortiz | Platform | Mexico | CST (GMT -6:00) | ||||
Gustavo Espindola | Mobile | Mexico | CST (GMT -6:00) | ||||
| Platform | India | IST (GMT +5:30) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Platform | USA | CST (GMT -6:00) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Platform | India | IST (GMT +5:30) | ||||
| Mobile | India | IST (GMT +5:30) | ||||
| Web | India | IST (GMT +5:30) | ||||
| Platform | Serbia | CET (GMT +1:00) | ||||
| Platform | india | IST (GMT +5:30) | ||||
| Platform | India | IST (GMT +5:30) | ||||
| Fineract CN | Cameroon | WAT (GMT + 1:00) | ||||
| Web | India | IST(+5:30) |
...
- Architectural White Paper: https://goo.gl/du7XhL
- API Docs: https://demo.mifos.io/api-docs/apiLive.htm
- Web Hooks framework: https://cwiki.apache.org/confluence/display/FINERACT/Hooks
- Platform - Apache Fineract: Source Code | Issue Tracker | Mailing List
- Web App - Mifos X: Source Code | Issue Tracker | Mailing List | Gitter Chatroom
- Mobile App - Android Field Officer App: Source Code | Issue Tracker | Gitter Chatroom
- Mifos Mobile - Android Mobile Banking App: Source Code | Issue Tracker | Gitter Chatroom
- Online Banking App - Web: Source Code | Issue Tracker | Gitter Chatroom
- MifosPay - Mobile Wallet Framework: Source Code | Issue Tracker | Gitter Chatroom
- Mifos Payment Hub EE: Source Code | Issue Tracker | Gitter Chatroom
- OpenG2P: https://github.com/openg2p
Hints
- When you need help, ask for help after exploring all options on the web. We are very excited for you to join us, but we need to know that you're willing to put in the time and effort required to do your part. When you do ask, ask well.
- Tips for a Good Application from former GSOC intern and Mentor, Ishan Khanna: https://hackernoon.com/7-things-you-need-to-know-to-ace-your-gsoc-proposal-8e422f2b6abe
- Not sure if you are qualified? Download and build the code, then run the Platform and the Mifos X distribution.
- Instructions for running the platform are in Getting Started Guide in the Apache Fineract Contributor's Zone
- Getting started with the web app can be found in the Getting Started Guide
- Email the mifos-developer mailing list with your questions and project ideas.
- Install Skype for (generally infrequent) video calls. You'll need a headset for Skype, too.
- Get started by solving few issues on Fineract here or for the web app here.
Project Ideas
Info | ||
---|---|---|
| ||
Our 2021 Ideas lists is currently being refined. Stay tuned for additional updates. |
All 2020 projects will be related to the Mifos X Web App, our mobile apps including our Android Field Operations app, our Mobile Banking app, or our Mobile Wallet App or our Online Banking App. There will also be projects focused on our payment hub and integrations with open source real-time payments platform - Mojaloop and integrations with the GSMA mobile money API and our Open Banking API. Some projects will also center directly around the Apache Fineract platform for financial inclusion and additional tools, features, or modules on that and our brand-new Apache Fineract CN application framework for digital financial services as well as the mobile apps connecting to Fineract CN. These apps and modules are built on top of the Apache Fineract platform, the world's only open platform for financial inclusion and is banking delivered as a service via the cloud. Apache Fineract is a true platform in which the back-end is cleanly separated from the front-end and all core platform services are exposed through an API making it easy develop new applications on top of the Apache Fineract platform.
Functional Enhancements to Mobile Wallet
Mentors | |
Category | Mobile - Mifos X |
Overview & Objectives | We provide a reference mobile wallet application for consumers and merchants that has been developed by our Google Summer of Code interns from 2017 to 2020. The mobile wallet provides an extensible mobile wallet framework to support the basic use cases of a mobile wallet as documented in the Level One Project mobile wallet requirements. This extensible framework should support both merchant and client use cases as well as be capable of integrating with a Fineract or Fineract CN back-end. Over time, we would like Mifos X to be more generically a wallet management system and this reference application is a powerful tool to support that. |
Description | In 2021 we aim to complete an MVP of a mobile wallet on top of the Fineract CN back-end so most of the major work will be around Fineract CN and Payment Hub integration and improving peer to peer and merchant transactions (initiating transactions to merchants, maintaining history of users with which recent transactions took place, adding deeplink support for unique payment links, payment related notifications using FCM). Payment Hub and Mojaloop integration will allow us to make payments across tenants and fineract deployments. A very basic integration of payment hub with mobile wallet is already in work but that will need to be extended to fully support all use cases. Functional enhancements include:
|
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin |
Impact | By providing an extensible mobile wallet framework, allow partners a complete reference stack of back and front-end applications to offer digital financial services to clients. |
Other Resources | 2020 Mobile Wallet Progress: https://gist.github.com/devansh-299/e2041c07d9ab55a747391951e9090df4 Mobile Wallet Framework: Source Code | Issue Tracker | Gitter Chatroom |
Technical Enhancements to Customer-Facing Apps
Mentors | |
Category | Mobile - Mifos X |
Overview & Objectives | We provide a reference mobile wallet application for consumers and merchants that has been developed by our Google Summer of Code interns from 2017 to 2020. The mobile wallet provides an extensible mobile wallet framework to support the basic use cases of a mobile wallet as documented in the Level One Project mobile wallet requirements. This extensible framework should support both merchant and client use cases as well as be capable of integrating with a Fineract or Fineract CN back-end. We also provide reference mobile banking apps for both Fineract 1.x and Fineract CN This project would center around technical enhancements to these three customer-facing mobile applications. |
Description | Technical enhancements to customer-facing apps include:
|
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin |
Impact | Transitioning to Kotlin enables multi-platform development capability and wider spread adoption of customer-facing apps. |
Other Resources | 2020 Technical Enhancements : https://gist.github.com/ashwinkey04/7bea77a5b5880023234b04dd68214c66 Mobile Wallet Framework: Source Code | Issue Tracker | Gitter Chatroom Mifos Mobile - Android Mobile Banking App: Source Code | Issue Tracker | Gitter Chatroom |
UI and Design Enhancements to Customer-Facing Apps
Mentors | |
Category | Mobile - Mifos X |
Overview & Objectives | Our suite of customer-facing mobile applications include our mobile wallet framework, and mobile banking apps for Fineract 1.x and Fineract CN. These are designed to serve as reference implementations for demonstration purposes but also to act as secure and robust starting dough that can be extended and enhanced and white-labeled. With the move towards more digital financial services, these reference solutions are ever more important and critical and must appear highly polished, clean, and professional. We are working with a designer to provide a set of clean, consistent and professional UI designs and workflows to implement across our customer-facing apps. This project would focus on implementing these new designs across the customer-facing apps providing a consistent and familiar look and feel. It will build off of efforts in 2020 implementing the UI designs previously proposed during GCI. |
Description | This project would focus on implementing these new designs across the customer-facing apps providing a consistent and familiar look and feel. It will build off of efforts in 2020 implementing the UI designs previously proposed during GCI. We provide a reference mobile wallet application for consumers and merchants that has been developed by our Google Summer of Code interns from 2017 to 2020. Design enhancements to customer-facing apps include:
|
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin |
Impact | A clean and simple UI is key for our low-tech audience and professional and consistent look and feel enhances credibility of our stack. |
Other Resources | 2020 UI Enhancements: https://gist.github.com/ShivangiSingh17/67b6041387c1e281caa7df23347f549e Mobile Wallet Framework: Source Code | Issue Tracker | Gitter Chatroom Mifos Mobile - Android Mobile Banking App: Source Code | Issue Tracker | Gitter Chatroom |
Functional Enhancement to Fineract CN Mobile
Mentors | |
Category | Mobile - Apache Fineract CN |
Overview & Objectives | Just as we have a mobile field operations app on Apache Fineract 1.x, we have recently built out on top of the brand new Apache Fineract CN micro-services architecture, an initial version of a mobile field operations app with an MVP architecture and material design. Given the flexibily of the new architecture and its ability to support different methodologies - MFIs, credit unions, cooperatives, savings groups, agent banking, etc - this mobile app will have different flavors and workflows and functionalities. |
Description | In 2020, our Google Summer of Code intern worked on additional functionality in the Fineract CN mobile app. In 2021, the student will work on the following tasks:
|
Helpful Skills | Android developmentDevelopment, SQLKotlin, Java, Javascript, Git, Spring, OpenJPA, Rest ,API |
Impact | Allows staff to go directly into the field to connect to the client. Reduces cost of operations by enabling organizations to go paperless and be more efficient. |
Other Resources |
|
JIRA Task |
Create Open Banking API Layer for Mifos Mobile
Mentors | |
Category | Mobile/Platform |
Overview & Objectives | Across our ecosystem we're seeing more and more adoption and innovation from fintechs. A huge democratizing force across the financial services sector is the Open Banking movement providing Open Banking APIs to enable third parties to directly interact with customers of financial institutions. We have recently started providing an Open Banking API layer that will allow financial institutions using Mifos and Fineract to offer third parties access to requesting account information and initiating payments via these APIs. Most recently the Mojaloop community, led by Google, has led the development of a centralized PISP API. We have chosen to the folow the comprehensive UIk Open Banking API standard which is being followed and adopted by a number of countriues through Sub-Saharan Africa and Latin America. Tremendous impact can be had at the Base of the Pyramid by enabling third parties to establish consent with customers authorize transactions to be initiated or information to be accessed from accounts at their financial institution. This Open Banking API layer would enable any instituion using Mifos or Fineract to provide a UK Open Banking API layer to third parties and fintechs. The API Gateway to connect to is still being chosen (WS02, Gravitee, etc.) |
Description | Mifos Mobile API Matrix (completed by Ashwin) MIfos Mobile API Matrix (completed by Shivangi) |
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin, Gravitee, WSO2 |
Impact | By providing a standard UK Open Banking API layer we can provide both a secure way for our trusted first party apps to allow customers to autheniticate and access their accounts as well as an API layer for third party fintechs to securely access FIneract and request information or initiate transactions with the consent of customers. |
Other Resources | CGAP Research on Open Banking: https://www.cgap.org/research/publication/open-banking-how-design-financial-inclusion Docs: https://mifos.gitbook.io/docs/wso2-1/setup-openbanking-apis Self-Service APIs: https://demo.mifos.io/api-docs/apiLive.htm#selfbasicauth Open Banking Adapter: https://github.com/openMF/openbanking-adapte
Reference Open Banking Fintech App:
Google Whitepaper on 3PPI: https://static.googleusercontent.com/media/nextbillionusers.google/en//tools/3PPI-2021-whitepaper.pdf UK Open Banking API Standard: https://standards.openbanking.org.uk/ Open Banking Developer Zone: https://openbanking.atlassian.net/wiki/spaces/DZ/overview Examples of Open Banking Apps: https://www.ft.com/content/a5f0af78-133e-11e9-a581-4ff78404524e |
Create Open Banking API Layer for Mifos Mobile CN
Mentors | |
Category | Mobile/Platform |
Overview & Objectives | Across our ecosystem we're seeing more and more adoption and innovation from fintechs. A huge democratizing force across the financial services sector is the Open Banking movement providing Open Banking APIs to enable third parties to directly interact with customers of financial institutions. We have recently started providing an Open Banking API layer that will allow financial institutions using Mifos and Fineract to offer third parties access to requesting account information and initiating payments via these APIs. Most recently the Mojaloop community, led by Google, has led the development of a centralized PISP API. We have chosen to the folow the comprehensive UIk Open Banking API standard which is being followed and adopted by a number of countriues through Sub-Saharan Africa and Latin America. Tremendous impact can be had at the Base of the Pyramid by enabling third parties to establish consent with customers authorize transactions to be initiated or information to be accessed from accounts at their financial institution. This Open Banking API layer would enable any instituion using Mifos or Fineract to provide a UK Open Banking API layer to third parties and fintechs. The API Gateway to connect to is still being chosen (WS02, Gravitee, etc.) |
Description | |
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin, Gravitee, WSO2 |
Impact | By providing a standard UK Open Banking API layer we can provide both a secure way for our trusted first party apps to allow customers to autheniticate and access their accounts as well as an API layer for third party fintechs to securely access FIneract and request information or initiate transactions with the consent of customers. |
Other Resources | CGAP Research on Open Banking: https://www.cgap.org/research/publication/open-banking-how-design-financial-inclusion Docs: https://mifos.gitbook.io/docs/wso2-1/setup-openbanking-apis Self-Service APIs: https://demo.mifos.io/api-docs/apiLive.htm#selfbasicauth Open Banking Adapter: https://github.com/openMF/openbanking-adapte
Reference Open Banking Fintech App:
Google Whitepaper on 3PPI: https://static.googleusercontent.com/media/nextbillionusers.google/en//tools/3PPI-2021-whitepaper.pdf UK Open Banking API Standard: https://standards.openbanking.org.uk/ Open Banking Developer Zone: https://openbanking.atlassian.net/wiki/spaces/DZ/overview Examples of Open Banking Apps: https://www.ft.com/content/a5f0af78-133e-11e9-a581-4ff78404524e |
Create Open Banking API Layer for Mobile Wallet
Mentors | |
Category | Mobile/Platform |
Overview & Objectives | Across our ecosystem we're seeing more and more adoption and innovation from fintechs. A huge democratizing force across the financial services sector is the Open Banking movement providing Open Banking APIs to enable third parties to directly interact with customers of financial institutions. We have recently started providing an Open Banking API layer that will allow financial institutions using Mifos and Fineract to offer third parties access to requesting account information and initiating payments via these APIs. Most recently the Mojaloop community, led by Google, has led the development of a centralized PISP API. We have chosen to the folow the comprehensive UIk Open Banking API standard which is being followed and adopted by a number of countriues through Sub-Saharan Africa and Latin America. Tremendous impact can be had at the Base of the Pyramid by enabling third parties to establish consent with customers authorize transactions to be initiated or information to be accessed from accounts at their financial institution. This Open Banking API layer would enable any instituion using Mifos or Fineract to provide a UK Open Banking API layer to third parties and fintechs. The API Gateway to connect to is still being chosen (WS02, Gravitee, etc.) |
Description | |
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin, Gravitee, WSO2 |
Impact | By providing a standard UK Open Banking API layer we can provide both a secure way for our trusted first party apps to allow customers to autheniticate and access their accounts as well as an API layer for third party fintechs to securely access FIneract and request information or initiate transactions with the consent of customers. |
Other Resources | CGAP Research on Open Banking: https://www.cgap.org/research/publication/open-banking-how-design-financial-inclusion Docs: https://mifos.gitbook.io/docs/wso2-1/setup-openbanking-apis Self-Service APIs: https://demo.mifos.io/api-docs/apiLive.htm#selfbasicauth Open Banking Adapter: https://github.com/openMF/openbanking-adapte
Reference Open Banking Fintech App:
Google Whitepaper on 3PPI: https://static.googleusercontent.com/media/nextbillionusers.google/en//tools/3PPI-2021-whitepaper.pdf UK Open Banking API Standard: https://standards.openbanking.org.uk/ Open Banking Developer Zone: https://openbanking.atlassian.net/wiki/spaces/DZ/overview Examples of Open Banking Apps: https://www.ft.com/content/a5f0af78-133e-11e9-a581-4ff78404524e |
Create Open Banking API Layer for Online Banking App
Mentors | |
Category | Mobile/Platform |
Overview & Objectives | Across our ecosystem we're seeing more and more adoption and innovation from fintechs. A huge democratizing force across the financial services sector is the Open Banking movement providing Open Banking APIs to enable third parties to directly interact with customers of financial institutions. We have recently started providing an Open Banking API layer that will allow financial institutions using Mifos and Fineract to offer third parties access to requesting account information and initiating payments via these APIs. Most recently the Mojaloop community, led by Google, has led the development of a centralized PISP API. We have chosen to the folow the comprehensive UIk Open Banking API standard which is being followed and adopted by a number of countriues through Sub-Saharan Africa and Latin America. Tremendous impact can be had at the Base of the Pyramid by enabling third parties to establish consent with customers authorize transactions to be initiated or information to be accessed from accounts at their financial institution. This Open Banking API layer would enable any instituion using Mifos or Fineract to provide a UK Open Banking API layer to third parties and fintechs. The API Gateway to connect to is still being chosen (WS02, Gravitee, etc.) |
Description | Mifos Mobile API Matrix (completed by Ashwin) MIfos Mobile API Matrix (completed by Shivangi) |
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin, Gravitee, WSO2, Angular |
Impact | By providing a standard UK Open Banking API layer we can provide both a secure way for our trusted first party apps to allow customers to autheniticate and access their accounts as well as an API layer for third party fintechs to securely access FIneract and request information or initiate transactions with the consent of customers. |
Other Resources | CGAP Research on Open Banking: https://www.cgap.org/research/publication/open-banking-how-design-financial-inclusion Docs: https://mifos.gitbook.io/docs/wso2-1/setup-openbanking-apis Self-Service APIs: https://demo.mifos.io/api-docs/apiLive.htm#selfbasicauth Open Banking Adapter: https://github.com/openMF/openbanking-adapte
Reference Open Banking Fintech App:
Google Whitepaper on 3PPI: https://static.googleusercontent.com/media/nextbillionusers.google/en//tools/3PPI-2021-whitepaper.pdf UK Open Banking API Standard: https://standards.openbanking.org.uk/ Open Banking Developer Zone: https://openbanking.atlassian.net/wiki/spaces/DZ/overview Examples of Open Banking Apps: https://www.ft.com/content/a5f0af78-133e-11e9-a581-4ff78404524e |
Open Banking Fintech App Framework
Mentors | |
Category | Mobile |
Overview & Objectives | Across our ecosystem we're seeing more and more adoption and innovation from fintechs. A huge democratizing force across the financial services sector is the Open Banking movement providing Open Banking APIs to enable third parties to directly interact with customers of financial institutions. We have recently started providing an Open Banking API layer that will allow financial institutions using Mifos and Fineract to offer third parties access to requesting account information and initiating payments via these APIs. Most recently the Mojaloop community, led by Google, has led the development of a centralized PISP API To demonstrate these Open Banking APIs and use cases that third parties and fintechs can provide we have developed a cross-platform reference mobile app on Kotlin to showcase a number of these features. It currently connects with the Open Bank Project that adheres to the UK Open Banking API standard. The API Gateway to connect to is still being chosen (WS02, Gravitee, etc.) The breadth and variety of apps that could be built leveraging these APIs from region to region is endless. We would like this app to be built in an extensible and modular fashion such that core libraries and components could be re-used across different use cases with this framework as the foundation and multiple reference apps on top. Applications include personal financial management apps aggregating information from multiple bank accounts in one place, wallet apps allowing payments to be made from different banks, lending apps, leveraging data and insight from multiple accounts, savings apps, etc. |
Description | |
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, Kotlin |
Impact | By providing an extensible open banking fintech app framework, allow partners a complete stack of Open Banking APIs and reference front-end application to rapidly build innovation via Open Banking APIs. |
Other Resources | 2020 Progress: https://gist.github.com/ankurs287/4ef7c3de462073bf36bd5247479cb176 Google Whitepaper on 3PPI: https://static.googleusercontent.com/media/nextbillionusers.google/en//tools/3PPI-2021-whitepaper.pdf UK Open Banking API Standard: https://standards.openbanking.org.uk/ Open Banking Developer Zone: https://openbanking.atlassian.net/wiki/spaces/DZ/overview Examples of Open Banking Apps: https://www.ft.com/content/a5f0af78-133e-11e9-a581-4ff78404524e |
Digital Bank UI on Fineract CN
Mentors | Gaurav Saini, Pranjal Goswami, @Giorgio Zoppi |
Category | Web - Fineract CN Web App |
Overview & Objectives | A new reference user interface on Fineract CN for staff of financial institutions such as digital, challenger, and neo-banks that focused on individual accounts is needed for multiple reasons:
|
Description | Intern will implement the front-end UI screens for the Fineract CN web UI for the following functionalities and use case:
|
Helpful Skills | Javascript, CSS, HTML5. Angular and Bootstrap (CSS framework) is plus |
Impact | Reference UI for microfinance institutions on Apache Fineract CN |
Other Resources | Use Cases - https://github.com/openMF/digital-bank-ui/wiki/Use-Cases-&-Requirements 2020 Progress: https://gist.github.com/abhi40308/21cf6f1ac78efe309faaf6a0d6d971e4 |
Github |
Mifos X Web App Enhancements
Mentors | |
Category | Web - Mifos X Web App |
Overview & Objectives | Our AngularWeb App is the standard application on the Mifos X distribution that provides all the core functionality for the most common methods of financial inclusion and products and services. It's also the starting point for any partners looking to customize or extend the UI. It's constantly being improved based on user feedback, better performance, and to integrate new design standards. |
Description | In 2018, we made the decision to re-write the entire Mifos X web app from Angular 1.75 to Angular 6 providing cleaner Material design, access to brand new libraries, better theming/skinnability, and a more stable and modern codebase. In 2019 we continued the re-write and upgraded to Angular 7. In 2020 we upgraded to Angular 9 and continued the rewrite. The re-write is nearly complete and now just needs to focus on a few minor remaining enhancements and optimizations. You can see the in-progress new UI at https://openmf.github.io/web-app/ (mifos/password) The remaining issues can be found: https://github.com/openMF/web-app/issues The progress is being tracked here: https://docs.google.com/spreadsheets/d/1JxeJjG1GdZ3BNJi-sScCQLirfevSc8amFr8o3SfUj4U/edit?usp=sharing Some additional work also includes adding in comprehensive keyboard shortcuts to enable power-users of the app and to ensure that the tabs and arrow keys work appropriately for navigating through the app, localization support, additional dashboards, adding of tooltips, etc. |
Helpful Skills | Javascript, SCSS, HTML5, Angular 9, Angular Material, Flex Layout |
Impact | Enhanced User Experience, Intuitive application design 2020 Progress: https://gist.github.com/karantakalkar/7a4acb83f31ebfe4f3b827c86c67eec0 https://gist.github.com/muskankhedia/b0929cbf2ae6236bfe07964a140da179 |
Other Resources | Usability and Design |
Improve Robustness of Mifos X and Apache Fineract by Fixing Issues/Feature Requests in Backlog
Mentors | |
Category | Platform |
Overview & Objectives | Mifos X and Apache Fineract is widely used by financial institutions of all different sizes and methodologies around the world. With that widespread user base there is a vast array of different processes and procedures that would like to be supported as slight modifications over the common functionality provided. Over the past several years, we have captured these minor enhancements in our issue tracker as feature requests. Also included in this backlog or additional minor and less critical bugs that have been reported but have not been fixed yet. This backlog has grown and it would be a very impactful project for an intern to work on completing as many of these bug fixes and minor enhancement as possible. The difficult level of these issues ranges from low to higher and touch all componets of the platform - most don't require too much domain knowledge but some will. |
Description | We have groomed the backlog and tagged issues and feature requests that are relevant for this project with the labels gsoc and/or Volunteer. Priority level of tasks is measured by p1 being the highest priority. Tasks with an assigned fix version of either 1.4.0 or 1.5.0 have a higher priority. There are more than 120 tickets in the saved filter. You are not expected to complete all of the tasks in the backlog but throughout the internship you should fix as many issues/feature requests as possible. You will work with your mentor to deliver a plan for each sprint and adjust velocity as you get scaled up. Issues to be worked on can be found at https://issues.apache.org/jira/issues/?filter=12345785 - the saved filter is named 2021 Intern Project. |
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, Javascript, SQL |
Impact | Better internal control and financial transparency |
Other Resources | Getting Started with Apache Fineract: https://cwiki.apache.org/confluence/display/FINERACT/Getting+Started+Docs |
OpenG2P - Digital Identity Proof of Concept on Sovrin & Hyperledger Indy
Mentors | Rachit Kansal |
Category | Platform & Modules |
Overview & Objectives | Digital Identity is a pressing topic and for both generations of Fineract (1.x and CN), we'd like to have integration with emerging KYC and digital identity solutions. KYC (Know your customer) is a fundamental banking concept. It refers to the process of identifying a new customer at the time of account opening, in compliance with law and regulation. The identification requirements may be lower for low value accounts ("Tiered KYC"). The term is also used in connection with regulatory requirements for a provider to understand, on an ongoing basis, who their customer is and how they are using their account. Most of the banks are mandated to perform basic/extensive KYC, before they can serve their customers. Traditionally KYC is done in a centralised fashion where a central agency has the control over all the data. For example consider each bank like SBI, Deutsche, JP Morgan, etc. when creating a bank account, each of them requires a separate KYC process to be completed and all this data gets stored in their respective databases. Even the systems like Aadhar or social security number, etc. have the data stored in a central manner and maintained by the government. However, in recent times all these centralised identity servers continue to be hacked and the important and private data being stolen regularly. With the advent of blockchain concepts and technologies, it is not ideal but imperative that we shift from the traditional identity management to a more secure decentralised claim-based identity management system. This kind of system has multiple benefits:
|
Description | See https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103093257 for details on the proof of concept P0 requirements
P1 requirements
|
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, Javascript, SQL, Hyperledger Indy |
Impact | |
Other Resources |
|
OpenG2P - Digital Identity Proof of Concept with MOSIP
Mentors | |
Category | Platform & Modules |
Overview & Objectives | Digital Identity is a pressing topic and for both generations of Fineract (1.x and CN), we'd like to have integration with emerging KYC and digital identity solutions. KYC (Know your customer) is a fundamental banking concept. It refers to the process of identifying a new customer at the time of account opening, in compliance with law and regulation. The identification requirements may be lower for low value accounts ("Tiered KYC"). The term is also used in connection with regulatory requirements for a provider to understand, on an ongoing basis, who their customer is and how they are using their account. Most of the banks are mandated to perform basic/extensive KYC, before they can serve their customers. Traditionally KYC is done in a centralised fashion where a central agency has the control over all the data. For example consider each bank like SBI, Deutsche, JP Morgan, etc. when creating a bank account, each of them requires a separate KYC process to be completed and all this data gets stored in their respective databases. Even the systems like Aadhar or social security number, etc. have the data stored in a central manner and maintained by the government. However, in recent times all these centralised identity servers continue to be hacked and the important and private data being stolen regularly. Omidyar Network along with Gates Foundation have developed the MOSIP project which provides an open source digital ID platform. Integration between Mifos along with Mojaloop can provide an end to end reference architecture for a digital cash transfer system built on open source digital public goods.
|
Description | Integration between Mifos/Fineract and digital identity systems and KYC protocols could be deepened. This project would focus on an initial proof of concept integration with MOSIP APIs for digital identity including
Registering a client with a MOSIP-powered Digital Identity in a Fineract system and verifying that digital identity to perform transactions. |
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, Javascript, SQL, MOSIP |
Impact | |
Other Resources |
|
Self-Service User Administrative Portal on Web App
Mentors | |
Category | Web - Mifos X Web App |
Overview & Objectives | Now that we have a robust mobile banking and online banking application which allows for users to self-create their own accounts, we need to add better back-end administrative support for staff of the financial institution to manage their self-service operations including user management, notifications to clients, task management, logo uploads, etc. |
Description | This project would involve front-end development of the new UI screens (some part has been already been implemented but may be enhanced) and development of additional APIs on the Apache Fineract back-end to support the following use cases:
|
Helpful Skills | Javascript, CSS, HTML5. Angular 7, Angular Material, Flex Layout |
Impact | Improved usability and staff control for self-service operations. |
Other Resources |
Android Field Operations App Functional Enhancements
Mentors | |
Category | Mobile - Mifos X Android Field Operations App |
Overview & Objectives | We have released several versions of our Android app for field officers to go out in the field to process transactions, create clients, etc. Most recently in 2020, our Google Summer of Code intern, Shashank, added support for instant search, optimized the UI, added language support through locale, added dark mode support, extended support for Kotlin in the app, and added KYC/Client Onboarding feature. For 2021, the functional focus for the application would include: cus for the appbuilding out new functionalities, UI enhancement to the application, and providing widespread coverage of automated testing throughout the app. |
Helpful Skills | Android development, SQL, Java, Javascript, Git, Kotlin |
Impact | Allows staff to go directly into the field to connect to the client. Reduces cost of operations by enabling organizations to go paperless and be more efficient. |
Other Resources | 2020 Progress: https://gist.github.com/robustTechie/85e9fde225be7926a77b1dd08c9906d1 https://github.com/openMF/android-client Architecture overview: Code style conventions guide: |
Optimize Payment Hub EE Operations UI
Mentors | @Istvan Molnar |
Category | Web |
Overview & Objectives | For our Payment Hub EE integration layer and payment orchestration engine, we provide an operational user interface which allow staff of the financial institution participating in a real-time payment scheme to manage view detail of the incoming and outgoing transactions that are flowing through the switch, manually process refunds, complete reconciliations, view and take action on unsuccessful and disputed transactions, and more. |
Description | Intern will implement the front-end UI screens for the Fineract CN web UI for the following functionalities and use case:
|
Helpful Skills | Javascript, CSS, HTML5. Angular and Bootstrap (CSS framework) is plus |
Impact | Reference UI for microfinance institutions on Apache Fineract CN |
Other Resources | Use Cases - https://github.com/openMF/digital-bank-ui/wiki/Use-Cases-&-Requirements |
Github |
Cloud interoperability Project
Android SDK Project
Mentors | |
Category | Mobile - Android SDK |
Overview & Objectives | The goal of this project is to continue work on developing the Fineract 1.x Client Android SDK which will be used in other Mifos Mobile Applications (android-client, mifos-mobile, mobile-wallet). The project aims to remove a lot of repeated code in the mobile apps and help mobile apps easily migrate to newer versions of Apache Fineract 1.x |
Description | The student will be working on implementing the following things:
|
Helpful Skills | Java, Kotlin, Android, Swagger Specification, Open API Specification, Spring (Good to have) |
Impact |
|
Other Resources | Last year progress: https://gist.github.com/Grandolf49/f79537436a467dac0baa9458a38290c5 Jira Issue for reference: https://issues.apache.org/jira/browse/FINERACT-838 |
Github |
Digital Bank UI on Fineract CN
Mentors | Gaurav Saini, Pranjal Goswami, Maulik Soneji, @Giorgio Zoppi |
Category | Web - Fineract CN Web App |
Overview & Objectives | A new reference user interface on Fineract CN for staff of financial institutions such as digital, challenger, and neo-banks that focused on individual accounts is needed for multiple reasons:
|
Description | Intern will implement the front-end UI screens for the Fineract CN web UI for the following functionalities and use case:
|
Helpful Skills | Javascript, CSS, HTML5. Angular and Bootstrap (CSS framework) is plus |
Impact | Reference UI for microfinance institutions on Apache Fineract CN |
Other Resources | Use Cases - https://github.com/openMF/digital-bank-ui/wiki/Use-Cases-&-Requirements |
Github |
Live Fineract CN API Documentation as Part of Developer Portal
Mentors | |
Overview & Objectives | The aim of this project is to provide a visual display of the Fineract CN API Documentation. We are now starting to use more of the Postman toolset for our developer portal and this project would focus on extending the existign work that was done. |
Description | This project involves providing a visual display of the API Documentation of Apache Fineract CN. Student would have to optimize documentation snippets ( .adoc ), document any service which isn't completely documented like template and reporting, document failing unit tests too and develop a visual website where these html files will be hosted. |
Skills | Java, PostgreSQL, MariaDB, Cassandra, TDD With JUnit 4, Spring REST Docs, Asciidoctor, HTML/CSS, Graphic Design |
Impact | A visual presentation of the Fineract CN APIs will be a key building block for an enabling environment for developers working on Fineract CN. |
Other Resources |
Functional Enhancements to Mifos Mobile - Mobile Banking App
Mentors | |||||
Category | Mobile - Mifos X | ||||
Overview & Objectives | Mifos Mobile is a reference mobile banking app which enables clients to authenticate themselves, view and edit their account details. and make repayments or transactions between their own accounts. It is now possible for any It is now possible for any financial institution using Mifos to provide an omni-channel banking experience including including smartphone-based mobile banking, USSD-based mobile banking, and online banking via a web app. In 2019, our Google Summer of Code intern, Prashant, extended our mobile banking app, completing a mix of functional, architectural, and design improvements including improving the outbound notification system by migrating from GCM to FCM, initial integration with RocketChat for direct customer support between staff and clients, a dark theme and better support for skinning, and phase 1 of integration with Mojaloop via the payment hub. With the payment hub and API Gateway now in place, next we look to add additional mobile money and payment system integrations into the app as well as having the app connect via the Open Banking API rather than the self-service APIs. This exercise of mapping the Fineract self-service APIs to the Open Banking APIs will be the major focus of this project. It was built on top of the Apache Fineract 1.x client-facing APIs to enable self-service channels for clients to interact with their own data and transact in a self-service manner. | ||||
Description | |||||
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, WS02 API Gateway | ||||
Impact | By providing an extensible mobile banking app, allow a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood. | ||||
Other Resources | User Stories - https://goo.gl/3xuUko Wireframes - https://goo.gl/3xuUko Customer Self Service APIs - https://cwiki.apache.org/confluence/display/FINERACT/Customer+Self-Service UK Open Banking API Standard: https://standards.openbanking.org.uk/ Source Code: https://github.com/openMF/mifos-mobile See: https://openmf.github.io/mobileapps.github.io/ Mifos Webinar on Open Banking API:
Mifos Open Banking API Documentation: https://app.gitbook.com/@mifos/s/docs/ |
Build Beyonic/MFS Africa Connector for Mifos Payment Hub EE
Mentors | |
Category | Platform - Payments Integrations |
Overview & Objectives | Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Providers like MFS Africa and Beyonic provide a set of cross-border payment rails to enable remittances across Africa terminating in mobile money wallets. Mobile money platforms like M-Pesa offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits. For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system. |
Description | The Payment Hub EE has been built out as an integration layer between Fineract and real-time payment systems like Mojaloop. Built around the Zeebe as an orchestration engine, it's built with an extensible architecture with a set of connectors for additional core banking systems, channels, and payment systems. We have a connector built for Mojaloop and the GSMA mobile money API and would like to build additional ones for the most widely used payment rails across our community. As part of our DIAL-funded project to integrate Mifos with the open source Mojaloop payments platform the team from DPC consulting built out a middleware component called the payment hub to enable the integration with the Mojaloop APIs. This middleware will also serve as the point of integration for all other external payment systems - the payment hub is extendable by additional payment connectors. This project would focus on adding the connector for the Beyonic APIs. Beyonic is a global mobile money aggregator which provides a common set of payment and collection APIs to seamlessly integrate with the leading mobile money platforms in East and West Africa. Our 2020 project provided a connector for GSMA mobile money API which can be followed as a blueprint for other connectors. This project will involve building the Beyonic connector and integrating with the specific Beyonic APIs for the mobile money use cases to be supported. |
Helpful Skills | Web Services, Java, SQL , JavaScript , Git, Sprint |
Impact | Great efficiency, reduced risk for clients, more impactful and relevant products & services. |
Other Resources |
|
Extend GSMA Mobile Money API Connector for Mifos Payment Hub
Mentors | |
Category | Platform - Payments Integrations |
Overview & Objectives | Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Mobile money platforms like M-Pesa offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits. For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system. |
Description | As part of our DIAL-funded project to integrate Mifos with the open source Mojaloop payments platform the team from DPC consulting built out a middleware component called the payment hub to enable the integration with the Mojaloop APIs. This middleware will also serve as the point of integration for all other external payment systems - the payment hub is extendable by additional payment connectors. This project would focus on adding the connector for the GSMA Mobile Money API. In 2016 GSMA published a first set of harmonized mobile money APIs to "ensure best practice in API design, security design, and more and to "address the complexity and fragmentation that is apparent in the fast-growing industry. The GSMA Mobile Money APIs are OTT (Over the Top) APIs that have been designed to cater for a core set of mobile money use cases:
This project will extend the work started by Sidhant Gupta under the mentorship of Avik Ganguly in 2019. This project will involve building the GSMA Mobile Money API connector and integrating with the specific APIs for the mobile money use cases to be supported. |
Helpful Skills | Web Services, Java, SQL , JavaScript , Git, Spring |
Impact | Great efficiency, reduced risk for clients, more impactful and relevant products & services. |
Other Resources |
|
Transformation Layer for GSMA Mobile Money API to Mojaloop Open API
Mentors | |
Category | Platform - Payments Integrations |
Overview & Objectives | Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Mobile money platforms like M-Pesa offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits. For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system. |
Description | As part of the GSMA Inclusive Tech Lab, they are building an Interoperability Test Platform to test how service providers can connect to a mobile money system via the GSMA Mobile Money API and how MNOs and DFSPs can connect to a central switch/hub via the Mojaloop API. The Mifos Initiative has also built and configured a lab environment that provides an immersive user experience complete with rich user interfaces to test out various scenarios and transaction flows originated across Mojaloop and via GSMA mobile money APIs from the perspective of various DFSPs including MFIs, wallet providers, merchants, etc. GSMA has built a transformation layer on PHP to map the GSMA Mobile Money API to the Mojaloop Open API. We would like to incorporate this transformation layer into our lab environment and to do so must write the transformation layer in a more production-ready language like Java. This project would focus on writing that Java transformation layer and ensuring the GSMA Mobile Money API connector is in place for the payment hub and API gateway. In 2016 GSMA published a first set of harmonized mobile money APIs to "ensure best practice in API design, security design, and more and to "address the complexity and fragmentation that is apparent in the fast-growing industry. The GSMA Mobile Money APIs are OTT (Over the Top) APIs that have been designed to cater for a core set of mobile money use cases:
This project will extend the work started by Sidhant Gupta under the mentorship of Avik Ganguly in 2019. This project will involve building the GSMA Mobile Money API connector and integrating with the specific APIs for the mobile money use cases to be supported. |
Helpful Skills | Web Services, Java, SQL , JavaScript , Git, Spring, Rest, Spring |
Impact | Great efficiency, reduced risk for clients, more impactful and relevant products & services. |
Other Resources |
|
Build Safaricom M-Pesa API Connector for Mifos Payment Hub EE
Mentors | |
Category | Platform - Payments Integrations |
Overview & Objectives | Mobile money is rapidly transforming financial inclusion by providing more immediate, impactful, affordable, and secure financial services to the client. Mobile money platforms like M-Pesa offer the client unparalleled value in terms of convenience, security and the possibility of new services and products that are more in line with real-world financial habits. For financial institutions and their clients to fully scale mobile money and leverage its potential, it needs to be fully integrated with their core-banking system. |
Description | As part of our DIAL-funded project to integrate Mifos with the open source Mojaloop payments platform the team from DPC consulting built out a middleware component called the payment hub to enable the integration with the Mojaloop APIs. This middleware will also serve as the point of integration for all other external payment systems - the payment hub is extendable by additional payment connectors. This project would focus on adding the connector for the Safaricom M-Pesa APIs. M-Pesa is the leading mobile money platform from Kenya. The payment hub built upon the work of previous interns, most recently the efforts on the Mifos Payment Gateway which were led by Sidhant Gupta in 2019. This project will involve building the M-Pesa connector and integrating with the specific M-Pesa APIs for the mobile money use cases to be supported. |
Helpful Skills | Web Services, Java, SQL , JavaScript , Git, Spring, Apache Camel, Kafka, Rest, Zeebe |
Impact | Great efficiency, reduced risk for clients, more impactful and relevant products & services. |
Other Resources |
|
Optimize Containerization & Deployment of Apache Fineract CN
Mentors | |
Overview & Objectives | The increasing need for fast and reliable access to financial services has prompted the expansion of Apache Fineract from a single complex financial platform to a platform constituted of multiple micro-services that interact and scale to meet up with this increased need - Apache Fineract CN. Apache Fineract CN is a digital financial application platform built to render financial services to consumers in a fast, reliable and scalable manner. Deploying this platform such that consumers get the latest features with no reduction impact requires an optimized release cycle in a CI/CD (continuous integration and continuous Deployment) environment. |
Description | In view of that, last year Courage began this work by implementing the needed scripts to containerize and deploy the Fineract CN services using Docker, Docker compose and Kubernetes. For the Google Summer of Code 2020, you are required to complete this work by performing the following task:
N.B:
|
Helpful Skills | Docker, Kubernetes, Jenkins, Bash, Java - Spring, PostgreSQL, MariaDB, Cassandra, TDD With JUnit 4, Gradle |
Impact | Provide a CI/CD pipeline to mange the the release of Apache Finerect CN microservices |
Other Resources | Vendor pages GSoC 2018: https://summerofcode.withgoogle.com/archive/2018/projects/5060024451727360/ |
Computer Vision Based PPI Tool Version 3.0
Mentors | |
Overview & Objectives | In 2019, Appoorva built out the alpha version of this project including the initial app and machine learning model for image processing. In 2020, Yash made this a functional application. The student for 2021 would extend the application and refine the model to achieve the original vision. Build out an AI-powered tool that leverages Machine Learning and Google's Cloud Vision to capture responses for the 10-question Poverty Probability Index (PPI) Scorecard using the simple image capture via a smartphone camera. Social Performance Measurement is a critical tool for financial inclusion providers and the PPI is a widely-accepted tool for capturing it. Student would work on training the model for analyzing these images based on the scorecard requirements for multiple PPIs. |
Description | The Poverty Probability Index (PPI®) is a poverty measurement tool for organizations and businesses with a mission to serve the poor. The PPI is statistically-sound, yet simple to use: the answers to 10 questions about a household’s characteristics and asset ownership are scored to compute the likelihood that the household is living below the poverty line. Recording the answers to these 10 questions on initial onboarding of a client and at future period intervals is fraught with manual human error and data integrity issues. Leveraging Cloud Vision, a field officer would simply have to take a series of photos with their smartphone camera inside and outside of the house and then the Cloud Vision would be able to deduce based on the images the response to the 10 questions (i.e. the presence of soot on the walls would denote a coal-base stove is using, the image could easily depict what material the roof is made of, the image could detect the BMI of the family, the image could detect if there is a TV in the household. Cloud Vision won't be able to answer every single question in each 10-question scorecard but for some it would. |
Helpful Skills | Machine Learning, AI, Data Science, Statistics |
Impact | More widespread adoption of Social Performance Measurement and Increased Efficiency and Improved Data Integrity by reducing manual data entry for PPI scorecard capturing. |
Other Resources | 2020 GSOC Output
About the PPI
About Google's Cloud Vision |
Static Analysis and Vulnerability Scanning of Apache Fineract CN
Mentors | |
Category | Framework - Apache Fineract CN, Security |
Overview & Objectives | As our product is core banking platform and our clients are financial institutions, we strive hard to make our code base as secure as possible. However, due to ever increasing security threats and vulnerabilities, it is the need of hour that we analyze our code base in depth for security vulnerabilities. During pull request merge process, we have a process in place wherein we do peer code review,QA and integration tests. This practice has been very effective and our community is already reaping the benefits of such a strong code review process. However, we should test our code against the standard vulnerabilities which have been identified by reputed organisations like Mitre to gain more confidence. It has become a critical part of independent and partner-led deployments |
Description | We can make use of opensource tools like Jlint, Findbugs , SonarQube or frameworks like Total output Integration Framework (TOIF) - used by companies dedicated to produce military grade secure systems. As our environments become more containerized we can also utilize tools like: Anchore, Snyk.io, and Docker Bench for Security It would be worthwhile, if we can dedicate one GSOC project for this analysis. The student would be responsible to analyse the findings, generate reports, identify if it is really a bug and then submit a fix after consultation from the community. Of course, the student needs to demonstrate some basic understanding of security vulnerabilities( like buffer overflow etc) and should have some academic level of experience working with static analysis tools. |
Helpful Skills | Java (Spring/JPA/Jersey), SQL , JavaScript , Git, Apache POI |
Impact | Improved security keeping the integrity and privacy of the underbank's financial data intact. |
Other Resources | Static Analysis of Apache Fineract Project- A GSOC project idea |
Static Analysis and Vulnerability Scanning of Apache Fineract 1.x
Mentors | |
Category | Framework - Apache Fineract CN, Security |
Overview & Objectives | As our product is core banking platform and our clients are financial institutions, we strive hard to make our code base as secure as possible. However, due to ever increasing security threats and vulnerabilities, it is the need of hour that we analyze our code base in depth for security vulnerabilities. During pull request merge process, we have a process in place wherein we do peer code review,QA and integration tests. This practice has been very effective and our community is already reaping the benefits of such a strong code review process. However, we should test our code against the standard vulnerabilities which have been identified by reputed organisations like Mitre to gain more confidence. It has become a critical part of independent and partner-led deployments |
Description | We can make use of opensource tools like Jlint, Findbugs , SonarQube or frameworks like Total output Integration Framework (TOIF) - used by companies dedicated to produce military grade secure systems. As our environments become more containerized we can also utilize tools like: Anchore, Snyk.io, and Docker Bench for Security It would be worthwhile, if we can dedicate one GSOC project for this analysis. The student would be responsible to analyse the findings, generate reports, identify if it is really a bug and then submit a fix after consultation from the community. Of course, the student needs to demonstrate some basic understanding of security vulnerabilities( like buffer overflow etc) and should have some academic level of experience working with static analysis tools. |
Helpful Skills | Java (Spring/JPA/Jersey), SQL , JavaScript , Git, Apache POI |
Impact | Improved security keeping the integrity and privacy of the underbank's financial data intact. |
Other Resources | Static Analysis of Apache Fineract Project- A GSOC project idea |
Scorecard for Credit Risk Assessment Phase 4
Mentors | Lalit Mohan S Victor Romero |
Overview & Objectives | Financial Organizations using Mifos/Fineract are depending on external agencies or their past experiences for evaluating credit scoring and identification of potential NPAs. Though information from external agencies is required, financial organizations can have an internal scorecard for evaluating loans so that preventive/proactive actions can be done along with external agencies reports. In industry, organizations are using rule based, Statistical and Machine learning methods for credit scoring, predicting potential NPAs, fraud detection and other activities. This project aims to implement a scorecard based on statistical and ML methods for credit scoring and identification of potential NPAs. |
Description | The approach should factor and improve last year's GSOC work (https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7) on Features/Characteristics, Criteria and evaluation (link). The design and implementation of the screens should follow Mifos Application standards. Should implement statistical and ML methods with explainability on decision making. Should also be extensible for adding other functionalities such as fraud detection, cross-sell and up-sell, etc. |
Helpful Skills | JAVA, Integrating Backend Service, MIFOS X, Apache Fineract, AngularJS, ORM, ML, Statistical Methods, Django |
Impact | Streamlined Operations, Better RISK Management, Automated Response Mechanism |
Other Resources | 2019 Progress: https://gist.github.com/SupreethSudhakaranMenon/a20251271adb341f949dbfeb035191f7 |
Mifos/Fineract Chatbot & Adapter 3.0
Mentors | Raul Sibija |
Overview & Objectives | For many of our users today, chat is a much more familiar form of user interface for them and it would be valuable to provide an extensible chatbot connected to Mifos/Fineract that could be used to both provide customer support as well as allow clients to directly interact with their accounts. See this post from ThitsaWorks for more: https://medium.com/@thitsaworks/chatbots-the-emergent-and-effective-tool-in-financial-education-f6e63baf9188 |
Description | This project will focus on building on the latest version of the chatbot. In 2019, our GSOC intern, Anshul extended the Mifos Chatbot and Adapter with better authentication, improved Natural Language Processing, and integration with the Slack, Telegram and Facebook messenger platforms. The project will include both leveraging other open source libraries and components to build the chatbot and building the adapter to the chatbot for MIfos/Fineract which will act as the interaction between chatbot and Mifos. It will take the replies from chat and feed them into Mifos. The program will sit in between Mifos and Chat. Main components needed are:
Note: only Apache license compatible libraries/frameworks/components can be used. It will cover the following use cases:
|
Helpful Skills | SQL, Java, Git, Spring, OpenJPA, Rest Helpful: technical knowledge of (any) chat protocol (e. g. XMPP, IRC), experience with NPU/NLP |
Impact | |
Other Resources | 2019 Progress: https://gist.github.com/iosdev747/2b7de87cd9b028bb97433ee2e26ad18d Source Code: https://github.com/openMF/mifos-chatbot AI/NLU services Frameworks NLP/NLU components and tools Tutorials Other |
Functional Enhancements to Mifos Mobile CN - Mobile Banking App for Fineract CN
Mentors | |||||
Category | Mobile - Fineract CN | ||||
Overview & Objectives | Just as we have a client-facing mobile banking app for our generation 2 Apache Fineract 1.0 platform, we need to provide a reference mobile banking app on top of the Apache Fineract CN architecture which allows a client to securely authenticate against the microservices architecture and interact with his/her accounts. | ||||
Description | |||||
Helpful Skills | Android development, SQL, Java, Javascript, Git, Spring, OpenJPA, Rest, WS02 API Gateway | ||||
Impact | By providing an extensible mobile banking app, allow a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood. | ||||
Other Resources | User Stories - https://goo.gl/3xuUko Wireframes - https://goo.gl/3xuUko Customer Self Service APIs - https://cwiki.apache.org/confluence/display/FINERACT/Customer+Self-Service Source Code: https://github.com/openMF/mifos-mobile-cn UK Open Banking API Standard: https://standards.openbanking.org.uk/ Mifos Webinar on Open Banking API:
Mifos Open Banking API Documentation: https://app.gitbook.com/@mifos/s/docs/ See https://openmf.github.io/mobileapps.github.io/ |
Credit Bureau Integration Phase 3
Mentors | |
Overview & Objectives | Because of regulatory reasons or to do background check of a client (risk management), MFIs depend on credit bureaus. As part of it, MFI must submit client details to credit bureau and also need to pull client information from credit bureau before approving any new loans to a client.Mifos X can be integrated with a popular CBs in India and from other regions (based on the demand). |
Description | During the 2016 Google Summer of Code, Nikhil Pawar, completed the credit bureau integration module with integrations for the major credit bureaus in India. This project will continue extending the functionality of the module and work on integrations with the major credit bureaus in Latin America and Sub-Saharan Africa. The major functionality will be sending the data to CBs on regular intervals in the format CB expects. And option to pull the client’s information from CB whenever loan officer/branch manager/ user wants to view the information for a particular client. |
Helpful Skills | SQL, Java, Javascript, Git, Web Services, Big Data (Hadoop, Hive) |
Impact | The credit report shows account information such as repayment record, defaults, type of loan, amount of loan, etc. of the customer. This information facilitates prudent decision-making when the credit underwriter processes the loan application. This help MFI to reduce the risk of bad loans and reduces the multiple lendings to same person from different MFIs. |
Other Resources | For the scope of this project for 2019, see https://jira.apache.org/jira/browse/FINERACT-734 Detailed requirementshttps://goo.gl/aZWMZa Mifos Credit bureau Integration. (Risk calibration Module -RCM) Source Code: https://github.com/apache/incubator-fineract/pull/215 |
Online Banking App 5.0
Mentors | |||||
Category | Web - Mifos X Online Banking App | ||||
Overview & Objectives | In 2019, we built out v3.0 of our online banking app, an Angular web app powered by self-service APIs allowing for account creation, logging in, viewing of account details, transferring between savings accounts, repaying loans via savings accounts, applying for new loans, and more. This project will extend off that to focus on integrating with the newly created Open Banking API layer which replaces the self-service APIs mapping to the newly created add new features and continue polishing the UI. | ||||
Description | |||||
Helpful Skills | AngularJS development, SQL, Java, Javascript, Git | ||||
Impact | Allows a member/client in having a self-service channel allowing them more direct control and visibility into their financial livelihood. | ||||
Other Resources | 2019 Progress: https://gist.github.com/CajetanRodrigues/b2b14b55f0f2c97ea276eb764209c4d9 Self Service APIs - https://cwiki.apache.org/confluence/display/FINERACT/Customer+Self-Service Source Code - https://github.com/openMF/web-self-service-app and https://github.com/openMF/online-banking-app Complete Details can be found here: Self Service Web Application UK Open Banking API Standard: https://standards.openbanking.org.uk/ Mifos Webinar on Open Banking API:
Mifos Open Banking API Documentation: https://app.gitbook.com/@mifos/s/docs/ Further Ideas: https://docs.google.com/document/d/1KXDSrBkuYA9g694-DE4qf1QKFcAhWwA-HNnn9YAucbk/edit?usp=sharing |
Digital Bank UI on Fineract CN
Scalability & Performance Enhancements for Supporting Millions of Clients, High TPS, and Concurrent Users
Mentors | |
Category | Platform |
Overview & Objectives | As Mifos X has matured as a core banking platform, it's been adopted and used by larger institutions serving hundreds of thousands and even millions of clients. Partners operating cloud-hosted subscription models are also supporting hundreds of thousands of clients across their multi-tenant installations. Most recently, more and more digital-first fintechs are using the platforms for highly scalable wallet accounts needing hundreds and thousands of TPS. We need to benchmark, analyze and improve the performance and scalability of the system. |
Description | Enhancements to the back-end platform will include parallelization of all the jobs with a configurable amount of concurrency, look at the explain plans of the queries being used in the jobs, paginate input queries for jobs, put lazy fetching where required, node-aware scheduler and cache, office-wise configurable jobs to distribute job-load across servers and write some tests to prove that the concurrency will work for a decent amount of scale. In addition, you'll provide some metrics which can help mid-sized MFIs (those having around a million active loans) in adopting Mifos X. |
Helpful Skills | Java, Javascript, Spring, JAX-RS, JPA, |
Impact | Higher outreach to the unbanked by supporting larger institutions and scaling more rapidly. |
Other Resources |
Ad Hoc Reporting Module/Business Analytics (OLAP)
Mentors | |||||||||
Overview & Objectives | Develop ETL scripts to create OLAP cubes (fact and dimension tables in MySQL). This will allow managers to perform ad hoc slicing and dicing of their data
This project would extend off of the work of a previous GSOC intern in building out integration with Saiku. | ||||||||
Description | The data and information housed in the centralized Mifos database is critical to the operations and management of a financial institution. While Mifos X ships with more than five dozen standard report and has multiple ways to build custom reports, non-technical staff who don’t know SQL queries nor the structure of the database struggle to be able to access new reports on the fly. Integration with Saiku would allow for ad-hoc reporting or more simply a drag and drop interface for management and non-technical staff to easily slice and dice and create reports on the fly. | ||||||||
Helpful Skills | Database Management Systems, MDX, SQL, | ||||||||
Impact | Data drives a microfinance institution - the more powerful and robust analytical tools management has, the better they can tailor their services and outreach to impact the poor most effectively. | ||||||||
Other Resources | Saiku Analytics Demo - demo.analytical-labs.com
|
Accounting Module Enhancements
Mentors | |
Category | Platform |
Overview & Objectives | Mifos X and the Apache Fineract platform already provide a range of sophisticated financial accounting needs, however for organizations that use it as both their core banking system and accounting system all in one, they continue to need other features. While Mifos X never intends to replace an ERP or accounting package, we do want to continue to add additional functionalities that provide the necessary integration with the portfolio and general accounting functionality to support a financial institution's core operations. Several features have been requested by users and partners that we've grouped together as one task. Applicants should be familiar with the stack as well as the accounting and financial services domain. Some of this work will include finalizing and incorporating existing pull requests and contributions that have been made by partners. |
Description | These enhancements will all be built into the Apache Fineract platform as part of or enhancements on top of the existing accounting module which provides full configuration of the chart of accounts, support for cash and accrual accounting, automated integration with the portfolio accounts and financial mappings, and single and compound journal entries to the general ledger. New enhancements include:
|
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, Javascript, SQL |
Impact | Better internal control and financial transparency |
Other Resources |
Collateral Management Module
Mentors | Avik Ganguly | ||||||||
Category | Platform | ||||||||
Overview & Objectives | As financial inclusion evolves, more loan products are collateral-based and require more detailed tracking of the asset (gold, property, etc.) along with its value, and its depreciation. Some institutions also require tracking collateral as off-balance sheet items. | ||||||||
Description | The practice of putting up collateral in exchange for a loan is used as part of the lending process between businesses for some time now. The Collateral Management Module (CMM) implements the issuance, validation and processing of collateral transactions between two members of an MFI. In a swap transaction between Party A ( Lender ) and Party B (Borrower ),
| ||||||||
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, SQL | ||||||||
Impact | Clients and Small Businesses are able to take out higher value loans when they can offer up different forms of collateral. This is essential as MFIs move beyond just group loans and to individual lending. | ||||||||
Other Resources | See |
Insurance Claims Module
Mentors | |
Category | Platform |
Overview & Objectives | A crucial part of financial inclusion is micro-insurance and the ability for clients to safely manage risk in their lives. Mifos X will not fully handle the entire lifecycle of an insurance product but it should integrate with microinsurance system and track the key parts of the process that relate to the core banking system - collection and pass through of the premium and tracking claims and processing of these. |
Description | This project would involve building out a separate module that tracks claims being made by a client, likely leveraging the CRM functionality being build to track activities. It will integrate with APIs to enable processing of the claim and tracking what proceeds must be paid out to the client. It will involve creating a new module with data model, UI screens and business logic that leverages Mifos X APIs Tasks involved include:
This will also be helpful for intern; An insurance claim is a formal request made to a Financial Institution asking for a payment based on the terms of an insurance policy. It would be nice for MFIs to provide a range of insurance products such as Health insurance, property insurance, casualty insurance, etc so that their members claim these. The insurance claims module has the following workflow;
|
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, SQL |
Impact | Clients are able to lower their risk and have a much larger safety net when they have affordable access to insurance policies. |
Other Resources |
Extend Surveys & SPM Framework
Mentors | |
Category | Platform & Web |
Overview & Objectives | Financial Inclusion providers need a comprehensive view into the overall livelihood of their client both for better risk analysis, credit scoring, as well as social performance management. |
Description | We have the back-end in place for a surveys/social performance management framework that allows the import of XMLs for the PPI (progress out of poverty index) SPM scorecard. We need to implement a front-end UI for viewing and recording PPI surveys as well as a UI in which to create new surveys from scratch (similar to Question Groups in an older version of software). 1) Build out the UI for creating survey from available PPI scorecard See Resources below for specs/wireframes. |
Helpful Skills | HTML, Spring, Hibernate, REST, Java, AngularJS, SQL |
Impact | Ability to measure social impact and have one single point of information on a client within the platform. |
Other Resources | See https://cwiki.apache.org/confluence/display/FINERACT/Social+Performance+Management+Framework These are the legacy docs on the old question group functionality: https://mifosforge.jira.com/wiki/display/MIFOS/Question+Groups+and+PPI |
Front Desk Service Module / Experience Module
Mentors | |
Overview & Objectives | Before booking a loan, the customer needs to require and assess the details of the loan he is enquiring for and there is no way to personally judge it, based on the parameters, Sales staff right now is using different external loan calculator and loan product schemes are not documented. We need a frontend experience service with personalized match to loan products. |
Description | The staff or customer should be able to enter their requirements before applying for a loan, like Loan amount, what kind of loan product he is interested in, and based on a questionnaire or a survey he should be presented a view where loan products are personally matched based on recommendation engine.After setting basic loan parameters, customer should be able to get a quote and then will be transferred to CRM given by Ankit Sharma |
Helpful Skills | ANDROID UI, Integrating Backend Service, MIFOS X |
Impact | Streamlined sales, Staff and Customer Better Interaction |
Other Resources | https://docs.google.com/document/d/18rS0gVWkjQvNdRnNj40uKNl32zuTh-uuzNv161n6YrY/edit?usp=sharing |
Client Impact Portal Phase 2
Mentors | |
Category | Platform |
Overview & Objectives | Microfinance institutions usually work with various external parties, such as funders or investors. Using the data that is available in MifosX we would like to offer those stakeholders a separate portal showing accurate and high-level information about the institution that would otherwise be reported manually by the institution. This information helps them in their decision making processes, but also enables them to assess the broader impact they are having with their funding. |
Description | To develop a portal that aggregates information from different Mifos X deployments and report on predefined social and operational metrics Objectives:
|
Helpful Skills | SQL, Java, Javascript, Git, Web Services, Scripting (Bash/Perl/Ruby), Regexes & Parsing |
Impact | Funders and investors are vital for almost all MFIs, providing them with accurate information on the impact they are making with each of their MFI's is something they highly value and that enables them to assess whether they want to further support the MFI's moving forward to enable growth of the MFI. |
Other Resources | Previous GSOC Client Impact Portal Project
Vision for Generic SPM Framework for Mifos X (PPI) Background on Client Impact Portal
|
ETL-Based Data Migration Tool for Mifos X
Mentors | |
Overview & Objectives | Data migration can be one of the most challenging and time-consuming phases of an implementation of a core banking system. It's often a barrier to financial institutions moving on to new and better more modern systems. It's critical to cleanly migrate over the historical data of a client and their transactions. Often the legacy system data needs to be cleaned up and transformed before it can be migrated into Mifos X and is one of the most costly and time-consuming phases of a deployment. We have the beginnings of a migration tool from Mifos X to Mifos I/O (Fineract CN) This project would extend the existing tool to provide a standard migration path. |
Description | Extend the existing Mifos to Mifos I/O migration tool
|
Helpful Skills | Java (Spring/JPA/Jersey), SQL , JavaScript , Git, Pentaho, Kettle, |
Impact | It has many impacts
|
Other Resources | https://github.com/openMF/fineract-cn-data-import-demoserver |
Basic CRM Functionality - Inquiries/Complaints Module
Mentors | TBD |
Category | Platform - Apache Fineract 1.0 |
Overview & Objectives | Right now Mifos X contains core client management functionalities including tracking basic demographic information, know your customer information, document management, and survey collection through data tables. As financial institutions, serving the poor begin to offer a more in-depth and diverse range of financial inclusion products, the need for more robust client management and in-depth client understanding has grown. Their core system needs to provide more and more CRM-type functionality that compliment the portfolio management and financial/social reporting that the Mifos X provides. This project will work to deliver the initial set of customer relationship management functionalities including a module for tracking inquiries, complaints |
Description | This module will have a request management functionality. A request can be of 2 types: Complaints and Service Requests. Each request must be against a customer and optionally against an account of the customer. Each request will go through a simple workflow. Actions that can be performed on a request: Assign -> will change status to "assigned" Start Work --> will change status to "in progress" Close --> will change status to "closed" (with a sub-reason code) At each step user can enter comments. The customer summary screen will have a link to view the requests of the customer - along with a summary and current status - with options to click-through to get the complete history of each request. |
Helpful Skills | familiarity with Mifos X tech architecture, angular js,node js, java,Spring, Backend Integration |
Impact | Deepening the client relationship and ensuring fair, responsible, and transparent financial services to the poor is a core piece of the industry's roadmap for financial inclusion. Providing customers the ability to voice their concerns and feedback about the services they're receiving provides a simple yet powerful tool to protect the client. Empowering the financial institution with the ability to track these inquiries and overall maintain a more holistic relationship tracking entire lifecycle of their clients gives them a much better ability to understand their clients and respond to their needs with appropriately designed services and products. |
Other Resources |
Security Penetration testing
Mentors | Mark Reynolds |
Category | Platform |
Overview & Objectives | We believe the Mifos X platform is super secure and impenetrable. Your mission, should you choose to accept it, is to prove us wrong, and help close gaps you may find. |
Description | Beyond a one time exercise, you should integrate (some of) the tools you've used into our build chain so that, even after you've gone, tools flag up future newly introduced potential vulnerabilities. |
Helpful Skills | Candidates applying for this project would ideally have prior experience in penetration testing, and document this in their application. |
Impact | Re-assuring the more Entreprise-y type Mifos clients that they can safely bet on Mifos X as an MFI platform. |
Other Resources | https://www.owasp.org/index.php/Main_Page https://code.google.com/p/zaproxy/ Run FindBugs & related tools for some serious static code analysis |
Mifos ID/Profile - Single Sign On for Community Infrastructure
Mentors | |
Overview & Objectives | This project would seek to create one unified ID/login and profile for community members similar to the OpenMRS ID. It would achieve the following two primary objectives:
|
Description |
Design a profile Extra Credit:
|
Helpful Skills | LDAP |
Impact | Impact is two-fold:
|
Other Resources |
Scalable Mifos X deployment on OpenShift: Automated Continuous Delivery, Scripts, Documentation
Mentors | |
Overview & Objectives | Create a POC of a scalable MifosX implementation on OpenShift. Also publish a whitepaper with details of this set up. |
Description | Mifos X was built to be cloud ready from the ground up. One of the most popular deployment environments for MifosX has been on Amazon EC2, however due to country specific regulation, many implementors are forced to seek alternative models that can scale as effectively. The aim of this project is two-fold:
To prepare for this project, applying students must demonstrate at least that they have already successfully locally built and ran a Mifos X REST back-end server and UI, populated the database etc. as well as provided a simple pull request proposing some minimal deployment related improvement. Note that we now believe that a Platform as a Service (PaaS) is a more suitable foundation for this project than a raw Cloud Infrastructure as a Service (IaaS) platform (such as Openstack, offered by public cloud provider such as e.g. Rackspace; or Azure, or raw Amazon EC2). This is because a PaaS, such OpenShift, already come with relevant features such as built-in, managed, supported and monitored HTTP load balancing (e.g. OpenShift comes with HAProxy). We are aware that OpenShift out-of-the-box currently does not provide supported clustering for the MariaDB/mysql database used by Mifos (there is documentation for un-supported example based on an OpenShift template and suggested descriptions on blog posts, or also this one based on Severalnines.com; similarly one could deploy the commercial Percona XtraDB Cluster product). However at this point we believe that this would not be required, and that proper configuration on OpenStack of the already existing cache facility (incl. distributed cache invalidation) available in Mifos X will add more value at signficantly less operational complexity. You may need to develop some minor "adjustments" for Mifos X to work well in a PaaS. For example, writeable directories may be limited, and configuration changes may be needed to pick up allowed data directories from an environment variable configuration (but consider multi node distribution in this cluster setup!). Also a cloud PaaS like OpenShift may not support "always running" instances, and scheduled jobs may have to be configured to be kicked off via an explicit HTTP "wake up" request from a cron job. While OpenShift should already take care of automatic distribution of Mifos code (WAR) updates among nodes in the cluster, you may also have to consider distributed configuration in a cluster. Normally all Mifos X configuration should reside 100% fully in the database only, and as such this may be a non-issue. If however there are any customized configuration files, then perhaps something like the Spring Cloud project could be of interest to ease distributed configuration management. We are aware of other PaaS product similar to OpenShift, such as notably Cloud Foundry, or even Heroku (closed source..) but would suggest to use OpenShift. |
Helpful Skills | Continous Integration, UNIX, OpenStack, experience with any public cloud (AWS etc) and Percona Server is a plus, plus some minor Java coding required to adapt Mifos code to be able to pick up the database configuration from the OpenStack provided environment variable (and possibly automated Cache configuration tuning on OpenStack). |
Impact | Improves deployment options for Mifos. Would be very helpful for specialists in African countries who deal with strict regulatory controls in hosting data outside their region |
Other Resources | OpenShift https://www.openshift.com Old Mifos mailing list posts related to related things, search e.g. "mifos google app engine", and find as this one as well as this one. |
Mifos X on "Enterprise Stack" - IBM WebSphere and Oracle WebLogic tests & documentation
Mentors | |
Overview & Objectives | Mifos X today is typically used on Tomcat (with Jetty known to work). For a certain class of users, testing it on "Enterprise Stack" application servers (meaning IBM WebSphere and Oracle WebLogic) is desirable - this project would properly test Mifos X on these configurations, make any adaptations to the code which may be required, and produce easy to follow documentation or even small tools helping future users how to go about this. |
Description | This project could be combined with and taken up by the same candidate as the Enterprise database project. |
Helpful Skills | Java, Application Server configuration, WAS classloading crap tricks, documentation writing. Use Cargo, Arquillian etc. for automated testing against WAS & WLS containers? |
Impact | Enable Mifos X to be considered by users wanting it to run (only) on an Enterprise stack |
Other Resources | Vendor pages |
...