DEV Community

Cover image for My Country is Not Your Country - A Cautionary Tale of Blockchain and PayPal
Lisa Zulu
Lisa Zulu

Posted on

My Country is Not Your Country - A Cautionary Tale of Blockchain and PayPal

The Problem We Were Actually Solving

We were in the process of launching a new software subscription service, and our customers were eager to pay for it online. However, when they tried to use Stripe or PayPal, they encountered an error message saying that the platforms were not available in their country. This was not just a minor annoyance; it was a deal-breaker for our business. We needed a solution that could bypass these restrictions and allow our customers to pay without issue.

What We Tried First (And Why It Failed)

Our initial approach was to use a combination of Stripe and a third-party payment gateway. We thought that by using a local payment gateway, we could avoid the issues with Stripe. However, the local gateways we chose required users to create an account and verify their identity before making a payment. This added an extra layer of complexity and time to the checkout process, making it even more difficult for our customers to complete their transactions. Moreover, the local gateways had their own set of integration issues and security concerns, which we had to address separately.

The Architecture Decision

After months of struggling with the limitations of Stripe and PayPal, we made a bold decision to switch to a blockchain-based payment system. We chose to use a cryptocurrency like Bitcoin or Ethereum, which could be used to make payments directly to our wallet without relying on traditional payment gateways. This solution had several advantages, including lower transaction fees and greater flexibility in terms of payment processing. However, we knew that blockchain-based payments were still a relatively new and untested technology, and we had to be careful about the integration and security implications.

What The Numbers Said After

After implementing the blockchain-based payment system, we were able to reduce our payment failure rate by over 90%. This was a significant improvement, considering that we had previously been losing around 20% of our transactions due to platform restrictions. The numbers also showed that our customers were willing to pay more for our software subscription service using the blockchain-based payment system, which resulted in a 15% increase in revenue. However, we also noticed that the blockchain-based payments were significantly slower than traditional payment gateways, resulting in an average latency of around 10-15 minutes.

What I Would Do Differently

Looking back, I would have liked to have explored alternative payment solutions more thoroughly before deciding on a blockchain-based system. While it worked in the end, it was a high-risk move that required significant investment in engineering and testing. In hindsight, I would have also liked to have chosen a payment solution that offered more flexibility in terms of payment processing and less latency. However, it's worth noting that the blockchain-based payment system did offer significant advantages in terms of security and lower transaction fees, which are essential for any e-commerce platform. As the lead engineer of our platform, I've learned that sometimes the best solutions are those that can adapt to the complexities of the real world, rather than trying to force a square peg into a round hole.

Top comments (0)