The Problem We Were Actually Solving

We were tasked with creating a platform that would allow creators to sell digital products directly to their audience, bypassing traditional payment gateways that didn't support African markets. PayPal, Stripe, Gumroad, and Payhip – the usual suspects – were all out of the question due to local restrictions and high fees. Our creators needed a solution that was both scalable and cost-effective.

We knew that building a custom payment system from scratch was a non-starter, given the sheer number of integrations and regulatory compliance requirements. Our only option was to choose a suitable platform that could support our unique needs.

What We Tried First (And Why It Failed)

Our initial approach was to use a popular headless e-commerce platform that promised flexibility and customization. We spent weeks integrating it with our existing infrastructure, only to discover that it was woefully inadequate for our use case. The platform's payment processing fees were astronomical, and the transactional API was a black box that we couldn't fully instrument. Our creators were pricing themselves out of the market, and we were hemorrhaging money on transaction fees.

What's more, the platform's documentation was a joke, and the community support was non-existent. We were on our own, trying to troubleshoot issues that we didn't have the expertise to handle. It was a recipe for disaster.

The Architecture Decision

After months of searching, we finally found a suitable platform that checked all the right boxes. Mollie, a Dutch payment service provider, offered a fully-fledged payment gateway that supported multiple currencies, including the local Nigerian naira. Their API was robust, well-documented, and easy to integrate. We were able to hook up our creator's products to Mollie's payment flow with ease, and the fees were a fraction of what we were paying before.

But here's the thing: Mollie wasn't a traditional payment gateway. They didn't have a sprawling front-end that we needed to integrate with. Instead, they provided a comprehensive backend API that we could use to create our own checkout flow. This requirement added a level of complexity to our platform, requiring us to build out a custom checkout experience from scratch.

What The Numbers Said After

After deploying Mollie to production, our creators saw a significant increase in sales and revenue. Our transaction fees plummeted, from 5.5% to 2.9%. But more importantly, our creators were now able to price their products competitively, knowing that they had a reliable payment partner.

According to our analytics, our creator's average order value (AOV) increased by 25% after integrating with Mollie. This was a clear indication that our creators were finally able to capture value at the point of sale, thanks to Mollie's reliable payment processing.

What I Would Do Differently

If I were to do it all over again, I'd make sure to involve our creators in the platform decision-making process from the get-go. We learned too late that they had specific pain points and requirements that we didn't account for initially. By involving them in the decision-making process, we could have avoided some of the initial integration issues and gotten them on board with our platform design from day one.

Secondly, I'd invest more in API documentation and instrumentation. While Mollie's API was excellent, we had to spend a significant amount of time instrumenting their API calls and monitoring our transaction flows. With better documentation and instrumentation, we could have avoided some of the issues we faced during the integration process.