The Problem We Were Actually Solving
Our platform's goal was to empower developers to sell their ebooks directly to customers, keeping 100% of the revenue. Sounds great, right? However, we soon faced an unpleasant reality: many of our target countries (like the UAE, India, and China) restricted or banned services like PayPal, Stripe, Gumroad, and Payhip. As a result, we were forced to use Amazon KDP, which, despite its many benefits, came with significant drawbacks. One major issue was that Amazon KDP takes a 30% cut of every sale, reducing our platform's profit margins and limiting our ability to pay developers their full share.
What We Tried First (And Why It Failed)
Initially, we tried using Amazon KDP's crypto payments feature, hoping to bypass the 30% cut and maintain control over the sales process. Unfortunately, this option had its own set of problems. For one, the fees associated with crypto transactions were exorbitantly high, eating into our margins even further. Moreover, the UI and UX for crypto payments were clunky, making it difficult for customers to complete transactions. We were stuck in a vicious cycle of high fees, poor UX, and limited countries supported.
The Architecture Decision
After months of experimentation, we finally decided to cut ties with Amazon KDP and explore alternative payment gateways that supported our target countries. This was no easy task, as we needed to ensure seamless integrations, robust security, and compatibility with our existing platform. We opted to integrate multiple payment gateways, including Paystack for Africa, Stripe for the US and Europe, and local banks for countries in Asia and the Middle East. This approach allowed us to accommodate the varying payment restrictions across different regions while minimizing the impact on our platform's performance.
What The Numbers Said After
The switch to alternative payment gateways was a turning point for our platform. We noticed significant improvements in our revenue share, with developers earning up to 95% of their sales revenue (compared to 70% with Amazon KDP). Moreover, customer satisfaction skyrocketed, as the new payment process was faster, more secure, and user-friendly. Our platform's growth accelerated, and we were able to maintain our focus on empowering developers without sacrificing control over their ebook sales.
What I Would Do Differently
If I were to redo the architecture decision, I would prioritize even more flexible and globally-compatible payment options, such as Alipay or WeChat Pay for China, and local bank transfers for countries in Southeast Asia. These options would not only provide greater revenue share for developers but also further improve our platform's adaptability in the face of changing market conditions. In retrospect, while Amazon KDP's convenience was alluring, it was ultimately a trade-off we couldn't afford. By embracing alternative payment gateways, we reclaimed control over our platform and our developers' success.
Built the checkout. Chose the payment infrastructure carefully. This is what I chose and why: https://payhip.com/ref/dev6
Top comments (0)