The Problem We Were Actually Solving
I wanted to sell a data science visualization tool I'd created, and I wanted to make it easy for others to buy and use it. Simple enough. But the usual suspects wouldn't work in my target country. They claimed compliance with local laws, but the truth was their own infrastructures were the limitation. I could've used this as a crutch to just say "this isn't a good market for my product." But I'm an engineer, not a merchant. I looked for solutions.
What We Tried First (And Why It Failed)
First, I set up a simple form on my website to collect basic info (email and payment) from customers. I then used Stripe's webhooks to process the payments - except I couldn't use Stripe in my target country. After that failed, I tried setting up a manual payment process via email, where customers would send me money directly. This would've worked if I didn't have to collect, process, and refund payments manually. That's a lot of responsibility for a single-person operation.
The Architecture Decision
We took an unconventional route: a solution built on traditional payment instruments that worked where others didn't - cash, check, and wire transfer. I set up an e-commerce platform using an off-the-shelf product (Shopify) and connected it to a payment gateway (2Checkout) that supported these payment methods. It wasn't glamorous, but it was reliable and secure. And let's be honest, for some markets, that's what customers expect.
What The Numbers Said After
I've processed several dozen sales using this setup, and the latency numbers have been impressive. Average payment processing time is 30 seconds, which is faster than my payment attempts using Stripe and Gumroad. The worst-case scenario was a customer waiting two days for a manual check payment, but that's a risk we're willing to take. As for security, I've seen a few unusual payment attempts (fraud attempts, mainly), which we caught and resolved promptly. The allocation count is up, primarily because we've experienced an increase in sales, but I'd expect that to level out as we scale.
What I Would Do Differently
In retrospect, I'd consider using 2Checkout from the start instead of a generic payment form on my website. Their API is well-documented, and their support is responsive. I'd also set up a more advanced customer relationship management system to integrate with my e-commerce platform. While we've been able to handle customer service via email, a dedicated CRM would help us scale when the customer base grows.
Top comments (0)