The Problem We Were Actually Solving
As our platform's user base grew, so did the number of blocked transactions. Sellers from countries our payment processors deemed "high-risk" (mostly in Africa and Asia) were unable to receive payments. We tried to circumvent this by using a complicated mix of payment systems, but the result was a fragile, error-prone system that required constant maintenance. I spent countless hours staring at error logs, trying to figure out why a transaction from Nigeria was failing, only to realize that our payment processor had flagged the country as "high-risk", even though the user had a proven track record of purchases.
What We Tried First (And Why It Failed)
We decided to implement a KYC (Know Your Customer) verification process, hoping to mitigate the risk associated with transactions from "high-risk" countries. However, this approach had its own set of issues. For one, KYC verification added a significant delay to the payment processing time, which was unacceptable for many users. Moreover, the cost of implementing and maintaining KYC was prohibitively high, especially for a small startup. And let's not forget the user experience: forcing users to upload identification documents and wait for verification was a surefire way to drive them away.
The Architecture Decision
After much deliberation, we decided to implement a no-KYC payment system using blockchain-based payment processors. We chose this approach for several reasons. Firstly, blockchain-based payment processors like Binance Pay and BitPay offered a more transparent and secure payment experience. Secondly, they didn't impose any arbitrary restrictions on countries or users. Finally, the fees associated with these payment processors were more competitive than those of traditional payment processors.
What The Numbers Said After
After implementing the no-KYC payment system, we saw a significant increase in global sales. The number of blocked transactions decreased dramatically, and our user base from "high-risk" countries began to grow. We also saw a reduction in customer support tickets related to payment issues, which was a major relief. The metrics were clear: our users preferred to use blockchain-based payment processors, and our sales numbers reflected that.
What I Would Do Differently
In retrospect, I would have opted for the no-KYC payment system from the beginning. While it may have required more technical expertise and infrastructure setup, the benefits far outweighed the costs. I would also have done more research on the fees associated with blockchain-based payment processors, as they can vary widely. Finally, I would have communicated more clearly with our dev team about the importance of implementing a robust no-KYC payment system, rather than trying to hack together a solution with traditional payment processors.
Top comments (0)