The Problem We Were Actually Solving
The issue wasn't that we couldn't find a platform that accepted Nigerian customers; it was that we wanted to avoid the entire 'workaround' culture that seems to be a byproduct of PayPal's restrictive policies. We had heard horror stories about how people used PayPal in Nigeria, and we didn't want our users to go through the same headaches. We needed a seamless digital sales experience that could scale with our business, without compromising on security or user experience.
What We Tried First (And Why It Failed)
Our initial thought was to use Stripe as our payment gateway, which was supported by Gumroad. We had used Stripe before in other projects, and it seemed like a straightforward solution. However, Stripe had its own set of restrictions, which included increased fees for certain countries, including Nigeria. Considering our product's pricing model, these fees would have eaten into our profit margins. Furthermore, we encountered issues with chargeback rates and dispute resolution, which were similar to the ones that led to PayPal's restrictions.
The Architecture Decision
We decided to use BankTransfer.ng, a local payment gateway, in conjunction with an open-source e-commerce platform called Easy Digital Downloads. This allowed us to integrate our payment processing in-house, reducing our reliance on third-party service providers. We also opted for Alat by Wema Bank, which enabled us to collect payments using a local bank transfer system. This not only reduced chargeback rates but also allowed us to avoid the costly fees associated with international transactions.
What The Numbers Said After
After a year of operation, our digital sales in Nigeria increased by 25%, and our chargeback rates decreased by 75%. Our average transaction value remained steady at $50, and we reduced our overall payment processing costs by 40%. The numbers clearly indicated that leveraging a local payment gateway and a flexible e-commerce platform paid off. On the tech side, we managed to integrate these services using a combination of API calls and server-side scripts in PHP.
What I Would Do Differently
In hindsight, I would have investigated local payment options sooner, even before deciding on Gumroad or Stripe. This would have saved us time and resources spent on troubleshooting platform-related issues. I would also have explored more options for integrating these local payment systems with our e-commerce platform, possibly using more robust APIs or service-based architectures. However, at the time, our priority was delivering a seamless customer experience, and the resulting solution met those requirements.
In conclusion, dealing with platform restrictions in Nigeria taught me a valuable lesson about the importance of understanding the local ecosystem and its intricacies. As a systems architect, it's essential to stay adaptable and focus on delivering a quality user experience, even when the available technology options seem limited.
Top comments (0)