D2C Trend Report v3

Deep Dive on Two Key Uncertainties: App Store Fees & Implementation Timelines — March 14, 2026

Methodology: David Deutsch's criterion — only non-variable explanations that are hard to change without also changing the observed facts. 2–3 core explanations per section maximum.

FOCUS 1, Question 1: How Certain Is Web-Based D2C Being "Allowed and Not Expensive"?

The Regulatory Timeline — What Actually Happened

Sep 2021
Original Epic v. Apple ruling: Judge Gonzalez-Rogers orders Apple to allow external payment links (anti-steering injunction).
2022–2024
Apple's compliance: introduces 27% commission on external link purchases — designed to be more expensive than IAP (30% minus 3% payment processing). Almost zero developers opt in.
Apr 30, 2025
Judge finds Apple in willful contempt. Orders: zero commission on external links, no design restrictions. Apple must comply immediately.
May 1–2, 2025
Apple updates App Store Guidelines. Spotify submits and gets approved for external payment links within 24 hours. Zero Apple commission goes live.
Jun 26, 2025
EU: Apple overhauls DMA fee structure — 2% acquisition + 5–13% Store Services + 5% Core Technology Commission for external payment path. CTF sunset by Jan 2026.
Dec 11, 2025
Appeals court partially reverses: Apple CAN charge a "reasonable" fee on external link purchases — but 27% was "prohibitive" and contempt is upheld. Case remanded to determine the actual fee.
Mar 2026 (now)
District court proceedings to determine "reasonable fee" ongoing. Currently: zero commission is in effect while the fee is being determined.
Core Explanation #1: The direction is settled; the magnitude is not. The appeals court unanimously affirmed that (a) external links must be allowed, (b) 27% was contempt-worthy, and (c) some "reasonable" fee covering Apple's costs + IP value is permissible. The structural question — "Can Apple block web D2C?" — is answered: No. The remaining question is the fee level.

What Will the "Reasonable Fee" Be?

Scenario Likely Fee Range Rationale Probability
Bull case 0–5% Court interprets "costs" narrowly — Apple's actual infrastructure cost for enabling a link is near-zero. Epic/Sweeney celebrated ruling as "death of Apple Tax." ~30%
Base case 5–12% Court grants some IP value for iOS platform + App Store distribution. Aligns with EU DMA structure (5% CTC + some store services). Google's User Choice Billing charged ~4% less than standard. ~50%
Bear case 12–20% Court agrees Apple's IP value is substantial. Still materially below 30% but not the windfall developers hoped for. ~20%
Core Explanation #2: Even in the bear case, D2C saves money versus IAP. At 15% Apple fee + 3% Stripe = 18% total vs. 30% IAP = 12pp savings. At 5% + 3% = 8% total = 22pp savings. The margin improvement for Bumble is real across all scenarios — the question is whether it's 5pp or 15pp of gross margin improvement at scale.

US vs. EU: Two Different Regimes

🇺🇸 United States

Current state: Zero commission on external links (contempt order still in effect while "reasonable fee" is being determined).

Future state: Some reasonable fee TBD by district court. Could take 6–12 months to resolve.

Can Apple block web D2C? No. The injunction is permanent and upheld by the 9th Circuit.

🇪🇺 European Union

Current state: Under DMA, apps can use external payment and link out. Fee structure: ~10–20% total depending on path (5% CTC + Store Services + Acquisition fee).

Future state: Jan 2026 single business model transition. European Commission actively monitoring compliance.

Can Apple block web D2C? No. DMA Article 5(4) prohibits it. EC has enforcement powers with fines up to 10% of global revenue.

Remaining Risk Factors

Risk: Apple could make web D2C technically difficult. History shows Apple's instinct is malicious compliance — the 27% "link tax" proved this. Even post-ruling, Apple can restrict link prominence to "no more prominent than IAP buttons." This creates friction. However, the court specifically noted Apple made things "as hard to use as possible" which "flies in the face of the Injunction's spirit" — suggesting future bad-faith compliance will be punished.
Open question: Supreme Court? Apple has not sought cert and the Dec 2025 ruling partially went in Apple's favor (they CAN charge something). Neither side has strong incentive to escalate further. The structural framework is likely final.
VERDICT on Question 1: HIGH CERTAINTY (8/10) that web D2C is permanently allowed with meaningful savings. The only uncertainty is the fee magnitude. Even worst-case, developers save 10–15pp vs IAP. The regulatory/legal direction has been affirmed at every level. No pending challenge can reverse external link rights.

FOCUS 1, Question 2: How Long Does D2C Web Payment Integration Actually Take?

Real-World Migration Case Studies

Company When What They Did Timeline Outcome
Netflix Dec 2018 Stopped accepting new iOS IAP signups. Directed all new users to web. Already had web billing infrastructure from day one (Netflix was web-first). ~0 months (already had web billing). Took until Feb 2024 to fully cut off grandfathered IAP subscribers. No meaningful churn reported. Users already had Netflix accounts with web credentials.
Spotify May 2016 Stopped accepting new iOS IAP signups after only 2 years of offering it (Jun 2014–May 2016). Directed to web. ~0 months (Spotify was web-first). Cut off remaining IAP subscribers in Jul 2023. By May 2025, immediately added in-app external link post-ruling — took ~1 day to submit update.
Epic/Fortnite Aug 2020 Added direct payment option in-app (bypassing IAP). Already had web store and Epic Games Store ecommerce. Built direct payment in ~months (had ecommerce infra). Launched "Web Shops" for third-party devs Jun 2025. Got removed from App Store (triggered lawsuit). V-Bucks web purchases worked fine technically.
Match Group / Tinder 2019–2022 Added direct credit card entry in Android app (2019). Fought Google on alternative billing. Put $40M in escrow. 6–12 months for Android direct billing. Multi-year legal battle for compliance. Proven that dating apps can do D2C. Match has been doing it on Android for years.
Bumble Q3 2025–present "As soon as permitted" after Apr 2025 ruling, started testing alternative payments. Rolled out Apple Pay direct billing in Q4 2025. ~3–4 months from ruling to testing (Q3). ~6 months to measurable margin impact (Q4). 1pp gross margin expansion in Q4 2025. Apple Pay adoption >50% of US iOS payments by early Q1 2026.
Core Explanation #1: Companies that already have web infrastructure migrate in weeks; the bottleneck is legal permission, not engineering. Netflix, Spotify, and Epic all had web billing before they exited IAP. The technical capability was never the constraint — Apple's rules were. Once the Apr 2025 ruling dropped, Spotify shipped external links in 24 hours. Bumble went from "testing" to 1pp margin impact in one quarter.

Bumble's Specific Situation — Already Executing

This question is partially obsolete because Bumble is already doing it and reporting results:

Data Point Source
Direct billing testing began Q3 2025 — "as soon as permitted" Bumble Q3 2025 earnings call (Nov 6, 2025)
Nearly all US members had some form of direct billing by Q3 Alpha-Sense Q3 2025 summary
Apple Pay program implemented in Q4 2025 Bumble Q4 2025 earnings call (Mar 11, 2026)
1 full percentage point of Y/Y gross margin expansion from alternative billing in Q4 CFO Kevin Cook, Q4 2025 call
Apple Pay adoption >50% of US iOS payments by early Q1 2026 Bumble Q4 2025 earnings call
"Benefits expected to increase through 2026" Multiple Q4 2025 transcript sources
VERDICT on Question 2: The execution risk has largely materialized — and the answer is positive. Bumble went from zero to 1pp gross margin expansion in ~6 months, with adoption accelerating. The Bumble 2.0 platform (cloud-native, Spring 2026) will likely deepen D2C integration further. This is not a "hope it works someday" thesis — it's already contributing to margins.

What About Conversion Rate Drop-Off?

The Fear

Redirecting users from seamless 1-tap IAP to web checkout = friction = lower conversion.

IAP has Face ID / Touch ID / saved payment. Web requires login + card entry.

The Reality (Bumble's Data)

Bumble used Apple Pay as the D2C method — not a redirect to web. Same biometric tap, lower commission.

>50% adoption rate in months suggests minimal friction. Users don't even notice the difference.

This is the key insight: D2C ≠ clunky web checkout. Apple Pay / Google Pay direct billing preserves UX.

Core Explanation #2: The "conversion drop-off" concern assumed D2C meant web redirects. In practice, Apple Pay direct billing preserves the UX while cutting commissions. Bumble's >50% adoption rate proves users will switch payment rails when the experience is equivalent. The technical risk was overestimated.

Turnkey Infrastructure: Build vs. Buy

Solution What It Does Fee Timeline to Integrate
Stripe Billing Full subscription management, recurring billing, dunning, analytics. No-code migration toolkit for importing existing subscriptions. 2.9% + $0.30 per transaction Weeks for basic; 2–3 months for full migration with entitlement sync
RevenueCat Web Billing Cross-platform subscription management. Web SDK that syncs entitlements with iOS/Android apps. "No coding or hosting required." $0.012/MTR (monthly tracked revenue per $1) Days for basic web paywall; weeks for full cross-platform sync
Adapty Paywall optimization, A/B testing, web+mobile subscription unification. Tiered pricing Weeks
Epic Web Shops White-label web storefronts for game developers. Launched Jun 2025. 12% (Epic takes) Self-service setup

The ecosystem of D2C billing infrastructure has matured dramatically since 2025. What once required custom engineering is now largely turnkey.

FOCUS 2: Payment Infrastructure Winners

The D2C shift creates a structural reallocation of ~$20B+ in annual app store commissions toward payment processors, billing platforms, and subscription management tools. The question is who captures that flow.

Tier 1: Direct Beneficiaries

Company Ticker Why They Win Exposure
Stripe Private Default payment processor for web. Stripe Billing has purpose-built subscription migration tools. Every app that leaves IAP for web likely lands on Stripe. 🔴 High — this is their core business
Adyen ADYEN (AMS) Enterprise payment processing. Already handles payments for Spotify, Netflix, Uber. Natural recipient of large D2C migrations. 🟠 Medium-High — large enterprise focus
Block (Square) XYZ Payment infrastructure, but more SMB/physical. Less direct D2C app exposure than Stripe/Adyen. 🟡 Medium

Tier 2: Subscription & Billing Infrastructure

Company Status Why They Win
RevenueCat Private (Series C, $1.5B+ valuation) The "picks and shovels" play. Already the dominant mobile subscription SDK. Now has web billing. Every developer exploring D2C touches RevenueCat. Their web billing product launched specifically for the post-Epic world.
Chargebee Private Enterprise subscription billing. Handles complex pricing, dunning, revenue recognition. Target for larger companies building D2C.
Adapty Private Mobile paywall optimization + web. Competes with RevenueCat on the experimentation/optimization layer.

Tier 3: Indirect Beneficiaries

Core Explanation: The D2C shift is a tax cut that gets split between developers (margin) and infrastructure providers (volume). When $20B+ of transaction volume moves from Apple/Google IAP to web/direct billing, payment processors capture 2.5–3.5% of that volume. That's $500M–$700M in new annual revenue for the payment infrastructure ecosystem. Stripe (private) and Adyen (public) are the highest-conviction beneficiaries.
Category Examples Mechanism
Identity / Auth Okta, Auth0 Web checkout requires user authentication outside app stores. More web = more auth flows.
Fraud Prevention Sift, Riskified App stores handled fraud. D2C shifts fraud liability to developers, who need third-party solutions.
Analytics / Attribution Amplitude, Mixpanel Tracking cross-platform purchase funnels is harder without IAP. More demand for analytics tooling.

Synthesis: What Has Changed Since v2

Question v2 Assessment v3 Assessment (Now)
Can Bumble do D2C? Likely yes, post-Epic ruling Already doing it. 1pp margin impact. >50% Apple Pay adoption.
Will Apple block it? Unlikely given court rulings Cannot. Injunction permanent. Only question is fee level (0–12%).
How long to implement? Uncertain — 6–18 months? ~3–6 months to measurable impact. Already done.
Conversion rate risk? Moderate concern Minimal. Apple Pay preserves UX. >50% adoption proves it.
Reasonable fee risk? Not analyzed in v2 NEW RISK: Appeals court says Apple can charge something. Base case 5–12%. Even worst case, still saves 10pp+ vs IAP.
Bottom Line: The two uncertainties we set out to investigate — regulatory permission and implementation timeline — have both resolved favorably since we started tracking them. Bumble's own Q4 2025 earnings provide the strongest possible evidence: real margin impact, rapid adoption, benefits accelerating into 2026. The remaining uncertainty (reasonable fee determination) is a matter of degree, not direction. The D2C structural shift is happening now, not hypothetically.

Sources: Bumble Q3 2025 & Q4 2025 earnings call transcripts (Motley Fool, Investing.com, Globe & Mail); MacRumors (Dec 11, 2025 appeals ruling); Ars Technica; TechCrunch (May 2, 2025 Apple guidelines update); RevenueCat blog; Apple Developer documentation; The Verge; Variety; Reuters.

Report date: March 14, 2026 | Methodology: Non-variable explanations per David Deutsch