Stripe vs IAP: Payment Strategy for Mobile Apps (2026)

Apple's 30% (15%) commission on IAPs is the indie tax. Many indie devs ask: can I use Stripe instead?

The answer depends on what you're selling, where, and how. Done right, you save significant revenue. Done wrong, you violate App Store policy.

This is the working guide.

What Apple's rules say

Allowed via IAP (must use Apple's payment system)

• Digital goods consumed in the app.
• In-app subscriptions for ongoing digital services.
• Premium tier of an app.
• Virtual currency for games.

Not required for IAP (can use web/Stripe)

• Physical goods + services (Amazon, Uber).
• One-time consumable purchases for physical experience (Airbnb, OpenTable).
• B2B services purchased on a website with separate signup.
• Reader app exceptions (more on this).

Reader app exceptions

• Apps that primarily allow consumption of previously-purchased content.
• Books, music, video, news, magazines.
• Can sell subscriptions via web; users access on mobile.

EU Digital Markets Act changes (since 2024)

For EU users:

• Apps can use alternative payment processors.
• Apple charges Core Technology Fee (CTF) above thresholds.
• Different rules apply only in EU.

See EU DMA App Store Changes.

When Stripe makes sense

Use case 1: B2B SaaS app

User signs up + pays on web. Mobile app is access.

• Slack, Notion model.
• No Apple cut on web-purchased subscriptions.

Use case 2: Reader app

Books, magazines, news. User can access pre-purchased content.

• Books / Audible model.
• Sell subscriptions on web.

Use case 3: Service marketplace

Uber, DoorDash. Physical service delivered offline.

• No Apple cut on physical service.

Use case 4: Physical goods e-commerce

Apple-allowed.

Use case 5: Outside-iOS users only

Some apps target only Android + web. Stripe is then default.

When Stripe doesn't make sense

Use case 1: pure mobile-first app

Spotify-style. Apple requires IAP for digital subscriptions.

Use case 2: small revenue

Setup overhead of Stripe (compliance, taxes, etc.) doesn't pay back.

Use case 3: international + multi-country

Apple's IAP handles VAT / international currency. Stripe requires you to do this.

The hybrid pattern

Some apps use both:

• IAP for users who sign up in-app.
• Stripe for users who sign up on web.
• Same product, same access — different billing.

Allowed if:

• Web signup is clearly separate.
• Don't link to Stripe from inside the app (Apple's rule).
• Users can access app content regardless of where they paid.

What you can't do

Don't link directly from app to Stripe checkout

Apple rejects. You can use IAP or zero links to web payments.

Don't say "20% off on our website" in app

Considered "circumventing IAP." Rejected.

Don't bait users to web after install

Aggressive funneling to web post-install is gray area.

Don't use Stripe for clearly digital goods consumed in-app

Rejected.

The economics

Pure IAP

Net per $9.99/month subscriber:

• Year 1: ~$7.00 (30% Apple cut).
• Year 2+: ~$8.49 (15% Apple cut).

Pure Stripe

Net per $9.99/month:

• ~$9.42 (3% Stripe cut).
• But: you handle VAT, taxes, compliance.

Hybrid

Mix of both. Optimization depends on your install split.

If 80% of installs sign up in-app: IAP dominates. If 80% on web: Stripe-dominant model.

Operational reality of Stripe

Going web-based requires:

• Stripe setup: free, fast.
• Subscription management: handle renewals, cancellations, etc.
• VAT / sales tax: per region.
• Customer support: refund + dispute handling.
• Compliance: PCI, GDPR, etc.

Apple's IAP handles all of these for you. The 30% is the convenience tax.

Subscription tools

Tools like RevenueCat / Adapty / Apphud:

• Manage Apple IAP + Google billing.
• Some handle Stripe integration too.
• Worth using to abstract complexity.

See RevenueCat vs Adapty vs Apphud.

App Store changes in 2024-2025

Apple's pressure from regulators:

• EU DMA forced alternative payments.
• US states have similar proposals.
• Apple sometimes allows more flexibility on smaller / reader apps.

This is evolving. Watch for updates.

Specific reader app rules

If you qualify as "reader app":

• Music, video, books, magazines, news.
• Can sell subscriptions via web.
• Can include a link to your website (limited form).
• Apple's Music + Apple Books examples.

Apply via App Store Connect.

When to bother with Stripe

For most indie apps under $50k MRR: stick with IAP.

• Operational simplicity.
• Apple's 30% is annoying but tolerable.
• Setup cost of Stripe > savings.

For larger apps:

• Math may shift to Stripe.
• Negotiate alternatives carefully.

For B2B apps:

• Stripe + web onboarding is standard.

Common mistakes

• Linking from app to Stripe checkout. Rejection.
• Hiding Stripe access from Apple. Eventually caught.
• Underestimating Stripe operational burden. Tax, VAT, compliance.
• Switching mid-product without communication. Confuses users.
• Trying to game IAP rules. Apple rejects.

Specific allowed patterns

Pattern 1: web sign-up + mobile access

• User signs up + pays on web (Stripe).
• Downloads app.
• Logs in; mobile app is access portal.

Pattern 2: free trial + web-billing for power features

• App free with IAP for basic features.
• Power tier on web only.

Pattern 3: B2B + mobile companion

• Sales rep sells via web.
• User installs mobile companion.

Run an audit

Pricing + payment flow appears in your App Store listing. Run free ASO audit to verify everything aligns.

Related reading

• EU DMA App Store Changes
• Mobile App Tax & VAT Compliance for Indie Developers
• RevenueCat vs Adapty vs Apphud
• Mobile App Monetization Guide 2026
• Mobile App Pricing Psychology
• Subscription App Cancellation Flow Design
• App Store Pre-Submission Quality Checklist

Try the tools

• Free ASO audit
• Ad Analytics Calculator