Integrating any sort of technology into the developing world requires a deep understanding of the available tools and usage patterns. The degree of difficulty — already considerable — increases exponentially when you’re dealing with bank and financial software.
The Grameen Foundation’s Mifos Initiative is tackling those integration challenges in a unique way. Rather than develop proprietary software with hundreds of country-by-country variations, Mifos is making its code available via open source. Financial institutions can repurpose the software for their unique microlending needs.
In the following Q&A, Mifos director of engineering Adam Feuer explains the rationale for pursuing the open source option. He also discusses some of the unique mobile and integration challenges his team is encountering.
Mifos is an open source technology. Why did you go that route?
We chose open source for several different reasons. Transparency is one: We believe that banking software, especially microfinance software used in the developing world, needs to be transparent and open. That means open source so that people can see how it works and verify that it’s operating correctly.
We also believe Mifos should be free so you can modify the software and make it suit your application. If we went out of business (not likely to happen but it is possible), or if people didn’t like the direction we were going, they wouldn’t be stuck with what we had accomplished or the direction we were going. That helps banks feel a lot more secure.
How many contributors are touching the code?
AF: Mifos is a small open source project, but it’s spread all over the world. Twenty of the 40 or so contributors are paid by the Grameen Foundation and they directly report to me. Another 10 contributors are third-party developers who are working with us to develop software. They work for partner organizations. Another 10 or 15 are volunteer developers who are just contributing to make the world a better place.
How are you addressing mobile?
AF: In Africa and India you send SMS messages with your phone to access your bank account. It takes a few messages back and forth to move money from one account to another or to make a payment. But it’s way better than having to drag yourself across a dusty city and use public transport to visit a bank branch where people may or may not discriminate against you because you’re poor. Toward that end, we’re integrating with a major mobile money system in Africa, a prototype called M-PESA. There’s also a mobile money system in India that we’re looking at for pilot projects.
What are the major challenges you’re encountering?
AF: Information technology in the developing world is a challenge for a variety of reasons. One of them is finding power to run a computer. Finding a good Internet connection is also challenging. We have to design our software to work in these conditions.
Another problem is that if you know information technology in say Kenya or India, you can get a better job. So microfinance banks have a hard time keeping employees that know anything about computers. We have to design our software so that it’s relatively easy to use and easy to learn. You can be sure that you’ll be training new people on it very frequently.
The main challenge that we are facing right now is how to open Mifos up in a modular way so that we can enable someone to write a plugin to customize Mifos for their particular country or environment. We see supporting plugins as the way to welcome everybody in the world to the promise of usable financial services for the poor.
This excerpt was edited, condensed and adapted for Radar. The full interview, available at the PayPal Developer Network, is part of a collaboration between O’Reilly and PayPal exploring the future of payment.
- The State of the Internet Operating System
- Thoughts from the front lines of payment’s big shift
- PayPal Taps the Developer Community to Build Next-Gen Payment Apps
- The Convergence of Advertising and E-commerce