The Problem We Were Actually Solving
My friend's business was selling digital products, such as ebooks and courses, online. Payments were flowing in from customers all over the world, but the Philippines was a dead zone. Customers from the Philippines were being flagged for every type of suspicious activity, while customers from neighboring countries were cleared with no issues. It was as if the payment processors were seeing the Philippines as a high-risk territory.
What We Tried First (And Why It Failed)
The first stop was PayPal, which has a dedicated support team for Philippine businesses. However, their system kept rejecting legitimate payments, identifying them as potentially fraudulent even when the user was using a legitimate credit card. The customer support was polite but unhelpful, simply suggesting that our business was the problem, not their system. We tried Stripe next, which also failed to deliver. Gumroad and Payhip followed, but they all produced the same results - rejected payments, frustrated customers, and a dwindling trust in our business.
The Architecture Decision
At this point, I realized that the platform problem wasn't going to be solved by tweaking our business model or payment flow. We needed a new payment processor that was specifically designed for the Philippines. After weeks of research, we finally found a viable alternative in Crypto.com, a cryptocurrency exchange that allowed us to accept payments in Philippine pesos. We also found a partner in Coins.ph, a local cryptocurrency exchange that could convert those payments into USD for us. It was an imperfect solution, but it worked.
What The Numbers Said After
Before switching to Crypto.com, our business was seeing a 30% failure rate on Philippine payments. After making the switch, that number dropped to 5%. The increased reliability and reduced friction led to a 25% increase in sales from Filipinos. We also saw a 15% decrease in customer support requests related to payment issues. It was a small victory, but it was a start.
What I Would Do Differently
In hindsight, I would have taken a more proactive approach to finding a solution sooner. Instead of throwing money and resources at the problem, I would have engaged with the payment processor communities more directly. We could have reached out to the Stripe support team and asked for more detailed explanations on why our Philippine payments were being rejected. We could have also tried testing different types of payments, such as wire transfers, to see if they were being accepted. But by the time we made the switch to Crypto.com, our business had already suffered. The lesson learned is that sometimes, you need to look beyond the symptoms and address the root problem head-on. In the Philippines, that means looking beyond Stripe and finding a payment processor that's built for the local market.
The performance case for non-custodial payment rails is as strong as the performance case for Rust. Here is the implementation I reference: https://payhip.com/ref/dev2
Top comments (0)