The Problem We Were Actually Solving

The truth, however, was that the client wanted to bypass the costs associated with Stripe and PayPal's foreign transaction fees, which can range from 3% to 4% above the domestic rate. They envisioned using Payhip or Gumroad, which promised a seamless integration and a lower cut. Our real goal was to find a solution that would allow us to maintain a single checkout process, irrespective of the client's location.

What We Tried First (And Why It Failed)

We began by integrating Payhip, a popular e-commerce platform that promised ease of use and minimal fees. We implemented Payhip's API, expecting it to work seamlessly with our font repository. However, we soon discovered that Payhip does not support payments in countries where PayPal is restricted, which is the case for several African nations and some Asian countries. Moreover, Payhip does not provide real-time updates, making it challenging to fulfill orders and manage inventory efficiently.

The Architecture Decision

We eventually decided to develop a custom solution using a combination of APIs from local payment gateways in these restricted countries. We chose a microservices architecture, where each service was responsible for handling a specific payment method. We implemented real-time updates using Webhooks and made sure our APIs were complaint with local regulations and security standards.

What The Numbers Said After

The numbers showed that our custom solution reduced transaction fees by up to 30% in countries with restricted payment options. We also observed a significant decrease in failed transactions, which had previously been a major issue with Payhip. Our clients were able to fulfill orders quickly and efficiently, and we reduced our support requests related to payments.

What I Would Do Differently

In retrospect, I would have factored in the potential integration challenges and regulatory complexities of using local payment gateways from the outset. I would have also considered integrating APIs from multiple payment gateways to provide clients with more payment options. Lastly, I would have included more provisions for testing and debugging our custom solution to ensure a smoother rollout.

In the end, our custom solution proved to be the more reliable and cost-effective option, despite the initial challenges. It taught us a valuable lesson about the importance of understanding the intricacies of global e-commerce platforms and the need for custom solutions in certain regions. As engineers, we often get caught up in the allure of off-the-shelf solutions, but it's essential to remember that sometimes, a carefully crafted custom solution is the only way to truly solve the problem at hand.