How to Avoid Apple's 30% Cut with Stripe (Legally, 2026)

You cannot trick Apple out of its commission, but you can legally avoid it in specific, well-defined cases, and in 2026 those cases are wider than they used to be. Physical goods and real-world services were never allowed to use In-App Purchase, so they already run through Stripe at roughly 97 cents on the dollar. In the United States, external payment links are now permitted after the Epic v. Apple contempt ruling, and in the EU the Digital Markets Act forces alternative payments open. For purely digital goods with no external route, IAP and its 15 to 30 percent still apply. The honest move is to know which bucket your product sits in, then build the checkout or paywall UI once and wire the payment path Apple actually allows.

When is Apple’s 30% actually required?

Only for digital goods and services consumed inside the app. Apple’s App Store Review Guidelines draw a hard line at section 3.1: unlockable features, subscriptions, in-game currency, and premium content must use In-App Purchase, which takes 30 percent (or 15 percent under the Small Business Program and for subscriptions after year one).

Anything a user consumes in the real world is the opposite. A physical product, a shipped item, a ride, a hotel night, a restaurant order, a one-to-one service: guideline 3.1.3 and 3.1.5 say these must not use IAP, and you route them through a normal processor like Stripe, Adyen, or PayPal. Uber, Amazon, and Deliveroo keep their full revenue minus a card fee for exactly this reason. If your app sells real-world value, you are already outside the 30 percent, and the only mistake is accidentally forcing IAP where it is forbidden.

What changed in 2026 for digital goods?

The United States opened up. After Apple was found in willful contempt of the original Epic injunction in April 2025, it updated guidelines 3.1.1 and 3.1.3 so US apps can show external payment links, buttons, and calls to action without an entitlement and without commission. In December 2025 the Ninth Circuit upheld the contempt finding but said Apple may charge a “reasonable commission tied to demonstrable costs,” and as MacRumors reported, no such rate has been approved, so external links in the US effectively run at 0 percent while the case moves toward the Supreme Court.

The EU is separate. Under the Digital Markets Act, iOS apps in the EU can use alternative payment providers and even alternative marketplaces, though Apple applies its own Core Technology Fee to high-volume apps. The practical takeaway: a digital-goods app can legitimately steer US and EU users to a web checkout today, and only users in stricter regions fall back to IAP.

Which route applies to your app?

Product type	Must use Apple IAP?	Who processes	Typical fee
Physical goods or real-world services	No, forbidden	Stripe, Adyen, PayPal	~2 to 3% card fee
Digital goods, US users	No, external link allowed	Stripe via web checkout	~0% Apple + card fee
Digital goods, EU users	No, DMA alternative payment	Stripe or alt provider	card fee plus possible CTF
Digital goods, other regions	Yes	Apple IAP	15 to 30%
Reader apps (media, cloud)	Account link allowed	Stripe on web	~0% Apple + card fee

How do you wire Stripe the compliant way?

Keep the purchase off the native screen and in the browser. The Stripe payments flow works the same in a React Native or SwiftUI app: you create a Checkout Session or Payment Link on your server, then open it in the system browser (SFSafariViewController or an external tab), let Stripe handle the card, and confirm the entitlement server-side through a webhook. For the in-app half of the US external-link flow, Apple requires its own disclosure sheet before the browser opens, which is the pattern in the external purchase link modal.

The UI you build once is the paywall and the checkout hand-off, not the payment field itself, since Stripe hosts that. A free VP0 template gives you the paywall, the plan selector, and the disclosure sheet as clean SwiftUI or React Native screens, so an AI builder wires the Stripe session and the webhook onto a layout that already matches Apple’s rules. The same approach carries the App Store path too, as in this Apple Pay and Stripe SwiftUI setup and a high-converting iOS paywall.

Common mistakes that get apps rejected

The expensive one is collecting a card in-app for digital goods in a region that still requires IAP. That is a guaranteed rejection, and it is the reason “just add Stripe” is bad advice without the regional split. Detect the store region and only show the external link where it is permitted.

Two more trip people up. Do not hide a paid digital upgrade behind a vague web link and hope the reviewer misses it, because anti-steering enforcement now runs both ways and mislabeled flows get pulled. And never treat the physical-goods exemption as a loophole for digital content: shipping a token or a sticker to “make it physical” is the kind of dodge Apple rejects on sight. The clean builds are the honest ones, matched to a real paywall for an AI-built app.

Key takeaways: keeping more of your revenue

• If you sell physical goods or real-world services, you already avoid the 30 percent: use Stripe and never wire IAP.
• For digital goods, US external links and EU DMA payments run near 0 percent Apple commission in 2026; other regions still need IAP.
• Build the paywall and checkout hand-off UI once, then let Stripe host the actual card entry through a web checkout.
• Split by store region in code, because showing an external card flow where IAP is still required is an instant rejection.
• Keep the flow honest and disclosed; anti-steering rules are enforced in both directions now.

Frequently asked questions

How do I avoid Apple’s 30% cut with Stripe? Match the route to your product. Physical goods and real-world services must not use IAP, so Stripe already keeps you at roughly 97 percent. For digital goods, US external payment links and EU DMA alternative payments let you take Stripe payments at near 0 percent Apple commission in 2026, while other regions still require In-App Purchase. Build the paywall and checkout hand-off once, then open a Stripe web checkout for the permitted flows.

Is bypassing Apple’s commission against the rules? Avoiding it in the ways Apple’s own guidelines allow is not a bypass at all. Selling physical goods outside IAP, using US external links, and using EU alternative payments are explicitly permitted. What breaks the rules is collecting a card in-app for digital goods where IAP is still mandatory, or hiding a paid upgrade to dodge review.

Do physical products really skip the 30% fee? Yes. Apple’s guidelines forbid IAP for goods and services used in the real world, so a store, delivery, or booking app processes payments through Stripe or another gateway and keeps everything except the card fee, usually 2 to 3 percent. This has been true since long before the Epic ruling.

What did the Epic v. Apple ruling change? It forced Apple to allow external payment links in US apps. After an April 2025 contempt finding, Apple updated its guidelines to permit external links without commission, and a December 2025 appeals decision left that at effectively 0 percent while a specific rate is decided. The case is still moving through the courts, so the exact US number may change.

Can I take Stripe payments in a React Native app on iOS? Yes, by creating the payment on your server and opening a Stripe Checkout Session or Payment Link in the system browser, then confirming the purchase with a webhook. The native app shows the paywall and, in the US flow, Apple’s required disclosure sheet before the browser opens. A free VP0 template supplies those screens so the Stripe wiring drops onto compliant UI.