$2.3M in monthly payments, 18% revenue recovered: A wellbeing app story

Project summary

• The client is a wellbeing app monetizing through FunnelFox web funnels, with Stripe as its sole payment provider.
• Before scaling, the team needed a payment setup that could support growth.
• They connected FunnelFox Billing, an end-to-end web monetization infrastructure with multiple PSPs, payment fallback, retries, and smart routing.
• By pairing their own growth expertise with the new payment setup, the team scaled payment volume 8x in six months and recovered 18% of revenue.

About the client

The client is a web-based wellbeing app that helps people understand themselves and feel more balanced, adapting to each user as it goes.

Wellbeing is a crowded space — dozens of apps chasing the same audience with the same promises.

But in under a year, our client took it from first transactions to millions of dollars a month. That takes two things: building a great product people are genuinely willing to pay for, and knowing web monetization cold.

Challenge: Big growth plans, a limited payment setup

From the beginning, the team monetized entirely through web funnels built on FunnelFox. As the product gained traction, the team planned to expand into new markets.

Payments, at first, ran through a single provider: Stripe. For a company operating in one market at modest volume, that’s rarely a problem. But scaling internationally comes with its own set of complications:

• Card network dominance shifts from country to country — Visa and Mastercard lead in some places, while others lean on local schemes.
• Payment habits shift too: cards dominate in some regions, Apple Pay and Google Pay in others, and local wallets somewhere else entirely.
• And banks handle authorization differently market to market — regulatory requirements like 3DS/SCA in Europe, different levels of fraud sensitivity, different risk tolerances.

One provider can’t optimize for all of that at once, and ignoring these differences can lead to lost revenue.

The team didn’t wait for scale to expose the gaps, so before pushing further into new markets, they decided to get their payment setup in order first.

Even with both resources and expertise, getting the web monetization infrastructure right takes time and effort that most growing teams don’t have to spare. So instead of doing it all themselves, the client looked for a solution that could cover everything they needed and found it in FunnelFox Billing.

Solution: End-to-end web monetization infrastructure

The first move was adding a second provider, Airwallex. With two providers in place, payments got a fallback layer. When a charge fails on one provider, the system doesn’t wait — it immediately attempts the same payment through the other. That runs first, before anything else.

Only if both providers decline does retry logic take over. Instead of writing the payment off after one decline, the system keeps trying on a set schedule: a grace period starts right away, a full charge is attempted a few days later, and if that fails too, smaller partial charges follow over the next couple of weeks rather than giving up on the full amount at once. FunnelFox Billing runs this schedule by default, tuned to the subscription’s billing interval, though it can be adjusted to be more aggressive or more conservative. The team runs the default schedule and hasn’t needed to touch it.

Provider order also shifts by region. For some traffic, Stripe goes first with Airwallex as the fallback; for other segments, it’s reversed. Airwallex performs better with certain regional traffic, so routing those payments through it first improves approval rates and cuts down on the extra fees that come with processing across borders.

Checkout is localized across three currencies — USD, EUR, GBP — and around ten languages. The team added those languages one at a time, checking whether each one held up. A newly localized market often shows a fast jump in signups, but that early wave of conversions tends to fade fast, while the cost of supporting the language stays the same. So each addition gets weighed against what it takes to keep it running.

Results: Payment volume up 8x, 18% revenue recovered

The fallback and retry setup, combined with region-based routing, recovered 18% of revenue that would otherwise have been lost to failed payments. Some of that recovery is what a single Stripe setup would manage on its own through retries. Fallback is what a single provider can’t do: when a payment fails on one, it goes through on another.

Fallback works especially well on renewals: recovery rates run close to 31% on subscription renewals, compared to about 24% on first payments. Existing customers, already verified and already invested in the product, are simply easier to recover than a first-time buyer bouncing off a decline.

Localized checkout brought acceptance rates to roughly 83% for GBP, 78% for EUR, and 71% for USD.

The team grew payment volume nearly 8x over the past six months, bringing in $2.3M in June alone. That’s fast growth for a wellbeing app competing in one of the most crowded verticals in the space.

Key takeaway: Payments should support growth, not limit it

Payment infrastructure isn’t something you fix after it breaks — it’s something you build alongside growth, before the gaps get expensive.

For this team, that meant setting up fallback, smart routing, and localized checkout before scaling further into new markets, and it paid off: 18% of revenue that would otherwise have been lost, recovered instead.

The lesson holds for any subscription app expanding across borders. At scale, even a single percentage point of acceptance rate is real money, and by the time it shows up, it’s already cost you.

Got growth plans that your payment setup might not be ready for? See what FunnelFox Billing can do.