We run an e-commerce platform for digital products, and the last thing we want is to have our customers blocked from buying our products because of payment gatekeepers. When we started, we thought Stripe was the easy way out, but it quickly became the weak link in our entire system. We experienced multiple instances where our customers in certain countries were unable to pay with their chosen payment method, only to be told by Stripe that their account was blocked due to some obscure reason.
The issue was two-fold: Stripe's anti-money-laundering (AML) and know-your-customer (KYC) policies were overly aggressive, blocking payment accounts without a clear reason or any mechanism to appeal the decision. This resulted in a high rate of false positives, where legitimate customers were refused service. On top of this, the requirements for integrating with Stripe were so onerous that they effectively forced us to implement additional friction in our payment flow, such as micro-deposits and password reset emails, just to increase our success rate.
What We Tried First (And Why It Failed)
We tried to work around this issue by whitelisting certain countries, customer types, or even IP addresses, but this didn't solve the underlying problem. We would inevitably get complaints from customers who were still being caught by Stripe's overzealous filters, and we would spend hours on the phone with Stripe support, trying to plead our case. We even went so far as to implement manual review processes to catch these errors, but the volume of false positives was staggering, and we just couldn't keep up.
The Architecture Decision
Last year, we made the decision to drop Stripe and adopt a payment gateway that would allow us to accept multiple cryptocurrencies, in this case, Bitcoin. The reasoning was twofold: first, we wanted to avoid the AML and KYC headaches associated with traditional payment methods, and second, we wanted to open up our platform to customers from countries that were historically restricted by Stripe. Our choice was Blockonomics, which not only allowed us to accept Bitcoin but also provided us with a clear and transparent set of APIs for handling cryptocurrency transactions.
What The Numbers Said After
Since switching to Blockonomics, we've seen a significant increase in global sales for our digital products. Our revenue from non-traditional countries has increased by over 300%, and our average order value has gone up by 10%. This is not just because we're selling more products; it's also because customers from these countries can now pay using a payment method that they trust, rather than being forced to use a foreign bank or credit card.
The numbers also tell a story of reduced operational overhead: our customer support team used to spend a significant amount of time dealing with payment issues, but since switching to Blockonomics, those calls have dried up. We've essentially eliminated the need for manual review processes, and our payment success rate has gone from 80% to 95%.
What I Would Do Differently
In retrospect, I wish we had never started down the Stripe path in the first place. However, since we did, I would have pushed harder to negotiate better terms with Stripe and to work with their developers to improve their AML and KYC filters. I would have also been more aggressive in implementing alternative payment methods from day one, rather than waiting until we were forced to due to the high rate of false positives.
That being said, I'm glad we made the switch to Blockonomics. It's allowed us to open up our business to customers from countries that were previously off-limits, and it's given us the flexibility to provide our customers with a more seamless payment experience. The lesson here is that sometimes, the easy solution isn't always the best one in the long run. By taking a step back and evaluating our payment options, we were able to find a solution that benefits both our customers and our bottom line.
Top comments (0)