Mifos Community App
This is the default web application built on top of the MifosX platform for the mifos user community.
Website: https://mifos.org
Type of Digital Public Good
- Open content
- Open data
- ✅ Open software
- Open standard
- Open AI model
1. Is it relevant to one of the Sustainable Development Goals?
- 1. No Poverty
Evidence: The Mifos Initiative is a global 501(c)3 fintech non-profit leveraging the cloud, mobile & open source community to democratize financial services worldwide and digitally transform the world?s 3 billion poor and underbanked. We aim to create a world of 3 Billion Maries where everyone has access to the financial resources needed to create a better life for themselves and their family. More than 15 million clients supported by 400+ fintechs and financial institutions using our open APIs to power their solutions.
We provide a set of Open Source Buildings Blocks for digital financial services consisting of re-usable and pluggable components that support the common core banking requirements. Our end to end open source architecture for digital financial services can power an an entire digital financial services ecosystem with multiple layers of open APIs at the solution and application level that fuel innovation on top of digital interoperable payment rails - Open Source Banking APIs for flexible account management from Mifos and Fineract, Open APIs for Payments Interoperability via Mojaloop, and app-level innovation enabled by Open Banking APIs and reference mobile apps. - 8. Decent Work and Economic Growth
Evidence: The Mifos Initiative is a global 501(c)3 fintech non-profit leveraging the cloud, mobile & open source community to democratize financial services worldwide and digitally transform the world?s 3 billion poor and underbanked. We aim to create a world of 3 Billion Maries where everyone has access to the financial resources needed to create a better life for themselves and their family. More than 15 million clients supported by 400+ fintechs and financial institutions using our open APIs to power their solutions.
We provide a set of Open Source Buildings Blocks for digital financial services consisting of re-usable and pluggable components that support the common core banking requirements. Our end to end open source architecture for digital financial services can power an an entire digital financial services ecosystem with multiple layers of open APIs at the solution and application level that fuel innovation on top of digital interoperable payment rails - Open Source Banking APIs for flexible account management from Mifos and Fineract, Open APIs for Payments Interoperability via Mojaloop, and app-level innovation enabled by Open Banking APIs and reference mobile apps.
2. Does it use an appropriate open license?
Yes, this project is licensed under the following license(s):
3. Is ownership clearly defined?
Is the ownership of the project and everything that the project produces clearly defined and documented?
Yes
If yes - please link to the relevant copyright, trademarks, or ownership documentation for the project.
4. Does the license of libraries/dependencies undermine the openess of the project?
Does this open project have mandatory dependencies (i.e. libraries, hardware) that create more restrictions than the original license?
No
If yes - are the open source components able to demonstrate independence from the closed component(s) and/or are there functional, open alternatives?
Not Applicable
If yes - please describe how the open source components are independent and/or list the open alternatives for the closed component:
Not Applicable
5. Is there documentation?
Does some documentation exist of the source code, use cases, and/or functional requirements. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For datasets and data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. For content collections, this should indicate any relevant compatible apps, software, hardware required to access the content and any instructions about how to use it.
Yes
If yes - please link to the relevant documentation:
6. Is non PII data and/or content accessible?
Does this project collect or use non-personally identifiable information (non-PII) data and/or content?
No
If yes - describe the mechanism for extracting or importing non-personally identifiable information from the system in a non-proprietary format:
Not Applicable
7. Does the project adhere to privacy and other applicable international and domestic laws?
Has this project taken steps to ensure adherence with relevant privacy, domestic, and international laws? For example, the General Data Protection Regulation (GDPR) in the European Union or the Supplementary Act A/SA.1/01/10 on Personal Data Protection for the Economic Community of West African States (ECOWAS) (yes/no)
Yes
If yes, please list some of relevant laws that the project complies with:
- GDPR
- OFAC
If yes, please describe the steps this project has taken to ensure adherence (include links to terms of service, privacy policy, or other relevant documentation):
Not Applicable
8. Does the project adhere to standards and best practices?
Does this project support standards? (i.e. Web Content Accessibility Guidelines (WCAG) 2.1 or other standards such as those listed on W3C)
Yes
Which standards does this project support (please list)
- W3C
Can you point to evidence of your support? (i.e. please link to your validator, open test suite, etc.)
Was this project built and developed according to or in adherence with any design, technical and/or sector best practices or principles? i.e. the Principles for Digital Development?
Yes
Which principles and best practices does this project support (please list)
- Principles for Digital Development
9. Does the project do no harm by design?
Has this project taken steps to anticipate, prevent and do no harm by design?
On the whole, does this project take steps to ensure that it anticipates, prevents and does no harm by design?
Yes
Is there any additional information you would like to share about the mechanisms, processes or policies that this project uses to avoid doing harm by design?
9.a. Data Privacy & Security
Does this project collect or store personally identifiable information (PII) data and/or content?
Yes
If yes - please list the types of data and/or content collected and/or stored by the project:
- We don't collect this information but our software (as a core banking platform) collects this information.
If yes - does this project share this data and/or content with third parties?
No
Please describe the circumstances with which this project shares data and/or content with third parties. Please add links as relevant.
Not Applicable
If yes - does the project ensure the privacy, security and integrity of this data and/or content collection and has it taken steps to prevent adverse impacts resulting from its collection, storage and distribution.
Yes
If yes - please describe the steps, and include a link to the privacy policy and/or terms of service:
While we don't collect the data ourselves, the software has high degrees of security and compliance at the software and network level to ensure data integrity.
9.b. Inappropriate & Illegal Content
Does this project collect, store or distribute content?
No
If yes - what kinds of content does this project, collect, store or distribute? (i.e. childrens books)
Not Applicable
If yes - does this project have policies that describe what is considered innappropriate content? (i.e. child sexual abuse materials)
No
If yes - please link to the relevant policy/guidelines/documentation.
Not Applicable
If yes - does this project have policies and processes for detecting and moderating innappropriate/illegal content?
Not Applicable
If yes - please describe the policies and processes for detecting, reporting and removing innapropriate/illegal content (Please include the average response time for assessment and/or action. Link to any policies or descriptions of how inappropriate content is handled):
Not Applicable
9.c. Protection from harassment
Does this project facilitate interactions with or between users or contributors?
Yes
If yes - does the project take steps to address the safety and security of underage users?
Yes
If yes - please describe the steps this project takes to address risk or prevent access by underage users:
- During programs like GCI, students full names aren't referenced - just their online ID or avatar.
If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment?
Yes
If yes - please describe the steps taken to help users protect themselves.
- We maintain a code of conduct and aim to mediate and resolve issues that arise amongst community members.
Development & deployment countries
List of countries this project was developed in.
- India
- United States of America
- Germany
- Netherlands
- Canada
- Kenya
- Mexico
- Hungary
- United Kingdom
List of countries this project is actively deployed in.
- Kenya
- South Africa
- Nigeria
- Rwanda
- Ethiopia
- Sierra Leone
- Uganda
- Hungary
- United Kingdom
- India
- Philippines
- Myanmar
- Vietnam
- Australia
- Mexico
- Peru
- Colombia
- Nicaragua
- Honduras
- Argentina
- Uruguay
- Nigeria
- Côte d'Ivoire
- Mozambique
- Senegal
- Tunisia
- Lebanon
- Spain
- China
- United States of America