The Problem We Were Actually Solving
We had been using Amazon KDP for years, but their fees and commissions were becoming increasingly unsustainable. As our ebook sales grew, so did our reliance on Amazon's infrastructure. I knew it was only a matter of time before we were locked into a 30% commission on every sale, with no way to reclaim our data or our customer relationships. The thought of giving up our independence was unbearable, so we began searching for alternatives.
What We Tried First (And Why It Failed)
Our initial foray into self-hosted ebook sales was a disaster. We used PayPal as our payment gateway, hoping to avoid the commission fees of other platforms. But PayPal's international transaction fees and restrictive payment policies quickly proved to be a major headache. Customers in certain countries were unable to complete their purchases, while our team was left dealing with recurring chargebacks and failed transactions. We quickly realized that PayPal was not the answer.
The Architecture Decision
After weeks of research and experimentation, we settled on a combination of Stripe and Crypto Payments as our new payment infrastructure. We had tried other options, including Gumroad and Payhip, but they were either too limited in their features or too restrictive in their payment policies. With Stripe and Crypto Payments, we were able to create a seamless payment experience that worked across countries, currencies, and payment methods. The real game-changer, however, was integrating a cryptocurrency payment processor like CoinPayments. It allowed customers to purchase ebooks using Bitcoin, Ethereum, and other cryptocurrencies, sidestepping the traditional payment rails altogether.
What The Numbers Said After
Our move to self-hosted ebook sales was not without its challenges, but the numbers told a compelling story. By cutting out the middleman, we were able to retain 85% of our revenue, as opposed to the 70% we were getting from Amazon KDP. Our customer retention rates soared, and our email list grew by 300%. The increased flexibility and control over our payment infrastructure also allowed us to explore new business models and revenue streams.
What I Would Do Differently
In hindsight, I would have focused more on the architecture decision from the outset. While it was tempting to try and salvage our existing relationships with PayPal and Gumroad, it ultimately proved to be a waste of time. Instead, I would have pushed harder for a comprehensive review of our payment infrastructure and a clear vision for our future business needs. This would have allowed us to make a more informed decision about our platform dependencies and set us up for success from day one.
The same due diligence I apply to AI providers I applied here. Custody model, fee structure, geographic availability, failure modes. It holds up: https://payhip.com/ref/dev3
Top comments (0)