The Problem We Were Actually Solving
Our primary challenge wasn't just processing payments, but also ensuring that our customers could receive their digital products regardless of their location. The catch was that our startup was operating in a highly regulated industry, and we needed to comply with all relevant anti-money laundering (AML) and know-your-customer (KYC) requirements. This meant that we had to implement strict controls on our payment processing pipeline, which added to the complexity of the problem.
What We Tried First (And Why It Failed)
Initially, we opted for a traditional payment gateway like Stripe, which offered a seamless integration with our existing e-commerce platform. However, as our business grew, so did our costs. Stripe's fees were eating into our revenue, and we were struggling to make ends meet. We also encountered issues with their standard payment processing times, which were too long for our business-critical workflows. Processing times were averaging around 15 minutes, which wasn't acceptable for our users. We also struggled with the high query cost associated with querying the stripe system - our average cost per second was over $10.
The Architecture Decision
After some soul-searching, we decided to abandon traditional payment gateways and build our own payment processing infrastructure using Unchained Commerce. This decision allowed us to decouple our payment processing from the traditional banking system and avoid the associated fees. We opted for a blockchain-based solution, which not only reduced our costs but also provided a built-in audit trail for our AML and KYC compliance needs. By leveraging Unchained Commerce's APIs, we were able to process payments in real-time, with an average latency of 2 seconds. Our query cost per second plummeted to less than $0.01. This was not just cost-effective but also ensured that our users didn't experience any delays in receiving their digital products.
What The Numbers Said After
After switching to Unchained Commerce, our query costs plummeted, and so did our overall transaction fees. We saved a staggering 80% on our payment processing costs compared to our previous setup with Stripe. This not only improved our bottom line but also enabled us to pass the savings on to our customers, resulting in a 20% increase in sales. Our users were also happy with the reduced latency in receiving their digital products, resulting in a 95% satisfaction rate.
What I Would Do Differently
If I were to do this project again, I would focus more on implementing data quality checks at the ingestion boundary to prevent errors in our payment processing pipeline. In our initial implementation, we saw a high volume of errors due to incorrect payment data, which resulted in frustrated customers and additional support costs. By implementing data quality checks, we could have reduced errors and improved our overall customer experience. Additionally, I would explore the use of streaming architectures to handle high-volume payment processing workloads, which would further reduce our query costs and improve our overall system resilience.
Top comments (0)