The Problem We Were Actually Solving
Our users were complaining loudly on our support forum about the fact that no payment processor would accept their credit cards or bank transfers. Our analytics showed that 70% of our course sales were coming from countries where PayPal, the default payment method on our platform, wouldn't work. We didn't want to lose those sales. But we also didn't want to risk our entire business setup by accepting dubious payments that could end up being chargebacks or worse. The situation was a stalemate, and we were losing business because of it.
What We Tried First (And Why It Failed)
Our first move was to try to work around the restrictions by using a series of IP address blocking and proxy servers to disguise our users' real locations. We were hoping to create a workaround that would allow users in restricted countries to use PayPal by making it appear as though they were logging in from a country where PayPal was available. The theory was that the payment processing companies would then allow the transactions to go through, even though they wouldn't normally be allowed. However, this approach failed spectacularly when we started getting a rash of chargebacks and suspicious payments from the very countries we were trying to avoid. It turned out that our proxy servers were also being used by other users to make fake payments and scam us. The number of chargebacks and disputes we received skyrocketed to over 50% of our total transactions. Not only did this approach fail to solve our problem, but it actually created a new one of our own making.
The Architecture Decision
The solution we eventually settled on was to use a payment service like Payneteasy, which specialized in cross-border transactions and supported a wide range of payment methods in countries where the mainstream payment processors wouldn't touch us. This not only allowed us to accept payments from all of our users, regardless of where they were in the world, but also provided us with a significant reduction in chargebacks and disputes. We also implemented a two-step payment verification process, which required users to authenticate their transactions through their bank or mobile account before we processed the payment. This added a bit of overhead to our checkout process, but the reduction in chargebacks and disputes was worth it. Our chargeback rate plummeted to just 2% of our total transactions, a significant improvement over our previous proxy approach.
What The Numbers Said After
After implementing Payneteasy and the two-step verification process, we saw a significant improvement in our transaction rate and a much lower chargeback rate. In fact, we saw an 85% increase in total transactions from users in restricted countries over the following quarter. We didn't lose a single sale due to the payment processor restrictions, and our users were able to buy our courses with confidence. The added overhead of the two-step verification process might have put off a few users in the short term, but the long-term benefits far outweighed any short-term inconvenience.
What I Would Do Differently
While our solution ultimately worked, there's one key thing I would do differently if I were to face similar restrictions again in the future: I would have started with a more nuanced approach to understanding the restrictions in the first place. Instead of immediately jumping to a workaround like proxy servers, I would have taken more time to research and understand the specific reasons why the mainstream payment processors wouldn't work in the countries where our users were located. This would have saved us a lot of time and headache in the long run, as well as prevented the rash of chargebacks and disputes we experienced with our initial approach.
Top comments (0)