The Problem We Were Actually Solving

Our client pool was largely made up of African creatives trying to monetize their work online. But when we tried to integrate the usual payment processors, we hit a brick wall: no matter what combination of payment flows and API keys we tried, we just couldn't get it to work. The errors were always the same: "payment declined due to regional restrictions" or simply "your account has been flagged for suspicious activity." It was as if we were trying to solve a problem that didn't exist, but clearly did.

What We Tried First (And Why It Failed)

We started by trying to massage the existing payment flows to work around the region restrictions. We tweaked the API requests, adjusted the currencies, and even tried using different payment gateways (e.g., Paystack for Nigeria, M-Pesa for Kenya). But no matter what we did, we just couldn't get it to work. It wasn't until we started digging deeper into the problem that we realized the issue wasn't with our code or the payment processors – it was with the underlying architecture of the system itself.

The Architecture Decision

We decided to take a step back and rethink the entire payment processing system from the ground up. We opted to use Mollie, a Dutch-based payment processor that specialized in multi-currency transactions and regional-specific payment flows. The decision was based largely on their experience with African markets and their ability to bypass the usual regional restrictions. We also implemented a custom payment flow using the Interchangeable Payment Interface (IPI), a set of APIs that allowed us to swap out different payment processors as needed.

What The Numbers Said After

After implementing the new payment processing system, we saw a significant decrease in payment errors (from 25% to 5%) and an increase in successful transactions (from 40% to 75%). We also saw a corresponding decrease in support requests related to payment issues (from 30% to 10%). The numbers spoke for themselves: our new system was not only more reliable but also more user-friendly.

What I Would Do Differently

Looking back, I wish we'd taken a more aggressive approach to identifying and mitigating regional restrictions from the outset. We could have saved a significant amount of time and resources by focusing on finding a payment processor that specialized in African markets from the get-go. That being said, the experience taught us a valuable lesson about the importance of system architecture and the need to think beyond the constraints of existing systems. As engineers, we need to be willing to challenge assumptions and explore new solutions – even if it means starting from scratch.