THEIR CHALLENGE
Using MongoDB Atlas to enhance scalability and enable growth for Nsano
In the Twi dialect of Ghana’s Akan language, Nsano means, ‘fingertips.’ The word neatly articulates the eponymously named fintech’s mission: to make financial services readily available and accessible for all. Nsano was founded in 2013 and is headquartered in Ghana’s capital, Accra. Nsano specializes in digital payments processing, striving to democratize how e-money moves across Africa by reinventing financial service delivery with technology-driven solutions. Nsano's vision is to process 50% of Africa's GDP by 2030, offering frictionless, low-cost payment solutions that address multi-currency challenges, fraud, and data privacy. By partnering with banks, businesses, and financial institutions, Nsano aims to scale digital payments across borders.
The company’s range of services includes mobile money aggregations, cross-border remittance, and bulk transaction processing. They currently have footprints in over 30 African countries, and the UK, with regional offices in five African countries—Ghana, Liberia, Zambia, Cote d'Ivoire, and Sierra Leone—Nsano aims to cover the rest of Africa before 2025.
Christian Glouin, Chief Technology Officer at Nsano started as a software engineer and has witnessed its trajectory. “When we first started building the platform, we didn’t have a proper orientation as to where we were going to end, therefore having a fully structured database was out of the question,” he explained. “Content was rapidly changing, and we needed something that was flexible. That is what led us initially to MongoDB.”
The team started its journey with MongoDB Community 3.6. But as Nsano’s operations grew, they began to struggle with managing it themselves, and moved to a third-party managed instance of the database. Within a year there were issues. “The software changes and upgrades we were doing led to bottlenecks,” said Glouin. “For every 1,000 requests into the database, some were simply failing.” Other pain points were consistently slow reads and writes, considerable downtime, and failure to hit uptime SLA for customers. Moreover, with its existing platform Nsano was unable to scale, the team was self-managing security, and paying around £24,000 a year for a free version that could have been managed in-house.
OUR SOLUTION
Acquiring the flexibility to manage rapidly changing content
Frustrated by the challenges of using the third-party managed MongoDB Community 3.6 version, Nsano began to consider alternatives – at one stage looking to re-platform to a relational SQL-based solution. It was a fortuitously timed approach by MongoDB in December 2023 that resulted in them moving instead to MongoDB Atlas. “The reason we chose MongoDB from the get-go was because we needed the flexibility to add objects or details on the fly without having to change a system all the time,” said Glouin. Already familiar with MongoDB’s technology, if not specifically the MongoDB Atlas interface, Nsano were nevertheless pro-support customers, meaning they received four days of funded consultancy.
That arrangement helped accelerate the migration from Nsano’s legacy third-party managed MongoDB Community to a MongoDB Atlas supported version. “It was a straightforward operation,” said Glouin of the process, which began in May and concluded in July 2024. Any challenges that did exist were largely internal – code that needed to be optimized in some areas to ensure the database could be moved quickly, for example. After that, “things went very smoothly,” said Glouin. “I didn’t have to do a rollback, all the processing issues I was having with our legacy version just disappeared.” Occasionally Glouin receives alerts about queries that need to be optimized. “It’s insightful for us, because we can rely on the automated suggestions of the system to improve our services,” he added.

