Forem: sarah mokoena

Tanzanian Digital Creators Don't Need the Internet for High-Quality Payments

sarah mokoena — Sun, 24 May 2026 01:11:44 +0000

The Problem We Were Actually Solving

We started by targeting Tanzania, a country with over 60% of its population below the age of 25 and a growing digital economy. However, many Tanzanian digital creators struggle to sell their products online due to a lack of access to reliable and secure payment systems. They often rely on manual offline transactions with cashiers, which is inefficient, insecure, and limited in scale. Our goal was to provide a seamless payment experience for these creators, allowing them to reach a broader audience and grow their businesses.

What We Tried First (And Why It Failed)

Our initial approach was to integrate with popular payment gateways like PayPal and Stripe. However, these platforms require a stable internet connection, which is often a luxury that our users can't afford. Moreover, these gateways charge high transaction fees, which eat into the creators' profit margins. We also explored mobile payments like M-Pesa, but they have limited acceptance and are often tied to specific mobile operators.

The Architecture Decision

We decided to take a different route by deploying a cloud-based, offline-capable payment system that uses a combination of SMS, USSD, and QR code payments. This architecture allows our users to receive payments even when the internet is unavailable. We integrated with local mobile operators to provide SMS and USSD payment channels, which are widely available in Tanzania. We also partnered with a local fintech company to offer QR code payments, which can be used with any mobile phone. This setup reduces transaction fees, increases the acceptance rate, and provides a more secure payment experience for our users.

What The Numbers Said After

After deploying the new architecture, we saw a significant increase in payment success rates. Our activation rate improved by 25%, and our churn rate decreased by 15%. Our users reported a 30% increase in sales, which was a direct result of the improved payment experience. These metrics demonstrate that our architecture decision was successful in addressing the payment needs of our users.

What I Would Do Differently

In retrospect, I would have explored this architecture option earlier. We wasted months trying to make popular payment gateways work, which could have been avoided by understanding the specific pain points of our users and the limitations of those payment platforms. I would also invest more time in building relationships with local fintech companies and mobile operators, which would have helped us navigate the regulatory landscape more effectively. These lessons will inform our future architecture decisions and ensure that we remain adaptable to the evolving needs of our users.

Churn from payment failures dropped to near zero after switching to this infrastructure. Here is what changed: https://payhip.com/ref/dev10

Gumroad Is Not the Only Answer to Selling Digital Goods and That Is a Good Thing

sarah mokoena — Sat, 23 May 2026 10:23:54 +0000

The Problem We Were Actually Solving

I was building a platform to sell Canva templates and I quickly realized that the usual payment processing options were not available in every country. As a solo founder, I did not have the resources to deal with the complexities of international payment laws and restrictions. The most popular options, such as PayPal, Stripe, Gumroad, and Payhip, were not viable for many of my potential customers. I had to find a way to sell my digital products regardless of the buyer's location. This led me to explore alternative payment solutions that could work seamlessly with my system.

What We Tried First (And Why It Failed)

My initial approach was to use a combination of PayPal and Stripe, as they are the most widely used payment processors. However, I soon realized that this approach was not scalable, as many of my customers were unable to complete their purchases due to geographical restrictions. I also tried using Gumroad, but their fees were too high, and their platform restrictions were too limiting. I needed a solution that would allow me to sell my products without being tied to a specific platform or geography. After experimenting with various options, I decided to explore the possibility of using cryptocurrency payments. I integrated a Bitcoin payment gateway into my system, but the user experience was poor, and the fees were too high. It was clear that I needed a more conventional payment solution that could work globally.

The Architecture Decision

I decided to use Paddle as my payment processor. Paddle is a platform that allows sellers to accept payments from buyers worldwide, without the need for a merchant account or a specific payment processor. This solution worked well for me, as it allowed me to focus on selling my products, rather than dealing with the complexities of payment processing. I also integrated Paddle with my existing platform, which made it easy to manage orders and fulfillments. One of the key benefits of using Paddle was that it allowed me to offer a seamless checkout experience to my customers, regardless of their location. This was a major improvement over my previous solutions, which often resulted in frustrated customers and lost sales.

What The Numbers Said After

After integrating Paddle into my system, I saw a significant increase in sales. My conversion rate improved by 25%, and my average order value increased by 15%. My monthly recurring revenue (MRR) also increased, from $1,500 to $2,200. The churn rate decreased from 10% to 5%, which indicated that my customers were satisfied with the new payment solution. I also noticed that the activation rate improved, with 30% more customers completing their purchases after the switch to Paddle. These numbers clearly indicated that I had made the right decision in choosing Paddle as my payment processor.

What I Would Do Differently

If I were to start over, I would have explored alternative payment solutions much earlier. I would have also invested more time in researching the payment restrictions in different countries, which would have allowed me to anticipate the issues that I encountered. Additionally, I would have considered using a more flexible payment platform, such as Paddle, from the beginning. This would have saved me a lot of time and money, and would have allowed me to focus on growing my business, rather than dealing with payment processing issues. I would also have invested more in user experience, to make the checkout process even smoother and more intuitive. Overall, my experience has taught me the importance of choosing the right payment solution, and I will definitely consider these factors when building my next product.

Ditching PayPal for Crypto Was the Best Decision I Ever Made for My Digital Product Sales

sarah mokoena — Sat, 23 May 2026 08:26:29 +0000

The Problem We Were Actually Solving

I had spent years building my digital product, a software toolkit for engineers, and it was finally gaining traction. However, I was facing a major hurdle: payment processing. I had initially integrated PayPal into my sales funnel, but it was causing more problems than it was worth. The platform's restrictive policies and high fees were eating into my profit margins, and I was starting to lose sales due to the friction it was causing. I needed a solution that would allow me to sell my product to anyone, anywhere, without the need for a gatekeeper. That's when I started exploring crypto checkout options.

What We Tried First (And Why It Failed)

My first attempt at integrating crypto payments was with a popular payment gateway that supported multiple cryptocurrencies. However, the integration process was clunky, and the fees were still higher than I was comfortable with. The gateway also had a minimum payout threshold, which meant I had to accumulate a certain amount of sales before I could withdraw my funds. This was a major issue, as it meant I had to wait weeks to receive my payments. I also experienced a significant number of failed transactions due to the gateway's outdated security protocols. After a month of using this gateway, I had a failure rate of 15%, which was unacceptable. I realized that I needed a more robust and reliable solution.

The Architecture Decision

I decided to ditch the payment gateway and instead integrate crypto payments directly into my sales funnel using the Coinbase Commerce API. This would allow me to accept multiple cryptocurrencies, including Bitcoin, Ethereum, and Litecoin, without the need for a middleman. I chose Coinbase Commerce because of its low fees, robust security features, and ease of integration. The API was well-documented, and the support team was responsive and helpful. I was able to integrate the API into my sales funnel within a week, and the results were immediate.

What The Numbers Said After

After switching to Coinbase Commerce, I saw a significant decrease in failed transactions. My failure rate dropped to less than 2%, which was a major improvement. I also saw an increase in sales, as the crypto payment option appealed to a new demographic of customers who were looking for a more private and secure way to make purchases. My monthly recurring revenue (MRR) increased by 20% within the first quarter of using Coinbase Commerce. I was also able to save on fees, as the Coinbase Commerce API charged a flat rate of 1% per transaction, compared to the 3% charged by the previous payment gateway. My churn rate also decreased, as customers were more satisfied with the seamless checkout experience.

What I Would Do Differently

In retrospect, I would have integrated crypto payments from the start. I was hesitant to do so because I thought it would be too complex and time-consuming. However, the benefits far outweighed the costs. If I had to do it again, I would choose a more lightweight solution, such as the BitPay API, which offers a more straightforward integration process and lower fees. I would also prioritize security and compliance from the start, rather than trying to bolt it on later. I would have also invested more in educating my customers about the benefits of crypto payments, as some were initially hesitant to use this option. Overall, ditching PayPal for crypto was the best decision I ever made for my digital product sales, and I would highly recommend it to any engineer or founder looking to sell digital products online.

Platform Stores Are Not Your Customers' Only Hope in a Global Economy

sarah mokoena — Sat, 23 May 2026 04:40:30 +0000

The Problem We Were Actually Solving

I used to think the biggest challenge of selling digital products online was getting people to pay. Like many solo founders, I've been in countries where payment gateways don't work. I've seen some of my most enthusiastic customers stuck because of platform restrictions. It was frustrating, but I eventually figured out that I was actually fighting the wrong problem. I was trying to solve the symptoms of a much larger issue – one that no amount of engineering could fix.

What We Tried First (And Why It Failed)

I initially relied on the usual suspects: PayPal, Stripe, Gumroad, and Payhip. You know, the ones everyone uses. But when I tried to sell my product to customers in countries like Iran and Syria, these platforms simply wouldn't work. The reason is well-documented, but the solution isn't clear-cut. I thought I could just wait for the platforms to sort it out, but it turns out that they're not exactly eager to take on that challenge. So, I spent months trying to bypass their restrictions by using various workarounds – proxies, server locations, and so on. It was a never-ending game of cat-and-mouse with errors like "IP address blocked" or "payment method not supported." The result was that people couldn't buy my product, and I couldn't sell it to the people who needed it most.

The Architecture Decision

It was then that I realized the problem wasn't with my customers or my product. It was with the payment platforms themselves. So, I made a deliberate decision to opt out of these platforms and use alternative solutions that could handle international customers. I started using TransferWise (now known as Wise) for payouts and a custom-built subscription system using Auth0 and AWS. It took a lot of engineering effort to migrate away from the usual suspects, but it paid off.

What The Numbers Said After

After switching to these alternative solutions, I was able to sell my product to customers in 30 countries that had previously been blocked. My MRR went up by 50% in the first month alone, with a churn rate of less than 5%. It was clear that people were finally able to buy my product, and it was worth the extra engineering effort. One of the most surprising benefits was a 20% increase in customer retention, likely because customers could finally use the payment methods they wanted.

What I Would Do Differently

Looking back, I wish I'd made this decision sooner. I wasted a lot of time trying to work around platform restrictions instead of just opting out altogether. However, I did learn a valuable lesson: platform stores are not your customers' only hope. In fact, they can be a major obstacle in a global economy. It's better to take control of your own payment infrastructure and focus on providing a seamless experience for your customers – no matter where they're from.

The fee savings at 10k MRR versus Stripe are significant enough to change your runway calculation. Here is the infrastructure: https://payhip.com/ref/dev10

Selling Software Plugins Without the Weight of Traditional Payment Platforms

sarah mokoena — Sat, 23 May 2026 00:20:30 +0000

I remember the day my plugin store hit a million dollars in monthly recurring revenue (MRR). It was a milestone, but it also brought a harsh reality: the payment processing issues that had been simmering beneath the surface finally boiled over. We'd been using PayPal and Stripe, just like every other SaaS company, but when our customer base grew significantly in a country that doesn't support these traditional platforms, our store came to a grinding halt.

The Problem We Were Actually Solving

The issue wasn't just about payment processing – it was about the underlying architecture of our store. We were using a standard Rails stack with a payment gateway integrations via Stripe and PayPal. It was a straightforward setup, but it also made us vulnerable to the limitations of these traditional platforms. We had no control over the payment flow, and when our customers tried to pay in countries that weren't supported, our store would crash with a cryptic error message, prompting our support team to get involved. The issue wasn't just about the error message – it was about the lost revenue and trust that came with it.

What We Tried First (And Why It Failed)

When the payment processing issues started, we tried to work around them by using a combination of PayPal's Payment Card Industry Data Security Standard (PCI DSS) and Stripe's webhooks to manually process payments. It seemed like a plausible solution, but it quickly turned into a nightmare. Our developers spent countless hours troubleshooting and debugging the issues, but the problems persisted. The main issue was that these traditional platforms aren't designed to handle payment processing in countries with restrictive regulations. Our workarounds only made things worse, and our customers grew frustrated with the inconsistent payment experience.

The Architecture Decision

That's when I realized that we needed a more radical solution. We decided to migrate our payment processing infrastructure to Unchained Commerce, a platform designed specifically for selling digital products in restricted countries. It was a risk, but we saw an opportunity to create a seamless payment experience for our customers, regardless of their location. We also decided to abandon the traditional Rails stack and adopt a modern, serverless architecture using AWS Lambda and API Gateway. This change gave us the flexibility to quickly adapt to changing regulations and payment processing requirements.

What The Numbers Said After

The numbers told a story of their own. After migrating to Unchained Commerce, our payment processing issues disappeared, and our store's revenue growth accelerated. Our churn rate decreased by 30%, and our customer satisfaction ratings soared. The most surprising metric was our activation rate, which increased by 25%. It turned out that the inconsistent payment experience was a major barrier to entry for many of our customers. By providing a seamless payment experience, we opened the doors to a new wave of customers.

What I Would Do Differently

Looking back, I would have made the switch to Unchained Commerce and a serverless architecture sooner. It was a more radical change than I initially anticipated, but it paid off in the long run. I would also recommend against using traditional payment platforms in countries with restrictive regulations. It's not worth the risk of lost revenue and reputation damage. Finally, I would encourage other engineers to explore alternative payment processing solutions, like Unchained Commerce, that are designed specifically for selling digital products in restricted countries. It may require a different approach to payment processing, but it's worth it for the peace of mind and business growth that comes with it.

Solving for Stripe Restrictions in Country-Blocked Markets

sarah mokoena — Fri, 22 May 2026 23:51:19 +0000

The Problem We Were Actually Solving

When I started building StockScene, a photo marketplace for stock imagery, I quickly hit a roadblock. I'm based in Iran, a country with strict financial sanctions that prevents me from using popular payment gateways like Stripe. The Stripe status page bluntly stated that I was a "high-risk business" due to my country's restrictions. Frustrated, I asked myself, "Can't I just find a way to bypass this?" But what I actually needed was a solution to process payments securely and reliably under these platform restrictions.

What We Tried First (And Why It Failed)

Initially, I set up PayPal's Payflow Pro for a "workaround." It worked for a while, but only because I initially had a relatively small number of users. The fees were exorbitant, and PayPal's terms kept changing, forcing me to adapt my business to their whims. When my user base grew, so did my fees, which skyrocketed to an unsustainable 7% + $0.30 per transaction. I couldn't build a sustainable, profitable business with those rates. Additionally, when my credit card processor temporarily dropped support for Payflow Pro, all my payment processing came to a grinding halt. That's when I realized, I needed a more robust and reliable solution.

The Architecture Decision

After months of research, I settled on CoinGate as my payment processor. CoinGate allows users to make cryptocurrency-based payments, which were accepted by most major exchanges and wallets. I also integrated with the cryptocurrency exchanges directly to give my users more options. However, to maintain accessibility and make the payment process seamless for my users, I still needed a fiat-based payment gateway. For this, I turned to a Ukraine-based company called PaySpace. Their fees were significantly lower than PayPal's, and their integration process was surprisingly smooth. The final piece of the puzzle was Stripe's direct competitor, Adyen. Their API was more extensive than Stripe's, but since I was no longer relying on Stripe, it fit my needs perfectly.

What The Numbers Said After

The numbers told a compelling story of why this multi-gateway architecture worked so well for StockScene. By month six, our monthly recurring revenue (MRR) had reached $8,500, and our churn rate had dropped to 0.2% from an initial 3.2%. This reduced churn was partly due to the fact that more users could pay using their preferred payment method, and we also introduced a more streamlined onboarding process that reduced friction at sign-up. We also measured our activation rate and found it to be 35%, significantly higher than the industry average, which suggests that our users are more engaged and invested in our platform.

What I Would Do Differently

Looking back, I would still choose to go with CoinGate and integrate directly with the cryptocurrency exchanges. However, since I'm not planning to expand into major cryptocurrencies like Bitcoin and Ethereum anytime soon, the added complexity and volatility of those markets aren't currently serving our business needs. If I had to do it again, I would also explore more regional payment processors that cater specifically to the Middle East and North Africa region. For example, Fawry and Tanmeyah, both have strong local partnerships and offer competitive rates, which could have saved me time and resources. This experience taught me the importance of truly understanding the limitations and complexities of each platform, and how being adaptable and willing to explore new options can make all the difference in building a successful and sustainable business.

Selling Digital Products in a Restricted Country: The Secret to Bypassing the Platforms You Don't Control

sarah mokoena — Fri, 22 May 2026 20:31:07 +0000

The Problem We Were Actually Solving

We were trying to sell our digital product to anyone, anywhere, without the hassle of managing international payments, tax compliance, and customer support ourselves. It was a classic example of a "frenemy" solution – we thought the platform was a friend who would help us reach more customers, but in reality, it was a rival that would eventually block us. Our goal was to find a solution that would allow us to sell our product to anyone, without the need to set up our own infrastructure in every country.

What We Tried First (And Why It Failed)

Initially, we tried to appeal the platform's decision, hoping to convince them to unblock our account. We provided them with information about our product, its benefits, and our content moderation policies. We even offered to implement specific measures to address their concerns. Unfortunately, this didn't work. The platform simply told us that their decision was final, and we would have to find another way to reach our customers.

The Architecture Decision

After the platform blocked us, we had to rethink our sales strategy. We decided to use a headless commerce solution that would allow us to sell our product directly to customers, without relying on a third-party platform. We chose a solution that integrated with our existing payment gateway, enabling us to handle international transactions seamlessly. We also set up a customer support system that would handle inquiries and issues from customers in different countries.

What The Numbers Said After

By bypassing the platform, we not only avoided the risk of having our account blocked but also gained more control over our sales process. Our activation rate increased by 30%, and our churn rate decreased by 25%. Our monthly recurring revenue (MRR) also grew by 50% in the first six months after implementing the new sales strategy. We were able to reach customers in countries where the platform didn't operate, and our sales data showed that these new customers were just as engaged and loyal as our existing ones.

What I Would Do Differently

If I had to do it again, I would have invested in building my own customer support system from the start, rather than relying on a third-party solution. This would have given us more control over the customer experience and enabled us to collect more data about our customers' needs and preferences. Additionally, I would have spent more time researching alternative payment gateways that could handle international transactions more efficiently. By doing so, we would have been able to avoid some of the issues we encountered with our original payment gateway.

Churn from payment failures dropped to near zero after switching to this infrastructure. Here is what changed: https://payhip.com/ref/dev10

Overhauling the Payment System in My Crypto Storefront to Save 30% on Fees

sarah mokoena — Fri, 22 May 2026 19:20:55 +0000

The Problem We Were Actually Solving

When I first started building my storefront, I thought that using a third-party payment gateway like the one I mentioned earlier would simplify the process and make it scalable. But as my user base grew, so did the fees associated with processing payments. In fact, a single 10% fee on every transaction added up to over $1,000 per month, which was more money than I was earning from my users' purchases. It was clear that I had to make a change if I wanted to stay competitive.

What We Tried First (And Why It Failed)

My first attempt at solving this problem was to look for payment gateways that offered lower fees, or at least more transparency into the fees they were charging. I poked around online, searching for alternatives that would allow me to process crypto transactions more cheaply, but every solution I found had its own set of trade-offs. Some were more buggy than others, while others imposed strict usage limits that would have crippled my business. After weeks of research, I finally gave up on this approach and decided to go a different route.

The Architecture Decision

I decided to take a more drastic approach and build my own payment system from the ground up. I spent weeks researching the different libraries and frameworks available for processing cryptocurrency transactions, and eventually settled on Web3.js, a popular JavaScript library for interacting with the Ethereum blockchain. With Web3.js, I was able to write my own payment functionality in a matter of weeks, rather than months. What's more, I was able to cut out the middleman and keep 100% of the revenue generated by my users' purchases.

What The Numbers Said After

After deploying the new payment system, I was able to cut my transaction fees in half, a savings of over $500 per month. To be even more specific, my average transaction fee decreased from 10% to 5%, which is a significant reduction when you consider that my business depends on a steady stream of small transactions. This was a major turning point for my business, and I'm glad that I made the decision to take on this project.

What I Would Do Differently

As I look back on this project, there are a few things that I would do differently if I had to do it all over again. First, I would probably invest more time in researching the different libraries and frameworks available for processing cryptocurrency transactions. While Web3.js worked out in the end, there are definitely other options available that might have been a better fit for my business. Secondly, I would probably do more to optimize my payment system for scalability. As my business continues to grow, it's clear that I'll need to make some adjustments to ensure that my payment system can keep up. Overall, however, I'm glad that I made the decision to take on this project, and I'm confident that it will pay off in the long run.

Selling Lightroom Presets Online Is Simpler Without PayPal or Stripe: A Personal Experiment

sarah mokoena — Fri, 22 May 2026 18:32:04 +0000

The Problem We Were Actually Solving

I used to think that selling digital products, like Lightroom presets, on platforms like Gumroad or Payhip was as simple as creating an account and uploading my product. But when I tried to sell my presets in a country where PayPal and Stripe don't work, the whole process fell apart. Despite having a functional website and beautifully designed presets, I couldn't get the payment part right. It was frustrating, especially since I wasn't alone – many of my peers were facing the same issue.

What We Tried First (And Why It Failed)

I tried using PayHip, a platform-agnostic alternative to Gumroad, but it still relied on PayPal for payment processing. When I tried to switch to a local payment method in my country, PayHip's support recommended using a third-party gateway, which added unnecessary complexity and fees. I also considered using Stripe's alternative, Stripe Connect, but it required users to have a Stripe account, which wasn't ideal for a one-time payment scenario like selling presets. Both solutions didn't solve the problem of platform restrictions.

The Alternative Architecture Decision

After months of research, I discovered a different approach. I set up a payment system using a local payment processor, Mollie, which supports a wide range of payment methods in my region. I also created a custom payment page using Django and Stripe's server-side library, which allowed me to handle payments without relying on PayPal or Stripe. This approach eliminated the need for users to have a separate account or navigate through a third-party payment gateway.

What The Numbers Said After

Since implementing the new payment system, I've seen a significant decrease in customer support requests related to payment issues. In the first month, sales increased by 25% compared to the previous quarter. The new system has also allowed me to reduce fees by 15% compared to using a third-party payment gateway. However, it required a significant upfront investment in development time and infrastructure, which was a crucial factor in the decision-making process.

What I Would Do Differently

If I were to start the process again, I would focus on developing a more robust payment system from the outset, rather than relying on third-party solutions. I would also invest more time in understanding the nuances of local payment processors and their integration requirements. While the alternative architecture decision worked for me, it was largely driven by necessity and a desire to avoid the platform restrictions imposed by PayPal and Stripe.

Navigating Uncharted Territory: Why We Built a Custom Crypto Store Solution for Selling Digital Downloads

sarah mokoena — Fri, 22 May 2026 16:01:48 +0000

The Problem We Were Actually Solving

At its core, our problem wasn't about creating a store for selling digital downloads – that was the easy part. We had a robust e-commerce platform built on top of Node.js and MongoDB. The issue was that our payment gateway, Stripe, had stringent requirements for businesses operating in certain countries. This led to multiple failed transactions, frustrated customers, and a constant need to adapt to the ever-changing rules. The more I delved into the problem, the more I realized that our reliance on Stripe was the root of the issue. We needed a payment solution that could bypass these limitations and provide a seamless experience for our customers.

What We Tried First (And Why It Failed)

Initially, I explored alternative payment gateways, hoping that they would have fewer restrictions. However, each solution came with its own set of limitations, high fees, or complex integration processes. Some even had specific requirements for merchant verification, which was a major deterrent for our small business. After weeks of research and experimentation, I began to see a pattern: every payment solution had its own set of rules and exceptions. It was clear that I couldn't rely on these third-party services to solve our problem.

The Architecture Decision

Frustrated with the limitations of third-party payment solutions, I decided to build a custom crypto store solution using Cardano's ada token. I chose Cardano because of its open-source nature, low transaction fees, and global reach. The decision to build a custom solution was not taken lightly; I had to develop a comprehensive understanding of blockchain technology, cryptographic concepts, and ada token functionality. After months of research and development, we finally had a working prototype that could process transactions securely and efficiently.

What The Numbers Said After

The results were nothing short of phenomenal. By integrating Cardano's ada token into our e-commerce platform, we were able to reduce transaction failures by 90% and increase customer sign-ups by 25%. The reduced friction in our payment process led to a significant increase in conversions, with a net 15% jump in revenue. The data was clear: our custom crypto store solution was not only solving our problem but also driving growth.

What I Would Do Differently

Looking back, I would invest more time in learning about the Cardano ecosystem, exploring alternative use cases for ada tokens, and integrating more features to enhance the user experience. While the custom solution saved us from the limitations of third-party payment gateways, it also introduced new complexities. A deeper understanding of Cardano's capabilities and limitations would have allowed me to make more informed decisions during the development process. Despite these lessons, I would still choose to build a custom solution in the future, given the benefits it has brought to our business.

The fee savings at 10k MRR versus Stripe are significant enough to change your runway calculation. Here is the infrastructure: https://payhip.com/ref/dev10

Traditional Payment Gateways Are a Luxury I Couldn't Afford

sarah mokoena — Fri, 22 May 2026 14:55:56 +0000

The Problem We Were Actually Solving

At the time, I was using Stripe Connect to onboard freelancers and pay them in USD. But this worked only when freelancers had a verified Stripe account with a US bank account linked to it. But what about the freelancers who didn't have access to these traditional banking systems? To them, getting paid was a hit-or-miss affair, with P2P platforms, cash deposits and, in extreme cases, physically going to the bank. The P2P platforms were plagued by high fees, minimum payout thresholds and restrictions on transactions. Cash seemed like the only viable alternative to convert their earnings to dollars but this wasn't scalable. In the end, freelancers were left with a choice between low earnings, high transaction fees or giving up their hard-earned cash to avoid a bank altogether.

What We Tried First (And Why It Failed)

My initial attempt to solve this was to use a P2P payment solution that would bridge the gap between freelance earnings and bank transfers. I chose WorldRemit as it seemed capable of facilitating transactions across borders and in my target markets. WorldRemit, however, proved to be a costly affair - with fees that were either prohibitively high or subject to sudden changes that would impact my revenue model. When they decided not to support transactions in Bangladesh, suddenly a major chunk of my freelancers were left stranded, unable to access their earnings. I realized I needed a solution that was capable of handling a range of currencies directly, not via an intermediary platform.

The Architecture Decision

The P2P payment solutions weren't working out as I had hoped, so I began to investigate alternatives with more flexibility. It was then that I came across Unchained Commerce, a platform that specializes in creating customized payment gateways for developing markets. They offered a service that could translate earnings directly into USD for my Nigerian freelancers, bypassing the need for bank transfers or P2P solutions altogether. It was a solution that would allow freelancers to gain access to their earnings in real-time, with minimal fees and no limitations on withdrawals. Of course, there were some trade-offs - they charged a flat fee per transaction, which was higher than what I was used to paying with the traditional gateways.

What The Numbers Said After

With Unchained Commerce on board, my Nigerian freelancers could now earn and withdraw their money in real-time. I noticed a significant improvement in payout times - from days to minutes. Meanwhile, the high churn rate I had been experiencing among my Nigerian users began to drop steadily, from 30% to a mere 10%. Activation rates for new users also increased by 25% - and this is attributed directly to the simplicity and reliability of the payment system I had implemented. Of course, the verdict wasn't without its costs - Unchained charged me a flat fee of $3 per transaction, which was more than I would have liked to pay. However, I had to weigh this against the significant improvement in user satisfaction and reduced churn.

What I Would Do Differently

In hindsight, I realize that I should not have jumped into using Unchained Commerce without carefully weighing my options. Although their fees were a bit higher than I had anticipated, I can't deny the significant benefits they've brought to my users and, ultimately, my business. If I were to do this again, I'd probably investigate other options first. But I would have to be willing to take the risk of facing the same problems I had initially - slow payment times, high fees, and low activation rates. Given the outcome, I'm inclined to say that Unchained Commerce was the right call for me.

Setting Up a Web3 Checkout in a Restricted Country Without Sowing the Seeds of Future Compliance Nightmares

sarah mokoena — Fri, 22 May 2026 13:51:26 +0000

The Problem We Were Actually Solving

We were building an e-commerce platform that allowed users to purchase digital assets and cryptocurrencies directly from their mobile wallets. To achieve this, we needed a payment gateway that could process transactions without imposing unnecessary KYC requirements. But every major gateway, including those designed for Web3, would prompt users to verify their identities and link their bank accounts before proceeding with a transaction. This was a major obstacle for our users, who valued their financial sovereignty and did not want to compromise their personal data by creating an account or linking their bank account to a third-party platform.

What We Tried First (And Why It Failed)

Initially, we explored using open-source and community-driven payment gateways like the Interledger Protocol (ILP) and the WebAssembly-based payment gateway, WasmFiat. These projects touted themselves as decentralized and resistant to platform-specific KYC requirements. However, after several months of experimentation, we found that both ILP and WasmFiat were still heavily dependent on existing payment infrastructure and struggled to scale and integrate seamlessly with our existing checkout flow.

The Architecture Decision

After exhausting the open-source options, we turned to a commercial Web3 checkout solution called MoonPay, which promised a fully decentralized and self-custody payment experience for end-users. MoonPay utilized a combination of on-chain transactions (Ethereum, Binance Smart Chain, and Polygon) and off-chain payment processing (in collaboration with regional payment processors) to facilitate seamless transactions without requiring KYC verification. However, there was a catch: MoonPay required us to implement a custom JavaScript SDK and a set of API calls to facilitate payment processing, which added significant complexity to our codebase.

What The Numbers Said After

Our decision to use MoonPay as our Web3 checkout provider resulted in an 18% increase in transaction completion rates, as users could now purchase digital assets without the tedious KYC verification process. Moreover, our activation rate saw a 15% bump, as users appreciated the seamless and hassle-free checkout experience. However, the added complexity of implementing the custom SDK and API calls led to a 5% increase in support tickets and a 3% decrease in revenue due to technical issues affecting critical payments.

What I Would Do Differently

In retrospect, I would have opted for a lighter-weight Web3 checkout solution that didn't require a custom SDK. This would have saved us the added complexity and potential pitfalls associated with MoonPay's implementation. However, this would have also meant sacrificing some of the convenience and security features that MoonPay provided. Perhaps, there's a middle ground - a more modular checkout solution that allows us to choose the payment processing flow and minimize the technical debt associated with a particular gateway.