Philip Pages, founder of Redux Payments, explains why moving off Apple's in-app purchases quietly strips away a retention machine most founders never knew they had, how failed payments actually work, and when payment orchestration is worth the extra complexity.
Philip has looked inside hundreds of app payment accounts, and most of them are leaving real money on the table. He walks through the difference between a customer who wants to churn and a card that simply had no funds that morning; why recovered subscribers stick around for another three to six billing cycles; and the single setting that quietly blows up Stripe accounts. Jacob and Philip also get tactical on the app-to-web paywall pattern that converts, the retry schedule that recovers cards without triggering the card networks, and a meditation app that got back six figures by changing nothing but the timing of its retries.
What you'll learn
• Why Apple's in-app purchase system silently recovers failed payments, and exactly what you give up when you leave it
• Why most failed payments have nothing to do with a customer wanting to cancel
• How recovered subscribers behave once you win them back (they stay another three to six billing cycles)
• Why the "30% down to 5%" margin pitch for web billing is misleading
• How to tell whether your app is even ready to test web billing
• Why older, Facebook-native audiences convert better on web-to-app flows than younger ones
• How to set up web payments without blowing up your Stripe or Paddle account
• What chargebacks, early fraud warnings, and approval rates actually do to your account health
• How merchant-of-record providers take ownership of your transactions, and what that costs you later
• What payment orchestration is, and the revenue point where it starts paying for itself
• How one meditation app recovered over $150K by fixing retry timing by locale
• How long you should really retry a failed card, and why spamming it backfires
• The compliant two-button app-to-web paywall pattern that didn't exist a year ago
Key takeaways
• Apple runs a retention machine you never see. Behind the scenes, Apple retries cards near paydays, fixes bank issues, and serves in-app prompts for up to 60 days. It feels like magic, but it is a system. Move to web and that system is now your job.
• Most failed payments are not people trying to leave. Insufficient funds at one moment in time and random bank rejections make up the bulk of failures. Treating every failure as a lost cause writes off customers who already paid you for months.
• The margin math is messier than the pitch. Providers love to say you'll save 25 to 27 percent. Philip says heavily discount that. Even so, saving 15 percent and reinvesting it in growth can compound fast, so the channel is still worth testing.
• Don't touch web billing before product-market fit. Under a million in ARR with no PMF, the only job is finding PMF. Optimizing payments early is a distraction. Post-PMF, commit real budget or don't bother.
• Cancel your subscriptions. The number one way apps wreck their Stripe account is leaving failed subscriptions open. They stack, they collect chargebacks, and one subscription that should have had a single chargeback ends up with seven.
• Retry timing beats retry volume. One app had 64 percent of failures come from insufficient funds. Retrying by local payday instead of at random recovered over $150K. Brute-forcing the card just gets you flagged by the networks.
• Orchestration is where big brands quietly win. Netflix, Spotify, and other large subscription companies route payments across multiple processors to lift approval rates. Most smaller apps have never even considered it.
• The app-to-web playbook is new, and it works. Two CTA buttons, a rebuilt mini-onboarding before the paywall, and Apple Pay on by default. Philip's word for the pattern Jacob describes: gold. It did not exist a year ago.
Links & resources
• Philip Pages on LinkedIn: https://www.linkedin.com/in/philip-pages-a881b5139/
• Redux Payments: https://www.reduxpayments.com/
0:00 Intro
02:00 Intro and Philip's first company (peaked near $3.5M ARR, then shrank)
04:11 Apple's hidden failed-payment machine, and what you lose moving to web
07:00 What a failed payment actually is, and why most aren't churn
11:05 The real margin math behind leaving the App Store
12:16 Why web billing is hitting critical mass now
17:20 Matching the right user to the right payment method
21:33 Getting started: providers, merchant of record, subscription management
25:47 How to not blow up your Stripe account
28:43 Chargeback alerts and fighting chargebacks
30:40 Merchant of record: owning the transaction, and getting out
34:27 Payment orchestration and cascading across processors
39:06 When web billing is a mistake (pre product-market fit)
44:47 App-to-web compliance and the two-button paywall playbook
52:32 A failed-payment recovery teardown (the six-figure meditation app)
59:02 How long to retry a failed card
01:03:00 The scariest account story, and what Redux Payments does
Philip has looked inside hundreds of app payment accounts, and most of them are leaving real money on the table. He walks through the difference between a customer who wants to churn and a card that simply had no funds that morning; why recovered subscribers stick around for another three to six billing cycles; and the single setting that quietly blows up Stripe accounts. Jacob and Philip also get tactical on the app-to-web paywall pattern that converts, the retry schedule that recovers cards without triggering the card networks, and a meditation app that got back six figures by changing nothing but the timing of its retries.
What you'll learn
• Why Apple's in-app purchase system silently recovers failed payments, and exactly what you give up when you leave it
• Why most failed payments have nothing to do with a customer wanting to cancel
• How recovered subscribers behave once you win them back (they stay another three to six billing cycles)
• Why the "30% down to 5%" margin pitch for web billing is misleading
• How to tell whether your app is even ready to test web billing
• Why older, Facebook-native audiences convert better on web-to-app flows than younger ones
• How to set up web payments without blowing up your Stripe or Paddle account
• What chargebacks, early fraud warnings, and approval rates actually do to your account health
• How merchant-of-record providers take ownership of your transactions, and what that costs you later
• What payment orchestration is, and the revenue point where it starts paying for itself
• How one meditation app recovered over $150K by fixing retry timing by locale
• How long you should really retry a failed card, and why spamming it backfires
• The compliant two-button app-to-web paywall pattern that didn't exist a year ago
Key takeaways
• Apple runs a retention machine you never see. Behind the scenes, Apple retries cards near paydays, fixes bank issues, and serves in-app prompts for up to 60 days. It feels like magic, but it is a system. Move to web and that system is now your job.
• Most failed payments are not people trying to leave. Insufficient funds at one moment in time and random bank rejections make up the bulk of failures. Treating every failure as a lost cause writes off customers who already paid you for months.
• The margin math is messier than the pitch. Providers love to say you'll save 25 to 27 percent. Philip says heavily discount that. Even so, saving 15 percent and reinvesting it in growth can compound fast, so the channel is still worth testing.
• Don't touch web billing before product-market fit. Under a million in ARR with no PMF, the only job is finding PMF. Optimizing payments early is a distraction. Post-PMF, commit real budget or don't bother.
• Cancel your subscriptions. The number one way apps wreck their Stripe account is leaving failed subscriptions open. They stack, they collect chargebacks, and one subscription that should have had a single chargeback ends up with seven.
• Retry timing beats retry volume. One app had 64 percent of failures come from insufficient funds. Retrying by local payday instead of at random recovered over $150K. Brute-forcing the card just gets you flagged by the networks.
• Orchestration is where big brands quietly win. Netflix, Spotify, and other large subscription companies route payments across multiple processors to lift approval rates. Most smaller apps have never even considered it.
• The app-to-web playbook is new, and it works. Two CTA buttons, a rebuilt mini-onboarding before the paywall, and Apple Pay on by default. Philip's word for the pattern Jacob describes: gold. It did not exist a year ago.
Links & resources
• Philip Pages on LinkedIn: https://www.linkedin.com/in/philip-pages-a881b5139/
• Redux Payments: https://www.reduxpayments.com/
0:00 Intro
02:00 Intro and Philip's first company (peaked near $3.5M ARR, then shrank)
04:11 Apple's hidden failed-payment machine, and what you lose moving to web
07:00 What a failed payment actually is, and why most aren't churn
11:05 The real margin math behind leaving the App Store
12:16 Why web billing is hitting critical mass now
17:20 Matching the right user to the right payment method
21:33 Getting started: providers, merchant of record, subscription management
25:47 How to not blow up your Stripe account
28:43 Chargeback alerts and fighting chargebacks
30:40 Merchant of record: owning the transaction, and getting out
34:27 Payment orchestration and cascading across processors
39:06 When web billing is a mistake (pre product-market fit)
44:47 App-to-web compliance and the two-button paywall playbook
52:32 A failed-payment recovery teardown (the six-figure meditation app)
59:02 How long to retry a failed card
01:03:00 The scariest account story, and what Redux Payments does