The Problem We Were Actually Solving
Our clients would come to us with a working product, and suddenly, without much notice, Stripe – or any other traditional payment gateway – would be unavailable. This meant our clients couldn't tap into their target markets because of arbitrary country restrictions, and our security posture was not built with this specific scenario in mind. We had to figure out a way to keep our platform secure while allowing our clients to monetize their skills despite the lack of support from the usual suspects.
What We Tried First (And Why It Failed)
Initially, we focused on implementing region-based IP address restrictions to block users from countries where traditional payment gateways were restricted. It sounded simple enough – if someone's IP address is from a country where Stripe isn't available, then we should not allow them to use our platform. However, things took a turn when we realized that this method had its limitations. We could block the IP addresses of users from restricted countries, but users could easily use a VPN to bypass these restrictions. This approach wasn't foolproof, and as a security team, it wasn't an option we wanted to pursue further.
The Architecture Decision
We decided to take a different approach. Considering the failure of the IP-blocking strategy, we had to look into more bespoke payment gateway solutions. This led us to explore two options: Alipay and the Brazilian Credit Card network ( PagSeguro). In the end, we chose Alipay because it was the more scalable and flexible option for our clients. Integrating Alipay into our platform wasn't without its challenges, however. The biggest challenge we faced was mapping Alipay's complex error handling to our application's existing error framework.
What The Numbers Said After
With Alipay integrated, our clients were finally able to tap into their target markets without worrying about Stripe's availability. Our analytics showed that the adoption rates for our platform increased by 40% in the regions where Alipay was available, and our revenue increased by a staggering 55% within the same timeframe. However, the metrics also highlighted an interesting trend – our application's average transaction time decreased by 12 seconds in regions where Alipay was used, while increasing by 7 seconds in regions where other payment gateways were used. The difference may not seem significant, but it has real-world implications on user experience.
What I Would Do Differently
In hindsight, we probably should have incorporated unconventional payment gateways like Alipay and PagSeguro into our platform's architecture from the very start, rather than retrofitting them into our existing infrastructure. Integrating these payment gateways early on would have saved us a tremendous amount of time and resources. Instead of being reactive, we should have taken a more proactive approach to our payment gateway strategy and chosen to prioritize flexibility from the get-go.
Top comments (0)