Updated 16 Oct 2026: October 1 EU terms effective; RevenueCat automates Stripe/Paddle reporting. Flag conflicting October 1 rollout claims rather than asserting unverified availability.

Key details

  1. Apple’s unified EU App Store payment terms took effect October 1, 2026.
  2. Standard commissions: 26% IAP, 20% alternative in-app checkout, 15% external-link purchase; eligible reduced rates 15% IAP and 10% alternative routes.
  3. Relevant alternative-marketplace or Web Distribution transactions face a 5% Core Technology Commission.
  4. RevenueCat’s October 1 changelog says Stripe/Paddle in-app checkout and automated reporting require purchases-ios 5.89.0+.
  5. RevenueCat’s October 1 blog simultaneously calls the bottom-sheet checkout forthcoming; confirm exact availability.
  6. RevenueCat says it reports purchase tokens, renewals, refunds, cancellations and unused tokens for integrated transactions.
  7. App Review, entitlements, child safety and the 12-month payment-option commitment remain.
  8. Payment-provider costs and support obligations are additional to Apple commissions.

What builders should take away

  1. Compare net margin after Apple commission, processor charges and conversion, not headline commission alone.
  2. Verify RevenueCat’s actual checkout-sheet availability before planning a migration; its October 1 materials conflict.
  3. Confirm StoreKit entitlements, SDK 5.89.0+, storefront/age eligibility and App Review compliance.
  4. Test transaction and unused-token reporting plus renewals and refunds, even when vendor-automated.
  5. Model the 12-month payment-option commitment before experimenting with IAP alternatives.

What changed

Apple’s unified EU App Store business terms took effect October 1, 2026: standard commissions are 26% Apple IAP, 20% alternative in-app checkout and 15% external-link purchase, with reduced 15%/10% rates where eligible, plus 5% Core Technology Commission for relevant alternative-distribution transactions. RevenueCat’s October 1 changelog says Stripe Billing/Paddle Billing in-app checkout is available with purchases-ios 5.89.0+ and automates Apple transaction reporting. Its same-day blog, however, says the bottom-sheet checkout is still being worked on and offers early access, so exact rollout availability needs confirmation.

Why it matters

Small EU app developers now have a concrete alternative-payment implementation path rather than merely a new rate table. RevenueCat says it handles StoreKit token matching and reports purchases, renewals, refunds, cancellations and unused tokens, reducing costly bespoke reporting work. But Apple commissions, processor fees, entitlements, App Review, taxes, customer support, child safety and the 12-month payment-choice commitment still apply. Conflicting vendor rollout language means teams should confirm availability before committing.

The October 1 fee model is effective

Apple’s standard EU App Store commission is 26% for IAP, 20% for alternative in-app processing and 15% for qualifying external links. Eligible small-business programmes and mature subscriptions pay reduced 15%/10% rates. Relevant digital transactions outside the App Store can incur a 5% Core Technology Commission. The old per-install Core Technology Fee is retired, not all platform fees.

RevenueCat automates reporting rather than removing Apple’s commission

The October 1 RevenueCat changelog describes an in-app Stripe Billing or Paddle Billing checkout sheet and automatic Apple reporting with purchases-ios 5.89.0+. RevenueCat’s explanation covers StoreKit eligibility, disclosure and token flows, purchases, renewals, refunds, cancellations and unused tokens, plus tax-amount normalisation. Only purchases flowing through its integrations can be reconciled automatically.

Availability needs confirmation

RevenueCat’s October 1 changelog presents the checkout sheet as available. Its October 1 blog instead says the bottom-sheet checkout is still in development and asks developers to sign up for early access, while Web Billing support is forthcoming. Developers should verify the current SDK and product documentation or ask RevenueCat before committing to an in-app sheet.

The cost and conversion comparison is not a headline-rate comparison

Apple’s 20%/10% in-app alternative-payment commission sits alongside processor fees, taxes, refunds and support. A 15%/10% external-link route may add conversion friction. RevenueCat says Apple-fee-adjusted analytics are coming soon. Model net margin and real conversion by payment path.

Apple’s constraints remain

Apple requires alternative-payment entitlements, disclosure and token handling, eligible EU storefront and age targeting, App Review compliance and consistent payment-option choices across EU storefronts for 12 months. RevenueCat automates some implementation work but does not waive these requirements.

Practical rollout checklist

Confirm entitlement and storefront eligibility, purchases-ios 5.89.0+ and actual availability of the desired checkout, validate Apple-branded buttons and App Review, test token and renewal/refund reporting, and compare 12-month economics against IAP before migrating.

What to watch next

  • RevenueCat confirmation of in-app checkout general availability and later Web Billing support.
  • Independent checkout conversion and margin data under the new terms.
  • Apple clarifications and regulatory scrutiny of EU commissions.

Still unclear

  • Conflicting same-day RevenueCat rollout language makes in-app-sheet availability uncertain.
  • Effective fees depend on programme status, subscription age and payment path.
  • No independent conversion data yet verifies the financial effect of this exact integration.

Sources

Direct reading behind this dossier.

7 sources
Changes for apps in the European Union
Apple Developer primary/vendor

Primary operational documentation for unified terms, alternative distribution, payment options, reporting obligations and the 5% Core Technology Commission.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment