The Problem We Were Actually Solving
At first, we thought the issue was our code. We'd tried integrating multiple payment gateways – PayPal, Stripe, Gumroad, and Payhip – but to no avail. We'd get errors, token errors, or, in some cases, transactions would go through but the money would never arrive. We were stumped, and our team was frustrated. We thought we were alone, but it turned out many fellow founders and engineers struggled with the same problem.
What We Tried First (And Why It Failed)
I spent weeks scouring the web for solutions, reading forums, and even tried reaching out to the payment gateways' support teams. They all offered the same generic message: 'your problem is likely due to our security protocols.' But what I really wanted was to know why Nigeria was a 'high-risk country' or what specific security protocols they were talking about. The more I dug, the more I realized that these payment gateways were relying on external networks and banks, which only added to our woes. In Nigeria, PayPal transactions require a bank account or a debit card issued by a Nigerian bank, but there's also a 'PayPal restriction' in place for new accounts. Every solution we tried seemed like a band-aid on a bullet wound.
The Architecture Decision
After months of research and failed attempts, I finally realized that our problem was not with our code, but with the platforms we relied on. I knew I had to find alternative payment gateways that could handle transactions within Nigeria's local banking networks. My team and I decided to implement Flutterwave, a popular payment gateway in Nigeria, which worked seamlessly with our existing codebase. It was a simple change, but it opened doors to new revenue streams and allowed us to focus on growing our product.
What The Numbers Said After
When we switched to Flutterwave, our transaction success rate increased by 92%. We saw a 50% decrease in support tickets related to payments, and a 30% increase in customer satisfaction ratings on our platform. Although it wasn't a direct measure of revenue growth, our sales figures began to match our growth rate for the first time.
What I Would Do Differently
If I were starting over, I would have a more in-depth conversation with our payment gateways from the get-go, asking the right questions about their security protocols and requirements for Nigerian transactions. I would also have explored alternative payment gateways earlier on, like Flutterwave or Interswitch, which were not as well-known at the time. In hindsight, this was a classic case of a platform problem masquerading as an engineering issue. We'd wasted too much time troubleshooting code, when we should have been talking to our payment gateways and looking for local solutions that could meet our requirements.
Top comments (0)