We were selling a product that didn't want to be a product in the classical sense – a digital learning platform that offered courses and tutorials on a very niche topic. The catch was that we wanted to sell it to anyone, anywhere in the world. Easy enough, right? Except that our platform of choice (a well-known marketplace) refused to let us because of our location – in a country that, for all intents and purposes, was considered "high-risk" by the likes of Google and Amazon.
The Problem We Were Actually Solving
We weren't just trying to solve the problem of restricted sales; we were trying to solve it without breaking a sweat. We were a small team, and compliance (or the lack thereof) was starting to get in the way of our core business – developing and selling quality content. We knew that we needed to find a payment method that didn't require any sort of Know Your Customer (KYC) verification, but the more pressing concern was finding something that wouldn't take away from the user experience.
What We Tried First (And Why It Failed)
Our first attempt was to use a well-known cryptocurrency service, thinking that the anonymity of crypto would be the perfect solution. The reasoning went that if transactions were decentralized and anonymous, we wouldn't have to worry about pesky KYC regulations. The problem was that we were completely unable to get the service to integrate properly with our existing payment infrastructure. The errors were always cryptic and hard to debug, and more often than not, we'd end up with abandoned transactions and frustrated customers.
The Architecture Decision
What ended up working for us was a combination of a bespoke payment gateway and a cleverly designed payment flow. We chose to go with a payment gateway that supported multiple currencies and payment methods, including those that didn't require KYC verification. We then implemented a custom payment flow that handled the complexities of cross-border payments and currency conversions. The key insight was to decouple the payment processing from the rest of our application, allowing us to handle the payment flow in a separate, headless process that didn't require any sensitive user data.
What The Numbers Said After
The immediate benefits were clear – we were able to process payments from customers in over 150 countries, and our sales figures skyrocketed. But more importantly, we were able to do it all without sacrificing user experience. Our customers were able to purchase our content without having to go through the hassle of verification, and we were able to avoid the costly and time-consuming process of compliance.
What I Would Do Differently
If I were to do it all over again, one thing I would change is the way we handled errors and exceptions. Our bespoke payment gateway was prone to errors, and we ended up spending a lot of time debugging and troubleshooting. In retrospect, I think it would have been better to use a more tried-and-true solution, even if it meant sacrificing some of the flexibility and customization that we got with the bespoke solution. As it stands, our payment flow is still a bit fragile, and we have to monitor it closely to avoid any issues.
Top comments (0)