Apache Fineract
Digital PaymentsApache Fineract is an open-source, API-first core banking engine for loans, savings, client management, accounting and payment processing, governed by the Apache Software Foundation. Already cited in the collection criteria as an example of the Digital Payments domain, it underpins financial inclusion for 400-plus institutions and millions of accounts.
- DPG Profile: https://www.digitalpublicgoods.net/r/apache-fineract
- Website: https://fineract.apache.org/
- Source code: https://github.com/apache/fineract
All DPGs in the DPGs for DPI Collection are assessed by the DPGA Secretariat against the DPGs for DPI criteria v2.0. Assessments use publicly available documentation and link to their evidence below. Assessed September 2026.
14 of 18 checks met
4 partially met
Layer 1
Recognised DPG
Layer 2
DPI Relevance
Layer 3
DPI Architecture Alignment
Layer 1 Recognised Digital Public Good
Listed in the DPG Registry.
Layer 2 DPI Relevance
Does it provide a foundational DPI function, reusable across sectors, at population scale?
It is a core banking platform for financial inclusion, squarely in the Digital Payments domain. Any institution — microfinance provider, bank or credit union — can run it, and deployment through the Mifos community across 400-plus institutions and millions of accounts proves it at scale.
- Apache Fineract: https://fineract.apache.org/
Layer 3 DPI Architecture Alignment
How the solution's architecture reflects the principles that distinguish DPI from conventional digitisation.
A · Interoperability
2/3Can other systems connect without modifying the core, using documented open standards?
A comprehensive REST API follows a headless, API-first design and is fully documented, returning JSON in standard financial data formats. ISO 20022, though relevant to the domain, is not prominently documented.
- API documentation: https://fineract.apache.org/docs/current/
B · Minimalist & Reusable Design
3/3Is it a modular building block that does one thing well, rather than a monolithic platform?
Loan, savings, client and accounting services are separate Spring Boot modules, and the headless core banking engine is cleanly separated from any user interface or application layer. Multi-tenancy makes it configurable for different country contexts without forking, as global deployments show.
- Documentation: https://fineract.apache.org/docs/current/
C · Ecosystem Enablement
3/3Can other public and private actors build on top of it?
The API-first design lets third parties build on it, with extensive Mifos community integrations and system integrators worldwide, plus 400-plus institutions running it independently. Apache Software Foundation governance under an Apache 2.0 licence is the strongest available guarantee against vendor lock-in.
- Apache Fineract: https://fineract.apache.org/
- Documentation: https://fineract.apache.org/docs/current/
D · Federation Readiness
1/3Can it run in distributed or federated deployments suited to national infrastructure?
Self-hosted deployment with an isolated database per tenant keeps data with the deploying institution. Each deployment is a single multi-tenant instance with no documented federation between instances, and high-availability clustering documentation is limited.
- Documentation: https://fineract.apache.org/docs/current/
E · Security & Privacy at Scale
2/3Does it meet the security and privacy bar for population-scale infrastructure?
Spring Security, encryption and multi-tenant isolation provide the security posture expected of financial services, with database isolation and regulatory compliance features protecting financial data. Vulnerability reports are handled by the Apache Security Team rather than through a Fineract-specific published policy.
- Documentation: https://fineract.apache.org/docs/current/
- Apache Fineract: https://fineract.apache.org/
Criteria: DPGs for DPI Collection criteria v2.0 · Co-stewarded by CDPI, Co-Develop and the DPGA Secretariat.
Spot something out of date? Contact the DPGA
