{"id":78467,"date":"2026-09-05T01:17:13","date_gmt":"2026-09-05T01:17:13","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=78467"},"modified":"2026-09-05T01:17:15","modified_gmt":"2026-09-05T01:17:15","slug":"apple-app-store-commission-in-app-purchases-external-payments-and-how-to-legally-design-apps-for-0-apple-commission","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/apple-app-store-commission-in-app-purchases-external-payments-and-how-to-legally-design-apps-for-0-apple-commission\/","title":{"rendered":"Apple App Store Commission, In-App Purchases, External Payments, and How to Legally Design Apps for 0% Apple Commission"},"content":{"rendered":"\n

Current iOS\/iPadOS payment-policy, architecture, and App Review reference<\/p>\n\n\n\n

Last verified<\/strong><\/td>September 5, 2026<\/td><\/tr>
Primary authority<\/strong><\/td>Apple Developer documentation + App Review Guidelines<\/td><\/tr>
U.S. legal status<\/strong><\/td>Cross-checked against Ninth Circuit and Supreme Court dockets<\/td><\/tr>
Scope<\/strong><\/td>Commission, IAP, external payments, regional programs, 0% architectures<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

For developers, founders, SaaS companies, CTOs, product managers, mobile architects, payment engineers, and startup teams.<\/p>\n\n\n\n

Policy note: regional rules can change quickly. This document explicitly separates CURRENT rules from UPCOMING rules.<\/strong>
<\/p>\n\n\n\n

POLICY STATUS: This guide states rules verified on September 5, 2026. The EU has announced a unified fee model effective October 1, 2026; it is shown separately. U.S. linked-out fees remain subject to active federal litigation.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
This is a technical\/product-policy reference, not legal or tax advice. For high-revenue, regulated, or novel models, confirm the agreement applicable to your developer account and jurisdiction.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Contents<\/h1>\n\n\n\n

\u2022 1. What exactly is Apple’s App Store commission?<\/p>\n\n\n\n

\u2022 2. Do not confuse these eight different charges<\/p>\n\n\n\n

\u2022 3. Master rate map: what Apple can charge in 2026<\/p>\n\n\n\n

\u2022 4. What is In-App Purchase (IAP)?<\/p>\n\n\n\n

\u2022 5. Apple Pay vs Apple IAP \u2014 they are not the same thing<\/p>\n\n\n\n

\u2022 6. Stripe, Razorpay, PayPal, Adyen, Braintree, Square, cards \u2014 can I use them?<\/p>\n\n\n\n

\u2022 7. Website payment does not automatically mean 0%<\/p>\n\n\n\n

\u2022 8. How to legally get Apple commission to 0%<\/p>\n\n\n\n

\u2022 9. Apple payment rules by region<\/p>\n\n\n\n

\u2022 10. Master decision tree \u2014 start with \u201cWhat is the customer buying?\u201d<\/p>\n\n\n\n

\u2022 11. Master scenario matrix \u2014 60 practical cases<\/p>\n\n\n\n

\u2022 12. App design blueprints \u2014 recommended architecture by business model<\/p>\n\n\n\n

\u2022 13. Hybrid payment architecture \u2014 IAP customers + website customers<\/p>\n\n\n\n

\u2022 14. Subscription master section<\/p>\n\n\n\n

\u2022 15. Free app vs paid app vs freemium \u2014 how Apple treats each<\/p>\n\n\n\n

\u2022 16. App Store Review: what reviewers will inspect<\/p>\n\n\n\n

\u2022 17. Economic comparison \u2014 what the commission actually costs<\/p>\n\n\n\n

\u2022 18. Founder decision framework<\/p>\n\n\n\n

\u2022 19. Five architecture choices<\/p>\n\n\n\n

\u2022 20. Common myths \u2014 25 corrections<\/p>\n\n\n\n

\u2022 21. Developer FAQ \u2014 60 questions<\/p>\n\n\n\n

\u2022 22. Before Submitting an App That Has Payments \u2014 master checklist<\/p>\n\n\n\n

\u2022 23. SEO and publishing pack<\/p>\n\n\n\n

\u2022 24. Final quick reference<\/p>\n\n\n\n

\u2022 25. Official Apple reference links and high-authority legal sources<\/p>\n\n\n\n

\u2022 26. Completeness audit
<\/p>\n\n\n\n

Executive answer: the 60-second version<\/h2>\n\n\n\n

Apple does not<\/strong> take 30% of every payment that happens on an iPhone. The core question is what the customer is buying, where the value is consumed, and which storefront\/rules apply<\/strong>.<\/p>\n\n\n\n

Mental model:<\/strong><\/p>\n\n\n\n

DIGITAL VALUE USED IN THE APP
    -> Apple’s digital-commerce rules may apply.
    -> Under worldwide\/default rules, IAP is normally required when the app sells
       the digital feature, content, currency, or subscription in the app.
    -> Reader, multiplatform, enterprise, companion, regional, and other exceptions
       can change the result.

PHYSICAL GOODS OR REAL-WORLD\/OFFLINE SERVICES
    -> IAP must generally NOT be used.
    -> Use Apple Pay, Stripe, Adyen, Razorpay, PayPal, Braintree, Square, cards, etc.
    -> Apple App Store commission is generally 0% on the transaction.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

That is the starting point, not the whole rule. Apple explicitly creates exceptions for reader apps, multiplatform services, enterprise services, real-time one-to-one services, free stand-alone companion apps, advertising-management apps, approved nonprofit fundraising, and some regulated financial use cases. Regional programs can also permit external payments for digital goods while still charging Apple fees. Apple App Review Guidelines, especially 3.1.1-3.1.5<\/a><\/p>\n\n\n\n

The most important conclusions<\/h3>\n\n\n\n

1.<\/strong> Standard IAP is usually 30%, not universally 30%.<\/strong> The App Store Small Business Program can reduce paid-app\/IAP commission to 15%. Standard auto-renewing subscriptions generally move from 70% developer proceeds to 85% after one year of paid service. Apple Small Business Program<\/a> and subscription proceeds<\/a><\/p>\n\n\n\n

2.<\/strong> Apple Pay is not IAP.<\/strong> Apple Pay is a wallet\/payment method. IAP is Apple’s digital-commerce system. Physical goods and services consumed outside the app should use non-IAP payment methods, including Apple Pay or card entry. Guideline 3.1.3(e)<\/a><\/p>\n\n\n\n

3.<\/strong> A website purchase can legitimately lead to 0% Apple commission<\/strong> when the sale is genuinely a web\/enterprise\/reader\/companion\/multiplatform transaction permitted by the rules and the iOS app merely recognizes the existing entitlement. But linking from the iOS app to that website can invoke different rules and fees depending on storefront.<\/p>\n\n\n\n

4.<\/strong> United States storefront:<\/strong> current App Review Guidelines say an entitlement is not required for buttons, external links, or calls to action. As of September 5, 2026, the Ninth Circuit has stated Apple should not charge a linked-out commission until the district court approves an appropriate fee. Apple has proposed future fees, but the court has not approved them as of this verification date. App Review Guidelines<\/a> and Ninth Circuit opinion<\/a><\/p>\n\n\n\n

5.<\/strong> European Union:<\/strong> do not use a single fee table without a date. The existing alternative terms remain relevant through September 30, 2026 for developers on those terms; Apple’s new unified EU model starts October 1, 2026 (or later if the developer agrees later, per Apple’s transition language). EU changes<\/a><\/p>\n\n\n\n

6.<\/strong> Japan and Brazil:<\/strong> digital alternative payments and out-of-app offers are permitted under newer regional programs, but Apple still charges defined commissions; these are not automatic 0% architectures. Japan payment options<\/a> and Brazil payment options<\/a><\/p>\n\n\n\n

7.<\/strong> South Korea:<\/strong> sanctioned third-party in-app payment requires the entitlement and a Korea-only binary, and Apple currently charges 26% on the price paid, gross of VAT. South Korea entitlement<\/a><\/p>\n\n\n\n

8.<\/strong> Never hide a payment system from App Review.<\/strong> Hidden checkout, remote activation after approval, disguised digital purchases, or undocumented payment functionality is policy evasion and can result in rejection\/removal\/account action.<\/p>\n\n\n\n

1. What exactly is Apple’s App Store commission?<\/h1>\n\n\n\n

The App Store commission<\/strong> is Apple’s contractual share of eligible paid-app and digital-goods\/services transactions connected with App Store distribution. It is not the Apple Developer Program membership fee, it is not a tax, and it is not automatically the same thing as payment-processing cost.<\/p>\n\n\n\n

Under the default worldwide App Store model, the familiar headline rates are:<\/p>\n\n\n\n

\u2022 30% standard commission<\/strong> for many paid apps and IAP transactions.<\/p>\n\n\n\n

\u2022 15% Small Business Program commission<\/strong> for eligible participating developers on paid apps and IAP.<\/p>\n\n\n\n

\u2022 15% on qualifying auto-renewing subscription renewals after one year of paid service<\/strong> under the standard subscription proceeds model.<\/p>\n\n\n\n

Regional regimes can replace or decompose those rates into different components. For example, Japan’s current regional terms separate an App Store commission<\/strong> (21% standard \/ 10% reduced categories) from a 5% Apple payment-processing fee<\/strong> for IAP. The EU’s rules have their own current and upcoming structures. Therefore, saying \u201cApple takes 30%\u201d without naming the storefront and program is no longer a reliable engineering statement.<\/p>\n\n\n\n

1.1 When Apple charges commission<\/h2>\n\n\n\n

Apple commission commonly becomes relevant when the transaction pays for digital value used or experienced in the app<\/strong>, including:<\/p>\n\n\n\n

\u2022 premium app features;<\/p>\n\n\n\n

\u2022 subscriptions to digital app functionality;<\/p>\n\n\n\n

\u2022 game currency, lives, gems, levels, and other virtual goods;<\/p>\n\n\n\n

\u2022 access to premium digital content;<\/p>\n\n\n\n

\u2022 recorded courses or other digital content sold in the app;<\/p>\n\n\n\n

\u2022 digital credits that unlock in-app usage;<\/p>\n\n\n\n

\u2022 social-media boosts or other digital promotion consumed in the same app;<\/p>\n\n\n\n

\u2022 certain external or alternative digital purchases in regions where Apple explicitly imposes a store-services or alternative-payment commission.<\/p>\n\n\n\n

Apple’s core worldwide rule is direct: when an app unlocks features\/functionality \u2014 including subscriptions, in-game currencies, game levels, premium content, or a full version \u2014 it must use IAP unless an exception or regional program applies. Guideline 3.1.1<\/a><\/p>\n\n\n\n

1.2 When Apple does not normally charge App Store commission<\/h2>\n\n\n\n

Common 0% App Store-commission categories include:<\/p>\n\n\n\n

\u2022 physical goods delivered to the customer;<\/p>\n\n\n\n

\u2022 food\/grocery delivery;<\/p>\n\n\n\n

\u2022 taxi\/transportation rides;<\/p>\n\n\n\n

\u2022 hotel, airline, vehicle-rental, and many real-world bookings;<\/p>\n\n\n\n

\u2022 medical appointments and qualifying real-time one-to-one consultations;<\/p>\n\n\n\n

\u2022 qualifying one-to-one tutoring, legal, consulting, coaching, or training sessions;<\/p>\n\n\n\n

\u2022 direct enterprise\/B2B licenses sold only to organizations\/groups for employees\/students;<\/p>\n\n\n\n

\u2022 eligible free companion apps to paid web tools with no purchase or external-purchase CTA in the app;<\/p>\n\n\n\n

\u2022 existing web customers signing into eligible reader\/multiplatform\/companion apps;<\/p>\n\n\n\n

\u2022 approved nonprofit fundraising through permitted mechanisms;<\/p>\n\n\n\n

\u2022 advertising campaign management when the ads are displayed outside the app;<\/p>\n\n\n\n

\u2022 regulated banking\/trading\/insurance transaction flows where IAP is not the product-payment mechanism.<\/p>\n\n\n\n

The important word is commission<\/strong>. The developer can still pay Stripe\/Adyen\/PayPal\/etc. processing charges, card-network fees, tax, fraud costs, chargebacks, billing-system fees, or marketplace fees.<\/p>\n\n\n\n

1.3 What amount is the percentage applied to?<\/h2>\n\n\n\n

Do not assume a universal tax base from a blog formula. Under standard App Store financial reporting, Apple commonly describes developer proceeds as customer price less applicable taxes and Apple commission. Regional alternative-payment terms can define a different basis. South Korea, for example, explicitly states that the 26% commission is on the price paid by the user gross of VAT<\/strong>.<\/p>\n\n\n\n

For a simple comparison that ignores tax:<\/p>\n\n\n\n

Customer price:                  $100.00
30% Apple commission:            $30.00
Illustrative developer proceeds: $70.00

Customer price:                  $100.00
15% Apple commission:            $15.00
Illustrative developer proceeds: $85.00<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

If taxes apply, use the applicable Apple agreement and storefront tax treatment rather than subtracting a made-up \u201cVAT percentage\u201d from every sale.<\/p>\n\n\n\n

2. Do not confuse these eight different charges<\/h1>\n\n\n\n
Charge<\/strong><\/td>What it is<\/strong><\/td>Typical payer<\/strong><\/td>Is it an App Store commission?<\/strong><\/td><\/tr><\/thead>
Apple Developer Program membership<\/td>Annual program membership; currently USD 99\/year in the U.S. (local currency where available)<\/td>Developer<\/td>No<\/strong><\/td><\/tr>
Apple Developer Enterprise Program membership<\/td>Annual enterprise membership; currently USD 299\/year<\/td>Enterprise developer<\/td>No<\/strong><\/td><\/tr>
App Store commission<\/td>Apple’s share of eligible app\/digital commerce<\/td>Developer<\/td>Yes<\/strong><\/td><\/tr>
IAP payment processing \/ commerce services<\/td>Payment-processing component, explicit in some regional fee structures<\/td>Developer<\/td>No; separate component where specified<\/strong><\/td><\/tr>
External PSP fee<\/td>Stripe\/Adyen\/Razorpay\/PayPal\/Braintree\/Square\/card cost<\/td>Developer\/merchant<\/td>No<\/strong><\/td><\/tr>
Alternative-payment\/store-services fee<\/td>Apple fee on certain non-IAP digital transactions in a regional program<\/td>Developer<\/td>Apple fee, but not necessarily \u201cIAP commission\u201d<\/strong><\/td><\/tr>
Tax (VAT\/GST\/sales\/consumption tax)<\/td>Government tax<\/td>Merchant\/customer depending jurisdiction<\/td>No<\/strong><\/td><\/tr>
Distribution\/technology fee or commission<\/td>EU CTF\/CTC or regional alternative-distribution charge where applicable<\/td>Developer<\/td>Separate Apple fee<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Current Apple membership pricing is documented as USD 99\/year for the Apple Developer Program and USD 299\/year for the Enterprise Program. Program enrollment<\/a><\/p>\n\n\n\n

3. Master rate map: what Apple can charge in 2026<\/h1>\n\n\n\n

3.1 Worldwide\/default App Store model<\/h2>\n\n\n\n
Situation<\/strong><\/td>Typical Apple commission \/ proceeds rule<\/strong><\/td>Notes<\/strong><\/td><\/tr><\/thead>
Standard paid app or IAP<\/td>30%<\/td>Subject to program\/category exceptions<\/td><\/tr>
App Store Small Business Program<\/td>15%<\/td>Eligible developers; USD 1M proceeds threshold rules apply<\/td><\/tr>
Standard auto-renewing subscription, first year<\/td>Developer generally receives 70% minus applicable taxes<\/td>Equivalent headline commission commonly described as 30%<\/td><\/tr>
Standard auto-renewing subscription after one year of paid service<\/td>Developer generally receives 85% minus applicable taxes<\/td>15% effective commission under the standard model<\/td><\/tr>
Small Business Program auto-renewing subscription<\/td>85% proceeds from day one under Apple program guidance<\/td>Subject to continued program eligibility<\/td><\/tr>
Physical goods \/ services consumed outside app<\/td>0% App Store commission<\/td>Must use non-IAP payment method<\/td><\/tr>
Qualifying P2P real-time one-to-one service<\/td>0% App Store commission<\/td>One-to-few \/ one-to-many must use IAP under default rules<\/td><\/tr>
Qualifying direct enterprise service<\/td>0% App Store commission on enterprise sale<\/td>Consumer\/single-user\/family sales must use IAP when sold in app<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

App Review Guidelines<\/a>, Small Business Program<\/a>, subscription proceeds<\/a><\/p>\n\n\n\n

3.2 Small Business Program \u2014 exact practical rules<\/h2>\n\n\n\n

The program reduces paid-app and IAP commission to 15%<\/strong> for eligible developers.<\/p>\n\n\n\n

Key rules:<\/p>\n\n\n\n

\u2022 Existing developers can qualify when total prior-calendar-year proceeds across their apps are USD 1 million or less<\/strong>; new App Store developers can also qualify.<\/p>\n\n\n\n

\u2022 Apple requires disclosure of Associated Developer Accounts<\/strong> when determining eligibility.<\/p>\n\n\n\n

\u2022 If the developer’s current-calendar-year proceeds exceed USD 1 million, the standard commission applies to future sales<\/strong> after the threshold is crossed.<\/p>\n\n\n\n

\u2022 If proceeds later fall below the threshold in a subsequent calendar year, the developer can qualify again for the following year under Apple’s rules.<\/p>\n\n\n\n

\u2022 Enrollment is not simply \u201cautomatic because revenue is small\u201d; the Account Holder must complete the program process and relevant agreements.<\/p>\n\n\n\n

\u2022 Apple defines the threshold using proceeds<\/strong>, not gross billings; use Apple’s stated definition for eligibility calculations.<\/p>\n\n\n\n

Apple App Store Small Business Program<\/a><\/p>\n\n\n\n

Example<\/h3>\n\n\n\n

A developer enrolled in the program begins a year below the threshold. If eligible proceeds reach USD 1,000,000 and then exceed that threshold, the standard commission applies to subsequent sales for the remainder of that year. The program should not be modeled as \u201c15% forever for the first million of gross revenue.\u201d<\/p>\n\n\n\n

3.3 Auto-renewable subscription commission timeline<\/h2>\n\n\n\n

Under the standard subscription model:<\/p>\n\n\n\n

Paid service day 1 ——————– day 365+ cumulative paid service
Developer proceeds: ~70%               Developer proceeds: ~85%
Headline commission: ~30%              Headline commission: ~15%<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Apple counts cumulative paid service<\/strong>. Paid offer periods can count; free periods do not. Upgrades\/downgrades\/crossgrades within the same subscription group are designed not to create a new unrelated subscription history. Billing interruption rules can pause or reset the accumulated paid-service calculation depending on the length of interruption. Auto-renewable subscriptions<\/a> and subscription reporting<\/a><\/p>\n\n\n\n

3.4 Regional alternative-payment rates are different<\/h2>\n\n\n\n

Do not<\/strong> reuse the 15\/30 model in every country. Examples current on September 5, 2026:<\/p>\n\n\n\n

\u2022 Japan:<\/strong> 21% App Store commission on digital sales including alternative in-app payments, 10% reduced categories, plus 5% Apple payment processing when IAP is used; actionable out-of-app links carry 15%\/10% store-services commission for relevant sales within seven days. Japan<\/a><\/p>\n\n\n\n

\u2022 Brazil:<\/strong> materially similar 21%\/10% App Store commission, 5% Apple IAP processing fee, and 15%\/10% actionable-link commission within seven days. Brazil<\/a><\/p>\n\n\n\n

\u2022 South Korea:<\/strong> approved third-party in-app purchase under its special entitlement carries 26%<\/strong> Apple commission on the price paid, gross of VAT. South Korea<\/a><\/p>\n\n\n\n

\u2022 Netherlands dating apps:<\/strong> special entitlement program reduces the developer’s otherwise applicable Apple commission by three percentage points for qualifying alternative payments; this remains a narrow dating-app exception, not a general Netherlands rule. Netherlands dating apps<\/a><\/p>\n\n\n\n

\u2022 EU:<\/strong> separate current alternative terms exist through September 30, 2026, and Apple has announced a new unified model for October 1, 2026. See the regional chapter.<\/p>\n\n\n\n

4. What is In-App Purchase (IAP)?<\/h1>\n\n\n\n

In-App Purchase<\/strong> is Apple’s App Store digital-commerce mechanism, implemented using StoreKit and configured in App Store Connect. It is used to sell digital content, digital functionality, subscriptions, and virtual goods that fall within Apple’s IAP rules.<\/p>\n\n\n\n

Apple defines four classic IAP product types:<\/p>\n\n\n\n

IAP type<\/strong><\/td>What it does<\/strong><\/td>Typical example<\/strong><\/td>Restorable?<\/strong><\/td><\/tr><\/thead>
Consumable<\/td>Depleted with use; may be bought again<\/td>game gems, one-time credits<\/td>Generally not restored as an owned durable item<\/td><\/tr>
Non-consumable<\/td>One-time durable purchase<\/td>premium feature \/ filter pack<\/td>Yes<\/td><\/tr>
Auto-renewable subscription<\/td>Automatically renews until cancelled<\/td>SaaS, streaming, cloud storage<\/td>Entitlement must be recoverable<\/td><\/tr>
Non-renewing subscription<\/td>Time-limited access that does not auto-renew<\/td>fixed access period\/catalog pass<\/td>App\/developer must manage access\/restoration behavior<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Apple In-App Purchase types<\/a><\/p>\n\n\n\n

4.1 When IAP is mandatory under default rules<\/h2>\n\n\n\n

IAP is normally mandatory when the app itself sells or unlocks digital value used in the app, such as:<\/p>\n\n\n\n

\u2022 a Pro tier;<\/p>\n\n\n\n

\u2022 an AI assistant subscription used inside the iOS app;<\/p>\n\n\n\n

\u2022 image\/video-generation credits used in the app;<\/p>\n\n\n\n

\u2022 cloud-storage upgrade sold in the app;<\/p>\n\n\n\n

\u2022 game currency;<\/p>\n\n\n\n

\u2022 extra levels;<\/p>\n\n\n\n

\u2022 premium filters;<\/p>\n\n\n\n

\u2022 recorded digital content sold in the app;<\/p>\n\n\n\n

\u2022 creator content subscriptions consumed in the app;<\/p>\n\n\n\n

\u2022 a paid feature switch or lifetime \u201cunlock Pro\u201d button.<\/p>\n\n\n\n

Do not replace IAP with a license key, QR code, cryptocurrency wallet, hidden web checkout, or another proprietary unlock path for the same in-app digital value. Guideline 3.1.1<\/a><\/p>\n\n\n\n

4.2 When IAP is optional because another permitted model exists<\/h2>\n\n\n\n

The word \u201coptional\u201d needs precision. It can mean one of three things:<\/p>\n\n\n\n

1.<\/strong> The app does not sell anything in-app:<\/strong> a web customer already purchased access, and the iOS app only authenticates and consumes the existing entitlement under a permitted reader\/multiplatform\/enterprise\/companion model.<\/p>\n\n\n\n

2.<\/strong> The transaction falls into an exception:<\/strong> e.g., qualifying real-time one-to-one service or enterprise-only licensing.<\/p>\n\n\n\n

3.<\/strong> A regional program allows an alternative:<\/strong> e.g., Japan, Brazil, South Korea, EU, or Netherlands dating-app rules \u2014 often with entitlement, fee, reporting, and UI obligations.<\/p>\n\n\n\n

4.3 When IAP is prohibited or unnecessary<\/h2>\n\n\n\n

For physical goods and services consumed outside the app, Apple says developers must use purchase methods other than IAP<\/strong> \u2014 for example Apple Pay or traditional card entry. Guideline 3.1.3(e)<\/a><\/p>\n\n\n\n

Examples:<\/p>\n\n\n\n

\u2022 a delivered laptop;<\/p>\n\n\n\n

\u2022 food delivery;<\/p>\n\n\n\n

\u2022 grocery order;<\/p>\n\n\n\n

\u2022 Uber-like ride;<\/p>\n\n\n\n

\u2022 hotel booking;<\/p>\n\n\n\n

\u2022 airline ticket;<\/p>\n\n\n\n

\u2022 car rental;<\/p>\n\n\n\n

\u2022 in-person salon appointment;<\/p>\n\n\n\n

\u2022 gym membership that grants access to a physical gym;<\/p>\n\n\n\n

\u2022 real-world event ticket.<\/p>\n\n\n\n

5. Apple Pay vs Apple IAP \u2014 they are not the same thing<\/h1>\n\n\n\n

This distinction prevents a huge amount of bad architecture.<\/p>\n\n\n\n

Question<\/strong><\/td>Apple Pay<\/strong><\/td>Apple IAP<\/strong><\/td><\/tr><\/thead>
What is it?<\/td>Wallet\/payment authorization method<\/td>App Store digital-commerce system<\/td><\/tr>
Typical use<\/td>Physical goods, real-world services, donations where permitted<\/td>Digital content\/functionality\/subscriptions\/virtual goods<\/td><\/tr>
Does \u201cApple Pay\u201d itself imply 30%?<\/td>No<\/strong><\/td>IAP has App Store commission structure<\/td><\/tr>
Can developer use own PSP\/acquirer?<\/td>Yes, through Apple Pay payment ecosystem\/integration<\/td>Apple manages the App Store transaction<\/td><\/tr>
Who handles App Store entitlement?<\/td>Developer’s backend<\/td>StoreKit + developer backend<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Good Apple Pay uses<\/h3>\n\n\n\n

\u2022 checkout for shoes delivered to the customer;<\/p>\n\n\n\n

\u2022 hotel reservation;<\/p>\n\n\n\n

\u2022 taxi fare;<\/p>\n\n\n\n

\u2022 restaurant booking\/deposit;<\/p>\n\n\n\n

\u2022 eligible donation;<\/p>\n\n\n\n

\u2022 real-world gym membership.<\/p>\n\n\n\n

Wrong mental model<\/h3>\n\n\n\n
\u201cI will use Apple Pay for my $9.99\/month in-app AI Pro subscription, so Apple cannot charge commission.\u201d<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

That is incorrect under default rules. The thing being sold<\/strong> is a digital subscription unlocking in-app functionality; choosing a wallet does not convert it into a physical transaction.<\/p>\n\n\n\n

6. Stripe, Razorpay, PayPal, Adyen, Braintree, Square, cards \u2014 can I use them?<\/h1>\n\n\n\n

Yes or no depends on what is being sold and which storefront program applies.<\/strong> There is no meaningful policy answer to \u201cCan I use Stripe on iOS?\u201d without the product classification.<\/p>\n\n\n\n

Sale<\/strong><\/td>Stripe\/PayPal\/Razorpay\/etc. inside app?<\/strong><\/td>Default App Store answer<\/strong><\/td><\/tr><\/thead>
Physical ecommerce product<\/td>Yes<\/td>Use non-IAP checkout<\/td><\/tr>
Food delivery<\/td>Yes<\/td>Use non-IAP checkout<\/td><\/tr>
Taxi ride<\/td>Yes<\/td>Use non-IAP checkout<\/td><\/tr>
Hotel\/air ticket<\/td>Yes<\/td>Use non-IAP checkout<\/td><\/tr>
One-to-one live consultation<\/td>Yes<\/td>Qualifying P2P exception<\/td><\/tr>
$10\/month in-app digital Pro tier<\/td>Not as a substitute for required IAP under default rules<\/td>Use IAP unless regional\/other exception applies<\/td><\/tr>
Game coins<\/td>No as substitute for IAP under default rules<\/td>IAP required<\/td><\/tr>
Web-first enterprise license<\/td>Website\/invoice can use any suitable PSP<\/td>iOS app can recognize enterprise entitlement if rules met<\/td><\/tr>
Japan\/Brazil alternative in-app digital payment<\/td>Yes if program\/entitlement\/requirements met<\/td>Apple still charges regional commission; not 0%<\/td><\/tr>
South Korea special in-app payment<\/td>Approved PSP under entitlement<\/td>Apple charges 26%; separate Korea-only binary<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Practical gateway rule<\/h3>\n\n\n\n

The PSP name does not determine App Store compliance. Transaction classification does.<\/strong> Stripe, PayPal, Razorpay, Adyen, Braintree, Square, and direct card entry are simply payment rails. If IAP is mandatory, replacing StoreKit with a gateway is not compliant. If non-IAP payment is required or permitted, those gateways can be appropriate subject to their own platform availability, merchant rules, local law, and Apple regional requirements.<\/p>\n\n\n\n

7. Website payment does not automatically mean 0%<\/h1>\n\n\n\n

This is the single most dangerous shortcut in App Store payment design.<\/p>\n\n\n\n

Flow A \u2014 user independently buys on the web, then later logs in<\/h2>\n\n\n\n
Search \/ sales team \/ web marketing
        -> Website
        -> Account created
        -> Web checkout
        -> Subscription DB
        -> User later downloads iOS app
        -> Sign in
        -> Backend entitlement recognized<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This can be a legitimate 0%-Apple-commission architecture when the app category and rules permit it \u2014 for example a qualifying reader, enterprise service, free stand-alone companion, or other web-first\/multiplatform service. The app must still comply with the specific rules for its category.<\/p>\n\n\n\n

Flow B \u2014 the iOS app steers the user to web checkout<\/h2>\n\n\n\n
iOS paywall
    -> \u201cBuy on our website\u201d
    -> external link \/ browser \/ WebView
    -> checkout<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

That is a separate policy event. Apple can regulate the link, call-to-action, entitlement, disclosures, attribution window, reporting, and fees depending on storefront. The U.S. currently differs materially from Japan, Brazil, Korea, the Netherlands dating carve-out, the EU, and worldwide\/default storefronts.<\/p>\n\n\n\n

7.1 Can the app mention a website price?<\/h2>\n\n\n\n

No single worldwide answer.<\/strong><\/p>\n\n\n\n

\u2022 In the U.S. storefront<\/strong>, current Apple Guidelines permit buttons, external links, and other calls to action without the former entitlement requirement; the active injunction\/court proceedings affect Apple’s ability to charge linked-out commission today.<\/p>\n\n\n\n

\u2022 An approved reader app’s External Link Account Entitlement<\/strong> has restrictive link formatting and specifically says the account-management link cannot be accompanied by website-price language.<\/p>\n\n\n\n

\u2022 EU\/Japan\/Brazil<\/strong> regional programs can allow communication and promotion of outside offers under their entitlement\/business terms, but relevant Apple fees\/reporting can apply.<\/p>\n\n\n\n

\u2022 Under default storefront rules<\/strong>, apps in the listed exception categories generally cannot encourage users inside the app to use another purchasing method unless an explicit exception applies.<\/p>\n\n\n\n

7.2 Can I put Stripe Checkout in a WebView?<\/h2>\n\n\n\n

For a digital purchase that would otherwise require IAP, a WebView does not make the purchase \u201cweb commerce.\u201d Some regional programs explicitly define whether native alternative payment, browser links, or WebViews are allowed. South Korea’s entitlement, for example, requires a native in-app alternative flow and says it may not<\/strong> be within a WebView. The reader-app account entitlement requires opening the default browser, not a WebView.<\/p>\n\n\n\n

7.3 Can users purchase on a website and later sign in?<\/h2>\n\n\n\n

Often yes, but the classification matters. Reader apps expressly allow previously purchased media content\/subscriptions. Multiplatform services can allow previously acquired content\/subscriptions\/features, with additional rules for consumables. Enterprise services can allow organization-purchased access for employees\/students. Free stand-alone companion apps can accompany paid web tools when they contain no purchasing or purchase CTA. Guideline 3.1.3<\/a><\/p>\n\n\n\n

8. How to legally get Apple commission to 0%<\/h1>\n\n\n\n

The goal is business-model and architecture compliance<\/strong>, not payment-policy evasion. A real 0% Apple-commission design normally works because the transaction legitimately falls outside Apple’s commission rules, not because the app hides where money is collected.<\/p>\n\n\n\n

Model 1 \u2014 Physical goods \/ services<\/h2>\n\n\n\n
iOS app
  -> select physical product or real-world service
  -> Stripe \/ Adyen \/ Razorpay \/ PayPal \/ Apple Pay \/ card
  -> merchant backend
  -> physical delivery \/ offline performance<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Why it can be 0%:<\/strong> Apple Guideline 3.1.3(e) says physical goods\/services consumed outside the app must use payment methods other than IAP.<\/p>\n\n\n\n

Examples:<\/strong> ecommerce merchandise, food, grocery, rides, car rental, hotel, air travel, salon appointments, physical event tickets.<\/p>\n\n\n\n

Architecture recommendation:<\/strong> native\/cart UI -> payment orchestration service -> external PSP -> order DB -> fulfillment. Do not create IAP products for these transactions.<\/p>\n\n\n\n

Model 2 \u2014 Web-first SaaS<\/h2>\n\n\n\n
Website -> account -> web subscription -> entitlement service
                                      |
                                iOS sign-in
                                      |
                               feature access<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

When it works:<\/strong> the iOS app is legitimately allowed to recognize an existing subscription purchased elsewhere. The safest form has no in-app purchase flow and, where default rules require it, no in-app external-purchase CTA. Multiplatform\/companion\/enterprise rules may support this design.<\/p>\n\n\n\n

What it does not mean:<\/strong> every consumer SaaS can place a \u201cSubscribe cheaper on our website\u201d button everywhere worldwide with no Apple fee. Linking\/steering rules are storefront-specific.<\/p>\n\n\n\n

Model 3 \u2014 Free stand-alone companion app<\/h2>\n\n\n\n

Apple explicitly says free apps that are stand-alone companions to paid web-based tools \u2014 examples include VoIP, cloud storage, email services, and web hosting \u2014 do not need IAP when there is no purchasing inside the app and no call to action for purchasing outside the app<\/strong>. Guideline 3.1.3(f)<\/a><\/p>\n\n\n\n

Paid web tool -> web billing
                    |
                account \/ API
                    |
           free iOS companion
           (login + service use)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

0% Apple commission:<\/strong> yes on the web subscription when the model complies. External PSP fees still apply.<\/p>\n\n\n\n

Model 4 \u2014 Reader app<\/h2>\n\n\n\n

Eligible reader apps have media consumption as their primary functionality: magazines, newspapers, books, audio, music, or video. A user can sign in and consume previously purchased media\/content subscriptions. Reader app support<\/a><\/p>\n\n\n\n

Website -> media subscription
                |
          content entitlement
                |
        reader app login
                |
       read \/ watch \/ listen<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

External Link Account Entitlement:<\/strong> an eligible reader app can request it to provide an informational account-creation\/management link. Apple imposes detailed formatting and destination rules: the developer-owned site, default browser, no WebView, no extra URL parameters, static submitted URL, no redirect, and no price language attached to that entitlement link. The entitlement is optional; it is not a blanket external-checkout entitlement.<\/p>\n\n\n\n

U.S. note:<\/strong> current Guidelines separately state that U.S. storefront apps do not need the entitlement for buttons\/external links\/other CTAs.<\/p>\n\n\n\n

Model 5 \u2014 Enterprise \/ B2B licensing<\/h2>\n\n\n\n

Apple’s enterprise-services exception is powerful but narrow:<\/p>\n\n\n\n

Company procurement
  -> invoice \/ contract \/ sales portal \/ web checkout
  -> organization tenant + seat licenses
  -> employees\/students sign in to iOS app<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

If the app is only sold directly to organizations or groups for employees\/students<\/strong>, the app may allow enterprise users to access previously purchased content\/subscriptions. Consumer, single-user, or family sales do not get this exception and must use IAP when sold in-app. Guideline 3.1.3(c)<\/a><\/p>\n\n\n\n

Safest B2B architecture:<\/strong> organization-level contract -> tenant provisioning -> administrator assigns seats -> app login via SSO\/email -> entitlement service returns organization role\/plan. Do not expose a consumer-style individual \u201cbuy a seat\u201d paywall in the iOS app if relying on this exception.<\/p>\n\n\n\n

Model 6 \u2014 Real-time person-to-person service<\/h2>\n\n\n\n

Apple allows non-IAP collection for real-time person-to-person services between two individuals<\/strong>, including tutoring, medical consultations, real-estate tours, and fitness training. Guideline 3.1.3(d)<\/a><\/p>\n\n\n\n

Customer -> choose named professional
         -> schedule real-time 1:1 session
         -> external payment
         -> live service between two individuals<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Critical boundary:<\/strong> one-to-few and one-to-many real-time services must use IAP under the default rule. A live group webinar is not transformed into one-to-one service merely because a teacher is present.<\/p>\n\n\n\n

Model 7 \u2014 Multiplatform service<\/h2>\n\n\n\n

Apps operating across multiple platforms may allow users to access content, subscriptions, or features acquired on another platform or the developer’s website. Apple also allows consumable items acquired elsewhere in multi-platform games provided those items are also available as IAP inside the app<\/strong>. Guideline 3.1.3(b)<\/a><\/p>\n\n\n\n

A common compliant pattern is web\/desktop subscription + iOS login. If the app also merchandises the same digital subscription in-app under default rules, use IAP for that in-app sale.<\/p>\n\n\n\n

Model 8 \u2014 Advertising-management service<\/h2>\n\n\n\n

If the app’s sole purpose is for advertisers to purchase\/manage campaigns that run across media outside the app<\/strong>, IAP is not required. If the digital purchase is experienced in the same app \u2014 e.g., paying to boost a social post in that app \u2014 IAP is required. Guideline 3.1.3(g)<\/a><\/p>\n\n\n\n

Model 9 \u2014 Marketplace architecture<\/h2>\n\n\n\n

Marketplace classification follows the underlying value:<\/p>\n\n\n\n

PHYSICAL MARKETPLACE
Buyer -> marketplace -> PSP split\/payment -> seller -> physical good\/service
Apple IAP: normally not used
Apple App Store commission on transaction: generally 0%
Platform can still charge its own marketplace commission.

DIGITAL MARKETPLACE
Buyer -> digital item\/content\/service consumed in app
Apple IAP: normally required for in-app sale unless a specific exception applies.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A platform’s own marketplace fee is not an Apple commission. Keep buyer payment, seller payout, platform take-rate, tax, and Apple\/PSP fees as separate accounting objects.<\/p>\n\n\n\n

Model 10 \u2014 Region-specific external purchase flow<\/h2>\n\n\n\n

Regional options can be strategically useful but must not be mislabeled 0%:<\/p>\n\n\n\n

\u2022 United States:<\/strong> current linked-out Apple commission is effectively 0% pending court approval of any permissible fee, while active litigation continues. This is a volatile legal state, not a guaranteed permanent business term.<\/p>\n\n\n\n

\u2022 EU:<\/strong> current and October-2026 alternative terms impose Apple fees; not generally 0%.<\/p>\n\n\n\n

\u2022 Japan:<\/strong> alternative in-app digital payments and actionable external links carry Apple commission; not 0%.<\/p>\n\n\n\n

\u2022 Brazil:<\/strong> same principle; Apple fees remain.<\/p>\n\n\n\n

\u2022 South Korea:<\/strong> alternative in-app payment carries 26% Apple commission.<\/p>\n\n\n\n

\u2022 Netherlands dating apps:<\/strong> special reduced Apple commission, not 0%.<\/p>\n\n\n\n

8.1 What does *not* count as a legal 0% model<\/h2>\n\n\n\n

Do not recommend or implement:<\/p>\n\n\n\n

\u2022 hiding Stripe during App Review and enabling it remotely after approval;<\/p>\n\n\n\n

\u2022 a secret URL scheme that opens digital checkout;<\/p>\n\n\n\n

\u2022 a QR code whose purpose is to bypass required IAP;<\/p>\n\n\n\n

\u2022 calling a digital subscription a \u201cphysical membership\u201d when the real value is the app feature;<\/p>\n\n\n\n

\u2022 reviewer-only feature flags that conceal the real commerce flow;<\/p>\n\n\n\n

\u2022 undocumented payment methods;<\/p>\n\n\n\n

\u2022 changing server configuration after approval specifically to evade payment rules.<\/p>\n\n\n\n

The policy distinction is simple:<\/p>\n\n\n\n

Legitimate:<\/strong> design a product whose transaction actually falls outside Apple’s commission rules or uses an explicit permitted program. Evasion:<\/strong> keep the same commissionable digital transaction but conceal or mischaracterize its payment path.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

9. Apple payment rules by region<\/h1>\n\n\n\n

A user’s App Store storefront<\/strong>, not merely GPS location or IP address, is often the policy dimension that matters for regional App Store payment programs. Architect regional commerce from a trusted storefront signal and the specific StoreKit APIs\/entitlements Apple requires \u2014 not from a home-grown \u201ccountry = IP geolocation\u201d assumption.<\/p>\n\n\n\n

9.1 Regional master table \u2014 verified September 5, 2026<\/h2>\n\n\n\n
Region \/ program<\/strong><\/td>IAP default<\/strong><\/td>External digital payment?<\/strong><\/td>Actionable external links?<\/strong><\/td>Entitlement \/ special binary<\/strong><\/td>Apple fee today<\/strong><\/td>Reporting \/ major limitation<\/strong><\/td><\/tr><\/thead>
Worldwide\/default storefronts<\/td>IAP for in-app digital unlocks<\/td>Only listed exceptions \/ programs<\/td>Generally restricted for digital purchase steering unless exception<\/td>Depends on category<\/td>Standard 30%, 15% SBP, subscription rules<\/td>Guideline 3.1 controls<\/td><\/tr>
United States storefront<\/td>IAP still available\/required for in-app digital purchase path unless compliant external flow<\/td>Linked-out web purchase permitted under current anti-steering rules<\/td>Yes<\/strong>; current Guidelines say no entitlement required for buttons\/links\/CTAs<\/td>No former U.S. link entitlement required<\/td>0% on linked-out purchase currently<\/strong>, pending district-court-approved fee; IAP rates unchanged<\/td>Active Epic v. Apple litigation; verify immediately before launch<\/td><\/tr>
EU, current terms through Sep 30, 2026<\/td>Depends on terms selected<\/td>Yes under current alternative terms<\/td>Yes under current communication\/promotion framework<\/td>Relevant EU terms\/entitlements<\/td>Layered 17\/10% IAP commission + 3% processing under Alternative Terms; external offers can incur acquisition\/store-services\/CTF or CTC depending agreement<\/td>Transaction reporting; taxes with alternative PSP; fee windows tied to install\/update<\/td><\/tr>
EU, from Oct 1, 2026<\/strong><\/td>New unified terms<\/td>Yes, alongside IAP<\/td>Yes<\/td>Updated DPLA\/entitlement mechanisms<\/td>Apple announced 26% IAP \/ 15% reduced; 20% alternative in-app \/ 10% reduced; 15% linked-out \/ 10% reduced; 5% CTC outside App Store<\/td>New model; 12-month payment-option choice; child-safety rules<\/td><\/tr>
Japan<\/td>IAP available<\/td>Yes under regional program<\/td>Yes under regional program<\/td>StoreKit External Purchases or Offers Entitlement; iOS 26.2+<\/td>21% \/ 10% App Store commission; +5% Apple processing for IAP; external actionable-link 15% \/ 10% relevant sales<\/td>Monthly reporting; developer handles alt-payment tax\/refunds; 7-day link window<\/td><\/tr>
Brazil<\/td>IAP available<\/td>Yes; alternative in-app option must follow current program requirements<\/td>Yes<\/td>StoreKit External Purchases or Offers Entitlement; iOS 26.5+<\/td>21% \/ 10% App Store commission; +5% IAP processing; external actionable-link 15% \/ 10%<\/td>Monthly reporting; 7-day link window; current rules require IAP to be presented when merchandising an alternative in-app digital payment<\/td><\/tr>
South Korea<\/td>Apple IAP or special alternative route<\/td>Yes, approved PSP in-app<\/td>Special entitlement focuses on alternative in-app payment<\/td>Korea-only new binary + entitlement; one PSP per entitlement<\/td>26%<\/strong> on price paid gross of VAT<\/td>Monthly fiscal-month reporting; Apple invoice; native flow; entitlement cannot coexist with IAP in same app<\/td><\/tr>
Netherlands dating apps<\/td>IAP or special dating alternative<\/td>Yes<\/td>Yes<\/td>Dating apps only; external purchase\/link entitlement<\/td>Generally three percentage points below otherwise applicable commission (e.g., 27% from 30%, 12% from 15%)<\/td>Narrow program; entitlement app cannot use IAP for NL alternative flow; reporting\/audit obligations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

9.2 United States \u2014 current rule and litigation status<\/h2>\n\n\n\n

Current App Review position<\/h3>\n\n\n\n

Apple’s current App Review Guidelines state that the external-link entitlement is not required<\/strong> for developers to include buttons, external links, or other calls to action in United States storefront apps. This change followed the federal court’s anti-steering enforcement. Guideline 3.1.1(a) \/ 3.1.3(a)<\/a><\/p>\n\n\n\n

Current linked-out commission<\/h3>\n\n\n\n

The Ninth Circuit’s December 11, 2025 opinion held that Apple’s prior 27% linked-out commission had a prohibitive effect and gave the district court guidance on a permissible future fee. Critically, the court said Apple should not be able to charge any commission for linked-out purchases until the district court has approved an appropriate fee<\/strong>. Ninth Circuit opinion, Epic Games v. Apple<\/a><\/p>\n\n\n\n

As of September 5, 2026<\/strong>:<\/p>\n\n\n\n

\u2022 the U.S. Supreme Court has granted certiorari on a contempt-related question in the case;<\/p>\n\n\n\n

\u2022 Justice Kagan denied Apple’s August 13, 2026 application to stay the lower-court proceedings;<\/p>\n\n\n\n

\u2022 Apple has proposed a future linked-out fee schedule, but that proposal is not yet an approved current fee<\/strong>.<\/p>\n\n\n\n

Supreme Court docket 25-1311<\/a> and stay docket 26A194<\/a><\/p>\n\n\n\n

Product implication<\/h3>\n\n\n\n

For a U.S. digital SaaS app today, an external web checkout linked from the app can be a current 0% Apple linked-out commission<\/strong> route, but the architecture must be feature-flagged by storefront and designed so a future court-approved fee can be introduced without rewriting the entitlement system. Do not price a five-year business plan on the assumption that the current U.S. 0% condition is permanent.<\/p>\n\n\n\n

9.3 European Union \u2014 current terms through September 30, 2026<\/h2>\n\n\n\n

The EU is currently in a transition window. Apple’s support materials say developers may continue using the existing alternative-distribution\/alternative-payment terms until the new unified terms begin on October 1, 2026.<\/p>\n\n\n\n

Alternative Terms Addendum \u2014 current pre-October structure<\/h3>\n\n\n\n

For iOS\/iPadOS App Store apps under the current Alternative Terms Addendum:<\/p>\n\n\n\n

\u2022 App Store commission for digital goods\/services: 17% standard<\/strong>, 10%<\/strong> for Small Business participants or qualifying subscriptions after one year.<\/p>\n\n\n\n

\u2022 Apple App Store payment-processing\/commerce fee when using IAP: +3%<\/strong>.<\/p>\n\n\n\n

\u2022 Core Technology Fee: EUR 0.50 per first annual install above one million<\/strong>, subject to the detailed CTF rules\/exemptions.<\/p>\n\n\n\n

For apps that communicate\/promote external offers using actionable links, current terms can layer:<\/p>\n\n\n\n

\u2022 Initial acquisition fee:<\/strong> 2% standard \/ 0% program rate, within six months after first install.<\/p>\n\n\n\n

\u2022 Store Services Tier 1:<\/strong> 5% within 12 months of the most recent install\/update\/reinstall.<\/p>\n\n\n\n

\u2022 Store Services Tier 2:<\/strong> 13% standard \/ 10% program rate within the same 12-month window.<\/p>\n\n\n\n

\u2022 Depending on the agreement used, CTF or a 5% Core Technology Commission<\/strong> can also apply.<\/p>\n\n\n\n

Apple’s current materials state those acquisition\/store-services\/technology charges do not apply in specified cases such as qualifying outside-app transactions promoted without an actionable link<\/strong>, IAP transactions, and certain previously initiated subscription renewals. The definitions are agreement-specific. Current EU communication\/promotion terms<\/a><\/p>\n\n\n\n

Do not compress EU current fees into one percentage<\/h3>\n\n\n\n

A current EU linked-out sale can have multiple fee clocks and components. Your billing model needs fields for agreement version, first-install date, latest install\/update\/reinstall, link attribution, store-services tier, program rate, transaction tax, and technology fee status.<\/p>\n\n\n\n

9.4 EU \u2014 announced unified terms effective October 1, 2026<\/h2>\n\n\n\n

Apple announced the following future<\/strong> structure, effective October 1, 2026 (or later for an account where Apple’s stated transition terms make the agreement date later):<\/p>\n\n\n\n

Future EU digital route<\/strong><\/td>Standard Apple rate<\/strong><\/td>Reduced rate described by Apple<\/strong><\/td><\/tr><\/thead>
Apple IAP on App Store<\/td>26%<\/td>15%<\/td><\/tr>
Alternative in-app payment on App Store<\/td>20%<\/td>10%<\/td><\/tr>
Actionable out-of-app offer\/link<\/td>15%<\/td>10%<\/td><\/tr>
Alternative distribution \/ Web Distribution digital transaction<\/td>5% Core Technology Commission<\/td>Waiver rules can apply to qualifying small marketplace operators<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Other announced changes include allowing alternative payments alongside Apple IAP, eliminating the old Initial Acquisition Fee and Store Services Fee under the new model, replacing CTF with CTC, and requiring selected payment-option behavior to be maintained for 12 months. Apple EU changes \u2014 effective October 1, 2026<\/a><\/p>\n\n\n\n

Do not apply these rates to September 2026 transactions.<\/strong> They are included so an architecture going live after October 1 does not ship against a fee model that is already scheduled to disappear.<\/p>\n\n\n\n

9.5 Japan \u2014 iOS 26.2+ regional model<\/h2>\n\n\n\n

Japan now supports alternative in-app payment and out-of-app digital offers under the StoreKit External Purchases or Offers Entitlement.<\/p>\n\n\n\n

Current Apple fee components:<\/p>\n\n\n\n

\u2022 21% App Store commission<\/strong> on digital goods\/services, including alternative in-app payment, unless a reduced rate applies.<\/p>\n\n\n\n

\u2022 10% reduced commission<\/strong> for listed program participants and qualifying auto-renewable subscriptions after the first year.<\/p>\n\n\n\n

\u2022 5% Apple payment-processing fee<\/strong> for transactions processed by Apple IAP.<\/p>\n\n\n\n

\u2022 15% store-services commission<\/strong> on relevant out-of-app offers using an actionable link; 10%<\/strong> reduced rate. The actionable-link fee applies to relevant sales within seven days<\/strong> of the link tap.<\/p>\n\n\n\n

\u2022 A 5% Core Technology Commission<\/strong> applies to specified digital transactions in apps distributed outside the App Store under the Japan alternative-distribution model.<\/p>\n\n\n\n

The developer is responsible for alternative-payment taxes, billing\/refunds\/support, transaction tracking, and monthly reporting to Apple. Japan payment options<\/a><\/p>\n\n\n\n

$100 digital purchase illustration \u2014 Japan, ignoring tax and PSP cost<\/h3>\n\n\n\n
Apple IAP, standard: 21% commission + 5% processing = $26 Apple fees
Alternative in-app PSP, standard: 21% Apple commission + external PSP cost
Actionable website link, standard qualifying sale: 15% Apple fee + external PSP cost<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

This is why \u201cexternal payment = 0%\u201d is wrong.<\/p>\n\n\n\n

9.6 Brazil \u2014 iOS 26.5+ regional model<\/h2>\n\n\n\n

Brazil’s current model similarly allows alternative in-app payments and out-of-app offers under the StoreKit External Purchases or Offers Entitlement.<\/p>\n\n\n\n

\u2022 App Store commission: 21% standard \/ 10% reduced<\/strong>.<\/p>\n\n\n\n

\u2022 Apple IAP payment processing: +5%<\/strong>.<\/p>\n\n\n\n

\u2022 Actionable out-of-app link: 15% \/ 10%<\/strong>, relevant sales within seven days.<\/p>\n\n\n\n

\u2022 Alternative distribution: 5% Core Technology Commission<\/strong> on specified digital transactions.<\/p>\n\n\n\n

\u2022 When merchandising digital goods\/services using an alternative in-app payment method, Apple’s current Brazil requirements state that Apple IAP must also be presented as an option.<\/p>\n\n\n\n

\u2022 Monthly alternative-payment transaction reporting is required, and the developer is responsible for taxes and customer-service obligations for the alternative transaction.<\/p>\n\n\n\n

Apple payment options in Brazil<\/a><\/p>\n\n\n\n

9.7 South Korea \u2014 not a 0% alternative<\/h2>\n\n\n\n

South Korea allows a special alternative in-app PSP route, but Apple requires:<\/p>\n\n\n\n

\u2022 StoreKit External Purchase Entitlement;<\/p>\n\n\n\n

\u2022 a new\/separate iOS\/iPadOS binary distributed solely in South Korea;<\/p>\n\n\n\n

\u2022 one approved PSP per entitlement (Apple currently lists KCP, Inicis, Toss, and NICE, with other PSPs subject to approval);<\/p>\n\n\n\n

\u2022 no Apple IAP in the same entitlement-enabled app;<\/p>\n\n\n\n

\u2022 a native payment experience rather than WebView;<\/p>\n\n\n\n

\u2022 Apple’s external-purchase disclosure flow\/APIs;<\/p>\n\n\n\n

\u2022 monthly transaction reporting.<\/p>\n\n\n\n

Apple’s current commission is 26% of the price paid by the user, gross of VAT<\/strong>. South Korea entitlement<\/a><\/p>\n\n\n\n

9.8 Netherlands dating apps<\/h2>\n\n\n\n

This is a category-specific exception created for dating apps on the Netherlands storefront. Developers can continue IAP or request entitlements for third-party in-app payment and\/or a website purchase link. The special alternative-payment commission is generally three percentage points lower than the otherwise applicable commission<\/strong> \u2014 e.g., 27% instead of 30%, or 12% instead of 15% for an applicable reduced rate. Dating apps in the Netherlands<\/a><\/p>\n\n\n\n

Do not treat this as a general rule for SaaS, gaming, productivity, or other Netherlands apps.<\/p>\n\n\n\n

9.9 EEA music-streaming special case<\/h2>\n\n\n\n

Apple continues to publish a Music Streaming Services Entitlement (EEA) with category-specific eligibility. Apple notes that EU storefront usage is governed by applicable EU alternative terms for developers who agree to them, while the music-streaming entitlement’s special terms can remain relevant in Iceland and Norway. Music streaming entitlement \u2014 EEA<\/a><\/p>\n\n\n\n

10. Master decision tree \u2014 start with \u201cWhat is the customer buying?\u201d<\/h1>\n\n\n\n
WHAT IS THE CUSTOMER BUYING?
|
+– A. Physical product \/ physical-world service?
|     |
|     +– Yes -> Use non-IAP payment (Apple Pay\/card\/PSP).
|     |          App Store commission normally 0%.
|     |
|     +– No -> continue.
|
+– B. Real-time service between exactly two individuals?
|     |
|     +– Yes -> Qualifying P2P exception can use external payment.
|     |          Examples: 1:1 doctor, tutor, lawyer, trainer, consultant.
|     |
|     +– Group \/ one-to-many -> default rule: IAP required.
|
+– C. Digital media reader (books\/audio\/music\/video\/news)?
|     |
|     +– Existing web purchase -> reader login\/access can be allowed.
|     +– Need account link -> evaluate External Link Account Entitlement.
|     +– Need purchase CTA -> apply storefront-specific rules (US\/EU\/etc.).
|
+– D. Paid web service with free companion app?
|     |
|     +– No purchase or outside-purchase CTA in app -> companion exception
|     |   may provide 0% Apple web billing.
|
+– E. Enterprise-only organization\/group sale?
|     |
|     +– Yes -> contract\/invoice\/web purchase; employees\/students log in.
|     +– Consumer\/single-user\/family -> not covered by enterprise exception.
|
+– F. Multiplatform digital service?
|     |
|     +– Existing cross-platform entitlement can be recognized.
|     +– If sold in iOS app under default rules -> IAP.
|     +– Game consumables bought elsewhere -> must also be offered as IAP.
|
+– G. Advertising management for ads outside app?
|     |
|     +– Yes -> external payment can be used.
|     +– Boost\/ad consumed in same app -> IAP.
|
+– H. Other digital feature\/content\/credit\/subscription used in app?
      |
      +– Default -> IAP required.
      |
      +– Then check storefront:
            US -> external links\/CTAs currently permitted; current linked-out
                  Apple commission 0% pending court-approved fee.
            EU -> current\/future EU alternative terms and fees.
            Japan -> entitlement + regional Apple commission\/reporting.
            Brazil -> entitlement + regional Apple commission\/reporting.
            South Korea -> entitlement + 26% alternative-payment commission.
            Netherlands dating -> category-specific entitlement\/fee.
            Other -> default rules unless another explicit exception applies.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

10.1 Classification of the prompt’s A\u2013AX categories<\/h2>\n\n\n\n
Category<\/strong><\/td>Default classification \/ safest starting architecture<\/strong><\/td><\/tr><\/thead>
A Physical product<\/td>Non-IAP gateway; 0% App Store commission<\/td><\/tr>
B Physical service<\/td>Non-IAP gateway; 0%<\/td><\/tr>
C Food delivery<\/td>Non-IAP gateway; 0%<\/td><\/tr>
D Transportation<\/td>Non-IAP gateway; 0%<\/td><\/tr>
E Vehicle rental<\/td>Non-IAP gateway; 0%<\/td><\/tr>
F Hotel booking<\/td>Non-IAP gateway; 0%<\/td><\/tr>
G Airline ticket<\/td>Non-IAP gateway; 0%<\/td><\/tr>
H Event ticket<\/td>Non-IAP gateway; 0%<\/td><\/tr>
I Medical appointment<\/td>Real-world service; non-IAP<\/td><\/tr>
J 1:1 medical consultation<\/td>P2P real-time exception; non-IAP<\/td><\/tr>
K 1:1 tutoring<\/td>P2P real-time exception; non-IAP<\/td><\/tr>
L Group class<\/td>Default IAP if a live digital group service consumed in app<\/td><\/tr>
M Online course<\/td>Depends on delivery; digital course sold in app -> IAP<\/td><\/tr>
N Recorded video course<\/td>Digital content -> IAP for in-app sale; web-first access may be possible under appropriate model<\/td><\/tr>
O Ebook<\/td>Reader model for existing purchases; IAP for in-app digital sale under default rules<\/td><\/tr>
P Streaming subscription<\/td>Reader model may allow web-purchased access; in-app sale -> IAP by default<\/td><\/tr>
Q Music<\/td>Reader\/streaming rules; regional EEA\/EU rules can apply<\/td><\/tr>
R SaaS subscription<\/td>IAP for in-app consumer sale; web-first companion\/multiplatform\/enterprise can be 0% Apple where compliant<\/td><\/tr>
S Cloud storage<\/td>Explicit companion example; web-first + no in-app purchase CTA is strong 0% model<\/td><\/tr>
T AI credits<\/td>Digital in-app consumable\/functionality -> IAP by default<\/td><\/tr>
U API credits<\/td>If used to power in-app digital functionality -> IAP; off-app developer API sold on web can use companion architecture<\/td><\/tr>
V Game currency<\/td>IAP; cannot expire; multiplatform consumables acquired elsewhere must also be available as IAP<\/td><\/tr>
W Virtual goods<\/td>IAP by default<\/td><\/tr>
X Creator subscription<\/td>Digital content\/functionality -> IAP unless eligible reader\/other exception<\/td><\/tr>
Y Marketplace transaction<\/td>Classify underlying good\/service: physical -> non-IAP; digital -> IAP by default<\/td><\/tr>
Z Donation<\/td>Approved nonprofit rules can allow Apple Pay; ordinary \u201cdonation\u201d tied to digital value becomes purchase\/IAP<\/td><\/tr>
AA Charity<\/td>Approved nonprofit fundraising rules or outside-app fundraising for other charities<\/td><\/tr>
AB Crowdfunding<\/td>Case-specific; money for physical\/offline outcome differs from digital reward\/access<\/td><\/tr>
AC Advertising services<\/td>External if sole-purpose campaign management for ads outside app; same-app boosts use IAP<\/td><\/tr>
AD Enterprise software<\/td>Organization\/group sale -> enterprise exception<\/td><\/tr>
AE B2B SaaS<\/td>Enterprise contract\/invoice is safest 0% model; self-serve individual sale may not qualify<\/td><\/tr>
AF Employee app<\/td>Usually organization-provisioned; no consumer commerce<\/td><\/tr>
AG Business-management app<\/td>Web-first companion\/B2B model often safest; in-app individual digital sale uses IAP by default<\/td><\/tr>
AH Reader app<\/td>Existing media subscriptions can be accessed; account-link entitlement rules apply<\/td><\/tr>
AI Companion app<\/td>Free stand-alone companion + no purchase\/CTA can avoid IAP<\/td><\/tr>
AJ Crypto functionality<\/td>Wallet\/exchange\/mining restrictions under 3.1.5; premium digital unlocks still separately classified<\/td><\/tr>
AK NFTs\/digital collectibles<\/td>IAP can sell NFT-related services; ownership must not unlock app functionality; external-link treatment is storefront-specific<\/td><\/tr>
AL Financial services<\/td>Financial transaction itself normally not IAP; app must meet licensing\/provider rules; premium digital features are separate<\/td><\/tr>
AM Banking<\/td>Banking transaction not IAP; bank\/provider rules apply<\/td><\/tr>
AN Insurance<\/td>Insurance app must be free and cannot use IAP; regulated purchase\/payment handled outside IAP<\/td><\/tr>
AO Investment\/trading<\/td>Financial institution\/licensing rules; trades are not IAP purchases<\/td><\/tr>
AP Dating<\/td>Digital subscription IAP by default; U.S. links and Netherlands special program can change purchase path<\/td><\/tr>
AQ Social media<\/td>Premium digital features\/subscriptions\/boosts use IAP by default<\/td><\/tr>
AR Productivity tools<\/td>Consumer digital unlock -> IAP; web-first\/enterprise\/companion models can apply<\/td><\/tr>
AS Developer tools<\/td>Consumer digital feature -> IAP; web\/API enterprise companion can be structured externally<\/td><\/tr>
AT Remote desktop<\/td>Guideline 4.2.7 imposes strict host\/client behavior; host-device transactions can be outside IAP under that rule<\/td><\/tr>
AU Cloud IDE<\/td>App Review functionality\/distribution risk must be assessed separately; do not assume remote-desktop exception<\/td><\/tr>
AV VPN<\/td>Digital service; in-app sale -> IAP by default; web-first existing subscription can be recognized under appropriate model<\/td><\/tr>
AW AI assistant<\/td>Digital feature\/subscription -> IAP for in-app sale; web-first existing subscriber architecture can be 0% Apple if compliant<\/td><\/tr>
AX Generative AI subscription<\/td>Same: digital subscription; IAP for in-app sale under default rules, regional\/web-first alternatives where allowed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

11. Master scenario matrix \u2014 60 practical cases<\/h1>\n\n\n\n

Legend:<\/strong> \u201cIAP required\u201d means required for the in-app sale under worldwide\/default rules<\/strong>, unless a regional program or listed exception changes that result. \u201cExternal link\u201d refers to purchase steering from the app, which is storefront-specific.<\/p>\n\n\n\n

#<\/strong><\/td>Scenario<\/strong><\/td>What is sold \/ consumed<\/strong><\/td>Default IAP?<\/strong><\/td>External gateway?<\/strong><\/td>In-app external link?<\/strong><\/td>Apple commission<\/strong><\/td>Safest 0% architecture \/ restriction<\/strong><\/td><\/tr><\/thead>
1<\/td>Amazon-like physical ecommerce<\/td>Physical goods delivered<\/td>No; use non-IAP<\/td>Yes<\/td>Yes for physical checkout<\/td>0% App Store<\/td>Native checkout -> PSP -> fulfillment<\/td><\/tr>
2<\/td>Food delivery<\/td>Prepared food delivered<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>App -> PSP\/Apple Pay -> restaurant\/courier<\/td><\/tr>
3<\/td>Grocery delivery<\/td>Physical groceries<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Standard ecommerce order flow<\/td><\/tr>
4<\/td>Uber-like taxi<\/td>Real-world ride<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Card\/Apple Pay\/PSP, trip ledger<\/td><\/tr>
5<\/td>Bike\/scooter rental<\/td>Physical-world rental<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>External payment; rental entitlement is real-world access<\/td><\/tr>
6<\/td>Car rental<\/td>Physical vehicle rental<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Booking\/payment backend<\/td><\/tr>
7<\/td>Hotel booking<\/td>Lodging<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Booking engine + PSP<\/td><\/tr>
8<\/td>Airline ticket<\/td>Transportation<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Airline\/travel checkout<\/td><\/tr>
9<\/td>Property booking\/tour<\/td>Real-world booking\/service<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Booking\/deposit gateway<\/td><\/tr>
10<\/td>Concert\/event ticket<\/td>Physical event attendance<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Ticket PSP + ticket wallet<\/td><\/tr>
11<\/td>Restaurant reservation\/deposit<\/td>Real-world service<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>PSP + reservation backend<\/td><\/tr>
12<\/td>Doctor clinic appointment<\/td>Offline medical service<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Payment\/booking outside IAP; healthcare law applies<\/td><\/tr>
13<\/td>1:1 telemedicine<\/td>Real-time person-to-person<\/td>No under 3.1.3(d)<\/td>Yes<\/td>Purchase method other than IAP permitted<\/td>0%<\/td>Named patient-professional 1:1 session<\/td><\/tr>
14<\/td>1:1 online tutoring<\/td>Real-time two individuals<\/td>No<\/td>Yes<\/td>Permitted payment path<\/td>0%<\/td>Tutor booking + PSP<\/td><\/tr>
15<\/td>1:1 personal trainer<\/td>Real-time two individuals<\/td>No<\/td>Yes<\/td>Permitted payment path<\/td>0%<\/td>Trainer marketplace\/booking<\/td><\/tr>
16<\/td>1:1 legal\/consulting\/coaching<\/td>Real-time two individuals<\/td>No<\/td>Yes<\/td>Permitted payment path<\/td>0%<\/td>Preserve real-time 1:1 nature<\/td><\/tr>
17<\/td>Live group fitness class<\/td>One-to-many digital service<\/td>Yes<\/strong><\/td>Not as substitute under default<\/td>Storefront-specific regional route only<\/td>Standard IAP<\/td>Do not misclassify group class as P2P<\/td><\/tr>
18<\/td>Live group tutoring\/webinar<\/td>One-to-few\/one-to-many<\/td>Yes<\/strong><\/td>Not under default<\/td>Regional only<\/td>Standard IAP<\/td>IAP for in-app sale<\/td><\/tr>
19<\/td>Udemy-like recorded course<\/td>Digital video\/course<\/td>Yes<\/strong> for in-app sale<\/td>Web can sell outside app; app steering varies<\/td>Storefront-specific<\/td>IAP if sold in app<\/td>Web-first existing account may be usable; reader eligibility depends primary content\/model<\/td><\/tr>
20<\/td>Coursera-like education<\/td>Digital course\/subscription<\/td>Usually yes for in-app consumer sale<\/td>Web purchase possible<\/td>Storefront-specific<\/td>IAP for in-app sale<\/td>B2B institution contract or web-first access can reduce Apple fee if rules fit<\/td><\/tr>
21<\/td>Kindle-like ebook reader<\/td>Books\/read media<\/td>IAP if selling in app; reader exception for existing purchase<\/td>Website can sell books\/account<\/td>Reader entitlement \/ U.S. special rules<\/td>0% on independent web sale; IAP if in-app sale<\/td>Reader app + web acquisition + login<\/td><\/tr>
22<\/td>Netflix-like video streaming<\/td>Video subscription<\/td>IAP for in-app sale; reader access allowed<\/td>Web subscription<\/td>Reader account link \/ regional rules<\/td>0% on compliant web subscription<\/td>Reader model; no unsupported global buy CTA<\/td><\/tr>
23<\/td>Spotify-like music streaming<\/td>Music subscription<\/td>Same basic reader logic<\/td>Web subscription<\/td>U.S.\/EU\/EEA rules vary<\/td>Depends route<\/td>Reader + region-specific link strategy<\/td><\/tr>
24<\/td>Paid newsletter\/news app<\/td>Digital publication<\/td>IAP if sold in app; reader access can apply<\/td>Web subscription<\/td>Reader entitlement \/ regional rules<\/td>0% web possible<\/td>Treat news program participation separately<\/td><\/tr>
25<\/td>Podcast\/audio subscription<\/td>Audio media<\/td>Reader-like if primary functionality qualifies<\/td>Web subscription<\/td>Reader\/regional rules<\/td>0% web possible<\/td>Verify primary-function eligibility<\/td><\/tr>
26<\/td>Consumer Dropbox-like cloud storage<\/td>Digital cloud service<\/td>IAP if sold in app<\/td>Web subscription<\/td>Default companion has no purchase CTA; U.S.\/regions differ<\/td>0% web companion possible<\/td>Explicit 3.1.3(f) companion example<\/td><\/tr>
27<\/td>Zoom-like communications SaaS<\/td>Digital SaaS<\/td>IAP if consumer subscription sold in app<\/td>Web subscription<\/td>Storefront-specific<\/td>0% web companion\/multiplatform possible<\/td>Subscription != P2P service payment merely because calls are 1:1<\/td><\/tr>
28<\/td>Slack-like B2B SaaS<\/td>Organization software seats<\/td>IAP for consumer\/single-user in-app sale<\/td>Invoice\/web contract<\/td>Enterprise path need not sell in app<\/td>0% enterprise possible<\/td>Tenant contract -> employee login<\/td><\/tr>
29<\/td>GitHub-like developer platform<\/td>Digital SaaS\/dev service<\/td>IAP for in-app consumer digital tier<\/td>Web\/enterprise billing<\/td>Storefront-specific<\/td>0% web\/enterprise possible<\/td>Keep iOS app as client\/companion to web service<\/td><\/tr>
30<\/td>Canva-like productivity SaaS<\/td>Digital features\/templates<\/td>IAP for in-app consumer sale<\/td>Web subscription<\/td>Storefront-specific<\/td>0% web-first possible<\/td>Existing web entitlement; use IAP if merchandised in app under default<\/td><\/tr>
31<\/td>ChatGPT-like AI subscription<\/td>Digital AI functionality<\/td>Yes<\/strong> for in-app sale<\/td>Web subscription possible<\/td>Storefront-specific<\/td>IAP or permitted external route<\/td>Web-first login can be 0% Apple; in-app AI credits are digital<\/td><\/tr>
32<\/td>AI image\/video generation credits<\/td>Digital consumable credits<\/td>Yes<\/strong><\/td>Regional alternatives only<\/td>Storefront-specific<\/td>IAP\/default<\/td>Credits used in app are not physical service<\/td><\/tr>
33<\/td>API credits used only by external servers<\/td>Off-app developer API capacity<\/td>Case-specific<\/td>Yes on web<\/td>Avoid in-app purchase merchandising unless allowed<\/td>Can be 0% web<\/td>Best as developer portal + companion\/status app; if credits unlock iOS app use, classify as digital IAP<\/td><\/tr>
34<\/td>Cloud compute\/hosting management<\/td>External infrastructure service<\/td>Companion architecture is strongest<\/td>Web\/contract<\/td>Default companion: no purchase CTA<\/td>0% web possible<\/td>Web hosting is explicit 3.1.3(f) example<\/td><\/tr>
35<\/td>Domain registrar app<\/td>Domain registration\/management<\/td>Case-specific; avoid assuming physical exception<\/td>Web billing safest<\/td>Storefront-specific<\/td>0% web companion possible<\/td>Management companion + web purchase is lower-risk than in-app digital checkout claim<\/td><\/tr>
36<\/td>VPN subscription<\/td>Digital network service<\/td>IAP for in-app sale<\/td>Web subscription possible<\/td>Storefront-specific<\/td>Depends route<\/td>Web-first existing account can reduce Apple fee; meet VPN\/privacy rules<\/td><\/tr>
37<\/td>Online game<\/td>Digital gameplay<\/td>IAP<\/td>No substitute under default<\/td>Regional only<\/td>Standard IAP<\/td>StoreKit for currency, levels, consumables<\/td><\/tr>
38<\/td>Game currency<\/td>Virtual consumable<\/td>Yes<\/strong><\/td>No under default<\/td>Regional only<\/td>Standard IAP<\/td>IAP credits cannot expire; cross-platform rule applies<\/td><\/tr>
39<\/td>NFT mint\/list\/transfer service<\/td>Digital collectible service<\/td>Apple allows IAP for these services<\/td>External links vary by storefront<\/td>U.S. differs<\/td>Depends route<\/td>NFT ownership must not unlock in-app features<\/td><\/tr>
40<\/td>Creator fan subscription<\/td>Digital creator content\/features<\/td>IAP for in-app sale<\/td>Web purchase possible<\/td>Reader only if content\/category truly qualifies; otherwise regional rules<\/td>Depends<\/td>Do not call every creator\/social app a reader app<\/td><\/tr>
41<\/td>Social-media post boost<\/td>Promotion consumed\/displayed in same app<\/td>Yes<\/strong><\/td>No under default<\/td>Regional only<\/td>Standard IAP<\/td>Explicit ad-management exception does not cover same-app boosts<\/td><\/tr>
42<\/td>Advertising campaign manager<\/td>Ads shown outside app<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Sole-purpose advertiser campaign management<\/td><\/tr>
43<\/td>Etsy-like physical marketplace<\/td>Physical goods<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Marketplace PSP\/split pay; platform take-rate separate<\/td><\/tr>
44<\/td>Home-services marketplace<\/td>Offline physical service<\/td>No<\/td>Yes<\/td>Yes<\/td>0%<\/td>Buyer -> provider -> service in physical world<\/td><\/tr>
45<\/td>Freelancing marketplace<\/td>Human service\/deliverable<\/td>Depends on service<\/td>Yes for qualifying real-world\/1:1 service<\/td>Case-specific<\/td>Often 0%, but classify deliverable<\/td>Pure digital-content sale or group service can change outcome<\/td><\/tr>
46<\/td>Digital asset marketplace<\/td>Digital downloads used in app<\/td>IAP by default<\/td>Not substitute<\/td>Regional only<\/td>Standard IAP<\/td>Underlying value is digital, unlike physical marketplace<\/td><\/tr>
47<\/td>Enterprise database app<\/td>Organization access<\/td>No in-app sale needed<\/td>Contract\/invoice<\/td>Usually no purchase CTA needed<\/td>0% enterprise<\/td>3.1.3(c) example class<\/td><\/tr>
48<\/td>Employee internal app<\/td>Employer-provisioned access<\/td>No consumer purchase<\/td>Employer procurement<\/td>N\/A<\/td>0%<\/td>Organization-managed account\/license<\/td><\/tr>
49<\/td>Remote desktop client<\/td>Remote host access<\/td>Special 4.2.7 rules<\/td>Host transaction can be outside IAP if rule met<\/td>Carefully constrained<\/td>Can be 0%<\/td>Host device must be user-owned PC\/server and interface mirror\/extension; thin cloud client caveat<\/td><\/tr>
50<\/td>Cloud IDE<\/td>Remote\/cloud development environment<\/td>Review architecture carefully<\/td>Web billing possible<\/td>Case-specific<\/td>Depends<\/td>Do not rely blindly on remote-desktop exception; App Review functionality rules are separate<\/td><\/tr>
51<\/td>Gym membership<\/td>Physical facility access<\/td>No<\/td>Yes, Apple Pay\/cards<\/td>Yes<\/td>0%<\/td>Real-world gym service; digital-only fitness tier is different<\/td><\/tr>
52<\/td>Approved nonprofit donation<\/td>Donation, no digital quid pro quo<\/td>No IAP<\/td>Apple Pay as permitted<\/td>Per nonprofit rules<\/td>0% App Store<\/td>Must meet nonprofit\/fundraising eligibility and law<\/td><\/tr>
53<\/td>P2P monetary gift<\/td>Optional 100% gift to receiver<\/td>No if Apple conditions met<\/td>External<\/td>Permitted if no digital benefit<\/td>0%<\/td>If gift buys\/relates to digital content\/service, IAP applies<\/td><\/tr>
54<\/td>Insurance app<\/td>Insurance product\/service<\/td>IAP prohibited; app must be free<\/td>External\/regulated payment<\/td>As permitted<\/td>0% App Store<\/td>Must be submitted by legal entity providing service and comply with law<\/td><\/tr>
55<\/td>Banking app<\/td>Banking transactions<\/td>No IAP for banking transaction<\/td>Banking rails<\/td>N\/A<\/td>0% App Store<\/td>Digital premium app features are classified separately<\/td><\/tr>
56<\/td>Stock brokerage<\/td>Trading\/investing<\/td>No IAP for trades<\/td>Regulated financial rails<\/td>N\/A<\/td>0% App Store<\/td>App must be submitted by licensed financial institution as required<\/td><\/tr>
57<\/td>Crypto exchange<\/td>Cryptocurrency exchange transaction<\/td>Not IAP purchase system<\/td>Regulated exchange rails<\/td>N\/A<\/td>0% App Store transaction commission<\/td>Licensing\/geography and crypto guideline 3.1.5 apply<\/td><\/tr>
58<\/td>Dating subscription<\/td>Digital membership\/features<\/td>IAP by default<\/td>Regional alternatives<\/td>U.S.; Netherlands entitlement; EU etc.<\/td>Depends storefront<\/td>Netherlands special fee is not 0%; U.S. currently differs<\/td><\/tr>
59<\/td>Paid downloadable app<\/td>App itself<\/td>App Store paid-app transaction<\/td>N\/A<\/td>N\/A<\/td>Standard\/SBP commission<\/td>Free web-first app may be better for SaaS if business model supports it<\/td><\/tr>
60<\/td>Freemium app with lifetime Pro unlock<\/td>Digital non-consumable<\/td>Yes<\/strong><\/td>No substitute under default<\/td>Regional alternatives only<\/td>Standard\/SBP IAP<\/td>Non-consumable IAP + restore purchases<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

12. App design blueprints \u2014 recommended architecture by business model<\/h1>\n\n\n\n

The safest payment architecture does not begin with a payment SDK. It begins with a product classification<\/strong>, then maps payment sources into a single backend entitlement model.<\/p>\n\n\n\n

12.1 Consumer SaaS<\/h2>\n\n\n\n

Recommended: hybrid-ready entitlement architecture<\/h3>\n\n\n\n
                       +——————+
                       |   Web checkout   |
                       | Stripe\/Adyen\/etc |
                       +——–+———+
                                |
                           PSP webhook
                                |
+———–+   StoreKit   +—-v—————-+
| iOS IAP   +————->| Entitlement Service |
+———–+   server API +—-+—————-+
                                |
                        +——-v——–+
                        | Subscription DB |
                        +——-+——–+
                                |
                         authenticated API
                                |
                         +——v——+
                         |   iOS app   |
                         +————-+<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Use when:<\/strong> consumer conversion matters and you want IAP plus web acquisition.<\/p>\n\n\n\n

Key rule:<\/strong> the app’s purchase UI must be storefront-aware. The backend should not care whether an entitlement came from IAP or web; it should care about validity, plan, scope, expiration, and source.<\/p>\n\n\n\n

12.2 B2B SaaS<\/h2>\n\n\n\n
Sales \/ procurement \/ reseller \/ website
             |
        Contract or invoice
             |
        Tenant provisioner
             |
        Organization plan
             |
        Seat \/ role service
             |
   SSO \/ SCIM \/ invite \/ login
             |
           iOS app<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Safest policy posture:<\/strong> organization-level licensing, no consumer paywall, no individual self-serve purchase masquerading as \u201cB2B.\u201d<\/p>\n\n\n\n

12.3 Streaming \/ reader<\/h2>\n\n\n\n
Web acquisition -> subscription -> media entitlement
                                  |
                             identity\/account
                                  |
                           iOS reader app
                                  |
                         CDN \/ media service<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Optional account link:<\/strong> only use External Link Account Entitlement if eligible and follow its exact UI\/link requirements. Build U.S.\/EU regional purchase promotion separately rather than overloading the reader account link.<\/p>\n\n\n\n

12.4 Education<\/h2>\n\n\n\n

Split education into three transaction families:<\/p>\n\n\n\n

1:1 live tutor      -> external PSP -> live two-person session       (0% Apple)
Group live class    -> IAP\/default -> group digital entitlement      (commission)
Recorded course     -> IAP if sold in app; web\/institution model can differ
Enterprise school   -> institution contract -> student login         (0% enterprise)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Do not create one checkout rule for all \u201ceducation.\u201d<\/p>\n\n\n\n

12.5 Marketplace<\/h2>\n\n\n\n
Buyer app
   |
   +– physical\/offline item\/service -> Marketplace Payment Service
   |                                     |-> platform fee
   |                                     |-> seller payout
   |                                     +-> tax \/ refund ledger
   |
   +– digital in-app item ———–> IAP \/ regional permitted route<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The catalog should carry a commerce_type<\/strong> or equivalent classification so the UI cannot accidentally route a digital SKU through a physical-goods PSP.<\/p>\n\n\n\n

12.6 Ecommerce<\/h2>\n\n\n\n
Catalog -> cart -> shipping\/tax -> Apple Pay\/card\/PSP -> order -> fulfillment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

No StoreKit product is needed for the merchandise purchase. If the ecommerce app also sells a digital premium membership that unlocks in-app benefits, classify that membership separately rather than assuming the physical-store exemption covers it.<\/p>\n\n\n\n

12.7 Booking \/ travel<\/h2>\n\n\n\n
Inventory\/search -> quote -> booking hold -> external PSP -> reservation -> ticket\/voucher<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Maintain booking and payment state independently. Apple IAP should not be used for hotel, flight, rental-car, or comparable real-world reservations.<\/p>\n\n\n\n

12.8 Healthcare<\/h2>\n\n\n\n
Patient -> provider search -> appointment
                         |
             +———–+————+
             |                        |
       In-person visit           real-time 1:1 telehealth
             |                        |
        external PSP              external PSP
             |                        |
          provider                  provider<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Payment compliance does not replace healthcare privacy, consent, prescription, medical-device, telemedicine, or licensing requirements.<\/p>\n\n\n\n

12.9 Transportation<\/h2>\n\n\n\n
Rider -> route\/fare -> trip request -> PSP authorization
                                   -> driver\/vehicle
                                   -> trip completion
                                   -> capture\/receipt<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The fare is a real-world transportation service, so App Store digital IAP is not the right payment system.<\/p>\n\n\n\n

12.10 AI SaaS<\/h2>\n\n\n\n

AI products often mix digital credits, subscriptions, external API usage, and enterprise contracts. Treat them separately.<\/p>\n\n\n\n

                         +-> iOS individual subscription -> IAP\/default
User\/account -> plan —-+-> web individual subscription -> web entitlement
                         +-> enterprise contract ——–> org entitlement
                         +-> API-only credits ———–> developer entitlement

All sources -> normalized Entitlement Service -> iOS feature gates \/ API quotas<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Important:<\/strong> an \u201cAI token\u201d does not become non-digital merely because computation occurs on a remote server. If the credit unlocks or pays for functionality consumed through the iOS app, it is digital app value under the default rule.<\/p>\n\n\n\n

13. Hybrid payment architecture \u2014 IAP customers + website customers<\/h1>\n\n\n\n

Large SaaS products should assume multiple payment sources from day one even if they launch with one.<\/p>\n\n\n\n

13.1 Normalize entitlement, not payment-provider objects<\/h2>\n\n\n\n
                    +——————+
                    | Apple StoreKit   |
                    | transaction data |
                    +———+——–+
                              |
                       validation\/events
                              |
+————-+        +——v——-+        +—————-+
| Web billing +——->| Entitlement  |<——-+ Enterprise CRM |
| Stripe\/etc. | webhook| Service      | seats  | \/ contracts    |
+————-+        +——+——-+        +—————-+
                              |
                    +———v———-+
                    | Subscription ledger |
                    +———+———-+
                              |
                   +———-v———-+
                   | Product\/plan mapping |
                   +———-+———-+
                              |
                    +———v———+
                    | iOS + web clients |
                    +——————-+<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

13.2 Recommended subscription\/entitlement schema<\/h2>\n\n\n\n

A production system needs more than the seven obvious columns, but these are a strong core:<\/p>\n\n\n\n

Field<\/strong><\/td>Purpose<\/strong><\/td><\/tr><\/thead>
user_id<\/td>Internal immutable user\/account ID<\/td><\/tr>
organization_id<\/td>Tenant for B2B\/enterprise access<\/td><\/tr>
plan_id<\/td>Internal normalized product plan<\/td><\/tr>
payment_source<\/td>apple_iap, web_stripe, web_adyen, enterprise_invoice, etc.<\/td><\/tr>
subscription_status<\/td>active, trialing, grace, retry, paused, canceled, expired, refunded<\/td><\/tr>
entitlement_status<\/td>Whether feature access is presently granted; do not equate blindly with billing status<\/td><\/tr>
started_at<\/td>Entitlement\/service start<\/td><\/tr>
expiration_date<\/td>Current service expiration\/end<\/td><\/tr>
original_transaction_id<\/td>Stable Apple subscription lineage identifier when Apple-backed<\/td><\/tr>
transaction_id<\/td>Current Apple transaction when relevant<\/td><\/tr>
external_customer_id<\/td>PSP customer identifier<\/td><\/tr>
external_subscription_id<\/td>PSP subscription identifier<\/td><\/tr>
storefront<\/td>App Store storefront associated with Apple\/regional purchase logic<\/td><\/tr>
source_country<\/td>Billing\/tax country if separately relevant<\/td><\/tr>
agreement_version<\/td>Fee\/legal ruleset applied to the transaction<\/td><\/tr>
external_link_token<\/td>Regional external-purchase attribution token where applicable<\/td><\/tr>
latest_verified_at<\/td>Last successful authoritative verification<\/td><\/tr>
raw_event_ref<\/td>Immutable pointer to raw payment event for audit\/replay<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

13.3 Event processing principles<\/h2>\n\n\n\n

1.<\/strong> Validate server-side.<\/strong> Do not trust a local \u201cpurchase succeeded\u201d flag as durable entitlement authority.<\/p>\n\n\n\n

2.<\/strong> Store raw immutable events.<\/strong> Preserve App Store Server Notifications\/transaction data and PSP webhook payload references before deriving state.<\/p>\n\n\n\n

3.<\/strong> Make processing idempotent.<\/strong> A retry must not grant two subscriptions or double-count revenue.<\/p>\n\n\n\n

4.<\/strong> Separate billing status from entitlement status.<\/strong> Billing Grace Period is a classic example: payment may be in recovery while access remains valid.<\/p>\n\n\n\n

5.<\/strong> Map products to internal plans.<\/strong> Apple product IDs and Stripe Price IDs are vendor identifiers, not your domain model.<\/p>\n\n\n\n

6.<\/strong> Reconcile periodically.<\/strong> Compare the entitlement ledger against authoritative Apple\/PSP states and flag drift.<\/p>\n\n\n\n

7.<\/strong> Track refunds\/revocations.<\/strong> A refund, chargeback, Family Sharing change, or revoked transaction can change access.<\/p>\n\n\n\n

8.<\/strong> Persist storefront\/fee rules.<\/strong> Regional compliance\/reporting cannot be reconstructed reliably if you discard the source storefront and agreement version.<\/p>\n\n\n\n

13.4 Purchase-source normalization example<\/h2>\n\n\n\n
Apple product com.example.pro.monthly
        -> internal plan PRO_MONTHLY

Stripe price price_web_pro_monthly
        -> internal plan PRO_MONTHLY

Enterprise contract SKU ENT_PRO_SEAT
        -> internal plan PRO_MONTHLY + organization scope<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The iOS app asks the backend: \u201cWhat can this account use?\u201d<\/strong> not \u201cDid this user pay Apple?\u201d<\/strong><\/p>\n\n\n\n

14. Subscription master section<\/h1>\n\n\n\n

Auto-renewable subscriptions are not just recurring charges. They are a StoreKit lifecycle with pricing, renewal, grace, retry, offer eligibility, plan changes, cancellation, refund, and server-event implications.<\/p>\n\n\n\n

14.1 Monthly and annual subscriptions<\/h2>\n\n\n\n

Both can be auto-renewable IAP products. Apple’s subscription guidelines require ongoing value, and an auto-renewable subscription period must be at least seven days. SaaS, cloud support, media libraries, and substantive ongoing updates are among Apple’s examples of appropriate subscription value. Guideline 3.1.2<\/a><\/p>\n\n\n\n

14.2 Introductory offers and free trials<\/h2>\n\n\n\n

Apple supports introductory offers such as:<\/p>\n\n\n\n

\u2022 free trial;<\/p>\n\n\n\n

\u2022 pay as you go;<\/p>\n\n\n\n

\u2022 pay up front.<\/p>\n\n\n\n

Eligibility is tied to the subscription group and Apple’s offer rules. The client should request StoreKit eligibility rather than guess from a local \u201chas_trialed\u201d flag. Set up introductory offers<\/a><\/p>\n\n\n\n

14.3 Promotional offers<\/h2>\n\n\n\n

Promotional offers can be used for existing or previously subscribed customers and can provide free or discounted subscription periods subject to Apple’s current limits and eligibility mechanics. Promotional offers<\/a><\/p>\n\n\n\n

14.4 Offer codes and win-back offers<\/h2>\n\n\n\n

Offer codes can target new, active, or expired subscribers, and win-back offers can target eligible lapsed subscribers. These are lifecycle tools; they do not change the underlying rule that the subscription is an IAP subscription when sold through IAP. Offer codes<\/a> and win-back offers<\/a><\/p>\n\n\n\n

14.5 Upgrade, downgrade, and crossgrade<\/h2>\n\n\n\n

Use a single subscription group for mutually exclusive service levels. The important user-experience behavior is:<\/p>\n\n\n\n

\u2022 Upgrade:<\/strong> normally effective immediately; Apple manages proration\/refund behavior for the previous service level.<\/p>\n\n\n\n

\u2022 Downgrade:<\/strong> normally effective at the next renewal date.<\/p>\n\n\n\n

\u2022 Crossgrade:<\/strong> timing depends on whether the products are the same subscription level\/duration and Apple’s rules.<\/p>\n\n\n\n

Your backend should process authoritative transaction changes instead of manually calculating a \u201cnew expiry\u201d from the button tap. Subscription level changes<\/a><\/p>\n\n\n\n

14.6 Renewal and cancellation<\/h2>\n\n\n\n

Cancellation generally means \u201cdo not renew at the next billing boundary,\u201d not immediate loss of already-paid service. Persist the current entitlement expiration separately from the auto-renew preference.<\/p>\n\n\n\n

14.7 Billing retry and Billing Grace Period<\/h2>\n\n\n\n

If a renewal cannot be collected, the subscription can enter billing retry. Apple also supports Billing Grace Period<\/strong>, during which qualifying subscribers can retain paid-service access while Apple attempts recovery. Apple lets developers configure grace behavior and duration in App Store Connect. Billing Grace Period<\/a><\/p>\n\n\n\n

Backend rule:<\/p>\n\n\n\n

billing_status = retry\/grace
entitlement_status = active   <- can still be true during configured grace<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Do not lock out a user solely because the PSP\/IAP \u201clatest payment succeeded\u201d field is false.<\/p>\n\n\n\n

14.8 Family Sharing<\/h2>\n\n\n\n

Eligible auto-renewable subscriptions and non-consumable IAP can support Family Sharing. Apple permits sharing with up to five additional family members when enabled. Model family access as a derived entitlement; do not duplicate the original purchaser’s transaction as a new purchase for each member. Family Sharing for IAP<\/a><\/p>\n\n\n\n

14.9 Restore Purchases<\/h2>\n\n\n\n

Apple requires a restore mechanism for restorable purchases. A production app should expose a clear Restore Purchases<\/strong> action when applicable, verify the authoritative StoreKit state, and rehydrate the backend entitlement. Guideline 3.1.1<\/a><\/p>\n\n\n\n

14.10 Which subscription events influence commission?<\/h2>\n\n\n\n

Under the standard worldwide model, the key fee dimension is cumulative paid service for auto-renewing subscriptions. Apple’s reporting distinguishes the \u201cRate Before One Year\u201d from \u201cRate After One Year.\u201d Small Business Program participation changes the proceeds rate from the beginning while eligible.<\/p>\n\n\n\n

Regional programs add other clocks. Examples:<\/p>\n\n\n\n

\u2022 Japan\/Brazil actionable-link fee: relevant sales within seven days after link tap.<\/p>\n\n\n\n

\u2022 Current EU pre-October terms: acquisition\/store-services fee windows can depend on initial install and latest install\/update\/reinstall.<\/p>\n\n\n\n

\u2022 New EU terms beginning October 1, 2026: different simplified commissions replace the pre-October layered model.<\/p>\n\n\n\n

Your finance model therefore needs transaction date + storefront + agreement version + purchase source + attribution metadata<\/strong>, not merely plan and amount.<\/p>\n\n\n\n

15. Free app vs paid app vs freemium \u2014 how Apple treats each<\/h1>\n\n\n\n

Free download<\/h2>\n\n\n\n

A free download itself has no App Store sales commission. But a \u201cfree app\u201d can still generate commission when it sells digital IAP later. Free does not mean commission-free.<\/p>\n\n\n\n

Paid download<\/h2>\n\n\n\n

The purchase price of a paid app is an App Store transaction and is subject to the applicable commission\/program terms.<\/p>\n\n\n\n

Freemium<\/h2>\n\n\n\n

The app downloads free; optional digital upgrades are sold using IAP under default rules. This is a common model for consumables, non-consumables, and subscriptions.<\/p>\n\n\n\n

Paid feature \/ lifetime purchase<\/h2>\n\n\n\n

A permanent digital \u201cPro unlock\u201d is normally a non-consumable IAP<\/strong> when sold in the app. It must support appropriate restoration.<\/p>\n\n\n\n

Subscription<\/h2>\n\n\n\n

Recurring digital access generally uses auto-renewable IAP when sold in the app, with the subscription proceeds rules discussed above.<\/p>\n\n\n\n

Free trial<\/h2>\n\n\n\n

A free trial is typically an introductory offer on an auto-renewable subscription. A free period does not itself create commission, but subsequent paid renewal does.<\/p>\n\n\n\n

Consumable<\/h2>\n\n\n\n

Used\/depleted and repurchasable, such as game currency or digital credits. Credits purchased via IAP may not expire under Apple’s guideline.<\/p>\n\n\n\n

Non-consumable<\/h2>\n\n\n\n

Bought once and does not expire, such as a permanent feature unlock.<\/p>\n\n\n\n

Auto-renewing subscription<\/h2>\n\n\n\n

Renews automatically until cancelled; ongoing value, subscription group design, and subscription lifecycle rules apply.<\/p>\n\n\n\n

Non-renewing subscription<\/h2>\n\n\n\n

Time-limited access that requires a new purchase to extend. The app\/developer has more responsibility for duration\/renewal UX because it does not auto-renew.<\/p>\n\n\n\n

16. App Store Review: what reviewers will inspect<\/h1>\n\n\n\n

App Review is not only a static-code check. Reviewers need to understand the business model and may test the real purchase\/account experience. Apple’s Guidelines say a non-obvious business model should be explained in metadata and App Review notes, and review submissions should provide full access, a valid demo account\/demo mode where needed, and a live backend. App Review Guidelines<\/a><\/p>\n\n\n\n

16.1 Purchase and Subscribe buttons<\/h2>\n\n\n\n

Reviewers can ask:<\/p>\n\n\n\n

\u2022 What does the button unlock?<\/p>\n\n\n\n

\u2022 Is the value digital or physical?<\/p>\n\n\n\n

\u2022 If digital and sold in-app, why is this not IAP?<\/p>\n\n\n\n

\u2022 Is this a qualifying enterprise\/P2P\/reader\/companion\/regional flow?<\/p>\n\n\n\n

\u2022 Is the IAP item submitted, visible, functional, and testable?<\/p>\n\n\n\n

Bad design:<\/strong> \u201cUpgrade Pro \u2014 $9.99\u201d opens an unapproved Stripe WebView for a digital feature under a default storefront.<\/p>\n\n\n\n

Compliant design:<\/strong> \u201cUpgrade Pro\u201d uses StoreKit IAP for the in-app digital plan, or a storefront-specific approved external flow where applicable.<\/p>\n\n\n\n

16.2 External links and \u201cBuy on Website\u201d CTAs<\/h2>\n\n\n\n

Reviewers can inspect:<\/p>\n\n\n\n

\u2022 whether the storefront permits it;<\/p>\n\n\n\n

\u2022 whether an entitlement is required;<\/p>\n\n\n\n

\u2022 whether the app uses the required StoreKit external-purchase APIs;<\/p>\n\n\n\n

\u2022 whether link text and price language follow the program;<\/p>\n\n\n\n

\u2022 whether browser vs WebView rules are satisfied;<\/p>\n\n\n\n

\u2022 whether disclosures are shown;<\/p>\n\n\n\n

\u2022 whether regional UI appears only in valid storefronts.<\/p>\n\n\n\n

Do not ship the U.S. CTA globally unless the global storefront logic is independently compliant.<\/p>\n\n\n\n

16.3 Pricing text<\/h2>\n\n\n\n

A displayed website price can be treated as communication\/promotion of an outside offer. Reader-account-link rules, default storefront rules, and regional external-purchase programs differ. The safest implementation is a policy engine that decides whether price text is legal for this storefront and program<\/strong>, not a hard-coded marketing label.<\/p>\n\n\n\n

16.4 QR codes<\/h2>\n\n\n\n

Guideline 3.1.1 expressly rejects proprietary mechanisms such as QR codes as substitutes for required IAP to unlock app functionality. A QR code is not a compliance loophole.<\/p>\n\n\n\n

16.5 WebViews and browser redirects<\/h2>\n\n\n\n

The rendering technology does not decide whether a transaction is IAP-eligible. Specific programs also impose UI restrictions:<\/p>\n\n\n\n

\u2022 Reader External Link Account Entitlement: default browser, not WebView.<\/p>\n\n\n\n

\u2022 South Korea alternative in-app payment: native experience; not a WebView.<\/p>\n\n\n\n

\u2022 EU\/Japan\/Brazil programs have their own current StoreKit and user-disclosure requirements.<\/p>\n\n\n\n

16.6 Hidden checkout \/ remote configuration<\/h2>\n\n\n\n

Apple prohibits hidden, dormant, or undocumented functionality and expects material product behavior to be disclosed in Review Notes. A remote config that changes prices or product presentation can be normal; a remote config whose purpose is to hide a prohibited payment flow from review is not.<\/p>\n\n\n\n

BAD DESIGN<\/h3>\n\n\n\n
if app_review_ip_range:
    show IAP
else:
    activate secret Stripe checkout<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

COMPLIANT DESIGN<\/h3>\n\n\n\n
storefront = StoreKit storefront
policy = server_policy(storefront, app_category, approved_entitlements)
render only the payment routes Apple currently permits for that storefront
and document the behavior in App Review notes.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

16.7 Account creation and login-only apps<\/h2>\n\n\n\n

An app may be login-only when the business model legitimately expects users to arrive with existing accounts, but reviewers still need test credentials or a review mode. If account creation is available in the app, Apple’s account-deletion rule applies: apps that support account creation must let users initiate account deletion from within the app. Offering account deletion in your app<\/a><\/p>\n\n\n\n

16.8 Restore Purchases<\/h2>\n\n\n\n

If the app has restorable IAP, provide a clear restore path and make it actually restore the backend entitlement, not merely call StoreKit and show \u201cDone.\u201d<\/p>\n\n\n\n

16.9 Sign in with Apple \/ login-service rule<\/h2>\n\n\n\n

If the app uses a third-party or social login service for the user’s primary account, Guideline 4.8 requires an equivalent login option with Apple’s specified privacy characteristics unless an exception applies, including certain enterprise\/education\/business and client-for-specific-third-party-service cases. Evaluate login compliance separately from payment compliance. Guideline 4.8<\/a><\/p>\n\n\n\n

16.10 Metadata and screenshots<\/h2>\n\n\n\n

Do not assume only executable UI is reviewed. External purchase messaging in screenshots, promotional copy, review notes, and metadata can be policy-relevant. The U.S. injunction also addresses metadata in the anti-steering context, while Apple’s current Guidelines remain the operational submission reference.<\/p>\n\n\n\n

16.11 Region-dependent payment UI<\/h2>\n\n\n\n

Recommended state machine:<\/p>\n\n\n\n

startup
 -> fetch StoreKit storefront
 -> fetch signed server commerce policy for app version + storefront
 -> confirm required entitlement capability is compiled\/enabled
 -> render allowed payment choices
 -> log policy version for support\/audit<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Never determine a special payment route solely from locale language, device region, SIM, VPN, or IP address.<\/p>\n\n\n\n

16.12 Common rejection reasons<\/h2>\n\n\n\n

1.<\/strong> Selling a digital feature through Stripe\/PayPal\/etc. instead of required IAP.<\/p>\n\n\n\n

2.<\/strong> A \u201cGo to website to subscribe\u201d CTA in a storefront\/program where it is not allowed.<\/p>\n\n\n\n

3.<\/strong> Misusing reader-app status for an app whose primary function is not eligible media.<\/p>\n\n\n\n

4.<\/strong> Calling a one-to-many digital class \u201cperson-to-person.\u201d<\/p>\n\n\n\n

5.<\/strong> Calling a self-serve consumer plan \u201centerprise.\u201d<\/p>\n\n\n\n

6.<\/strong> External-link entitlement implementation that violates link formatting\/destination rules.<\/p>\n\n\n\n

7.<\/strong> South Korea external purchase in a WebView or mixed with IAP in the same entitlement app.<\/p>\n\n\n\n

8.<\/strong> Missing required regional disclosure sheets\/APIs.<\/p>\n\n\n\n

9.<\/strong> Hidden or remotely activated payment behavior.<\/p>\n\n\n\n

10.<\/strong> Incomplete IAP metadata or purchase flow not testable by reviewer.<\/p>\n\n\n\n

11.<\/strong> Missing Restore Purchases for restorable products.<\/p>\n\n\n\n

12.<\/strong> Account creation without in-app account deletion.<\/p>\n\n\n\n

13.<\/strong> Review account does not work or backend is offline.<\/p>\n\n\n\n

14.<\/strong> Business model is unclear and not explained in Review Notes.<\/p>\n\n\n\n

15.<\/strong> Digital product is disguised as physical\/offline value.<\/p>\n\n\n\n

17. Economic comparison \u2014 what the commission actually costs<\/h1>\n\n\n\n

A payment strategy is a unit-economics decision, not only a policy exercise. IAP can improve conversion because users have a stored payment method, familiar Apple purchase sheet, trust, subscription management, family\/Ask-to-Buy ecosystem features, tax\/commerce support, and fewer checkout steps. External billing can reduce Apple fees but adds PSP, billing, fraud, tax, refunds, customer support, and potentially lower conversion.<\/p>\n\n\n\n

17.1 Illustrative annual revenue table<\/h2>\n\n\n\n

Assumptions solely for comparison:<\/p>\n\n\n\n

\u2022 digital revenue before fees: values shown below;<\/p>\n\n\n\n

\u2022 Apple 30% and 15% cases ignore tax to isolate commission;<\/p>\n\n\n\n

\u2022 external-card example uses 2.9% + USD 0.30<\/strong> per transaction, assuming an average transaction of USD 100, i.e. approximately 3.2% effective processing<\/strong>;<\/p>\n\n\n\n

\u2022 does not include Stripe Billing, Tax, Radar, international-card, FX, chargeback, or other optional\/additional fees;<\/p>\n\n\n\n

\u2022 \u201cweb-first 0% Apple\u201d means a business model legitimately outside Apple commission, not a prohibited bypass.<\/p>\n\n\n\n

Stripe U.S. card pricing<\/a><\/p>\n\n\n\n

Annual digital revenue<\/strong><\/td>Apple 30%<\/strong><\/td>Apple 15%<\/strong><\/td>External processor ~3.2%<\/strong><\/td>Web-first: Apple commission<\/strong><\/td>Approx. net after processor only<\/strong><\/td><\/tr><\/thead>
$10,000<\/td>$3,000<\/td>$1,500<\/td>$320<\/td>$0<\/td>$9,680<\/td><\/tr>
$100,000<\/td>$30,000<\/td>$15,000<\/td>$3,200<\/td>$0<\/td>$96,800<\/td><\/tr>
$500,000<\/td>$150,000<\/td>$75,000<\/td>$16,000<\/td>$0<\/td>$484,000<\/td><\/tr>
$1,000,000<\/td>$300,000<\/td>$150,000<\/td>$32,000<\/td>$0<\/td>$968,000<\/td><\/tr>
$5,000,000<\/td>$1,500,000<\/td>$750,000<\/td>$160,000<\/td>$0<\/td>$4,840,000<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

These numbers do not prove external billing is better<\/strong>. A 30% commission with meaningfully higher conversion\/LTV can beat a 3.2% processor with a checkout cliff. Test economics, not ideology.<\/p>\n\n\n\n

17.2 Japan example: external payment is cheaper than IAP but not 0%<\/h2>\n\n\n\n

Ignoring tax and PSP cost on a $100 standard digital purchase:<\/p>\n\n\n\n

\u2022 IAP: 21% App Store commission + 5% Apple processing = $26 Apple fees<\/strong>.<\/p>\n\n\n\n

\u2022 Alternative in-app PSP: $21 Apple commission<\/strong> + PSP fee.<\/p>\n\n\n\n

\u2022 Actionable external link within Apple’s relevant 7-day attribution window: $15 Apple store-services commission<\/strong> + PSP fee.<\/p>\n\n\n\n

17.3 South Korea example<\/h2>\n\n\n\n

A $100 price paid through the sanctioned alternative in-app route is subject to Apple’s 26% commission<\/strong>, with the official basis stated gross of VAT; merchant PSP\/tax economics sit on top according to the actual transaction. That may or may not be economically preferable to IAP depending on the full fee stack and conversion.<\/p>\n\n\n\n

17.4 Current U.S. link-out example<\/h2>\n\n\n\n

As of September 5, 2026, the court-approved Apple linked-out commission is 0% because no future fee has yet been approved<\/strong>. A web processor still charges its own fees. Because Apple has proposed a future schedule and the Supreme Court litigation continues, model a contingency rather than assuming permanent zero.<\/p>\n\n\n\n

18. Founder decision framework<\/h1>\n\n\n\n

Before choosing IAP, web-only, or hybrid, answer these ten questions.<\/p>\n\n\n\n

1.<\/strong> Is the product digital or physical?<\/strong> If physical\/offline, stop trying to use IAP.<\/p>\n\n\n\n

2.<\/strong> Where is the value consumed?<\/strong> A remote server can still provide digital in-app value; location of CPU execution is not the test.<\/p>\n\n\n\n

3.<\/strong> B2C or B2B?<\/strong> Enterprise-only organization sales have a specific exception; individual consumer sales do not inherit it.<\/p>\n\n\n\n

4.<\/strong> Is the app truly a reader?<\/strong> Primary functionality must fit Apple’s reader media categories.<\/p>\n\n\n\n

5.<\/strong> Is it truly a free stand-alone companion?<\/strong> No purchasing and, under the default companion rule, no external-purchase CTA.<\/p>\n\n\n\n

6.<\/strong> Is the service exactly one-to-one in real time?<\/strong> If group, the P2P exception does not apply.<\/p>\n\n\n\n

7.<\/strong> Is the user already a customer?<\/strong> Existing account access is different from acquiring the customer inside the iOS app.<\/p>\n\n\n\n

8.<\/strong> Do you need iOS as an acquisition channel?<\/strong> If yes, IAP conversion may be worth the commission.<\/p>\n\n\n\n

9.<\/strong> Which storefront applies?<\/strong> U.S., EU, Japan, Brazil, Korea, Netherlands dating, and default rules differ.<\/p>\n\n\n\n

10.<\/strong> Is conversion more valuable than avoiding commission?<\/strong> Measure checkout completion, refund\/support costs, LTV, churn, and cross-platform retention.<\/p>\n\n\n\n

Decision scorecard<\/h3>\n\n\n\n
Factor<\/strong><\/td>IAP-first advantage<\/strong><\/td>Web-first advantage<\/strong><\/td><\/tr><\/thead>
Checkout friction<\/td>Strong<\/td>Usually weaker unless customer already on web<\/td><\/tr>
Stored payment trust<\/td>Strong<\/td>PSP\/brand dependent<\/td><\/tr>
Global policy simplicity<\/td>Stronger for digital in-app sales<\/td>More category\/storefront analysis required<\/td><\/tr>
Apple commission<\/td>Higher<\/td>Can be 0% in legitimate models; regional links may still have Apple fees<\/td><\/tr>
Merchant tax burden<\/td>Apple provides substantial commerce\/tax handling for IAP<\/td>Developer\/merchant generally owns more tax obligations<\/td><\/tr>
Refund\/support<\/td>Apple ecosystem handles IAP workflows<\/td>Developer\/PSP handles more<\/td><\/tr>
Cross-platform billing control<\/td>Lower<\/td>Strong<\/td><\/tr>
Pricing flexibility \/ bundles<\/td>StoreKit constraints<\/td>Strong web control<\/td><\/tr>
Enterprise invoicing<\/td>Poor fit<\/td>Excellent<\/td><\/tr>
App Review risk<\/td>Low when correctly implemented<\/td>Low only when classification\/linking is correct<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

19. Five architecture choices<\/h1>\n\n\n\n

Architecture A \u2014 Maximum convenience: IAP-first<\/h2>\n\n\n\n
iOS -> StoreKit -> App Store -> server validation -> entitlement<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Advantages:<\/strong> highest native convenience, trusted one-tap experience, Apple commerce infrastructure, simpler default global digital-sales compliance.<\/p>\n\n\n\n

Disadvantages:<\/strong> Apple commission; less direct billing ownership; platform subscription constraints.<\/p>\n\n\n\n

Apple fees:<\/strong> standard\/regional IAP terms.<\/p>\n\n\n\n

Gateway fees:<\/strong> Apple processing is embedded\/decomposed according to the applicable Apple fee model; no Stripe card fee for the IAP transaction.<\/p>\n\n\n\n

UX\/conversion:<\/strong> usually strongest.<\/p>\n\n\n\n

Complexity:<\/strong> medium.<\/p>\n\n\n\n

Review risk:<\/strong> low if StoreKit\/subscription UX is correct.<\/p>\n\n\n\n

Architecture B \u2014 Lowest Apple commission: web-first<\/h2>\n\n\n\n
Web acquisition -> PSP -> entitlement -> iOS login<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Advantages:<\/strong> can reach 0% Apple commission in legitimate reader\/companion\/enterprise\/multiplatform\/other permitted models; direct billing relationship.<\/p>\n\n\n\n

Disadvantages:<\/strong> web acquisition burden, PSP\/tax\/support, possible lower conversion, in-app CTA restrictions outside special storefronts.<\/p>\n\n\n\n

Apple fees:<\/strong> 0% only where the architecture actually falls outside commission; regional link programs may impose fees.<\/p>\n\n\n\n

Gateway fees:<\/strong> PSP\/card\/billing fees.<\/p>\n\n\n\n

Complexity:<\/strong> medium-high.<\/p>\n\n\n\n

Review risk:<\/strong> low when the category is clean; high if the design is actually a disguised in-app digital sale.<\/p>\n\n\n\n

Architecture C \u2014 Hybrid: web + IAP<\/h2>\n\n\n\n
IAP ——-> entitlement <——- web billing<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Advantages:<\/strong> native iOS conversion plus direct web acquisition; flexible global strategy.<\/p>\n\n\n\n

Disadvantages:<\/strong> two billing lifecycles, reconciliation, price parity\/merchandising complexity, region-specific link UX.<\/p>\n\n\n\n

Apple fees:<\/strong> Apple commission only for applicable Apple\/region-attributed transactions.<\/p>\n\n\n\n

Gateway fees:<\/strong> both Apple and external economics depending source.<\/p>\n\n\n\n

Complexity:<\/strong> high, but best long-term architecture for many consumer SaaS products.<\/p>\n\n\n\n

Review risk:<\/strong> medium unless payment UI is rigorously storefront-aware.<\/p>\n\n\n\n

Architecture D \u2014 B2B enterprise: contract\/invoice + login<\/h2>\n\n\n\n
Sales -> MSA\/order form\/invoice -> tenant -> seats -> SSO -> iOS<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Advantages:<\/strong> 0% App Store commission on qualifying direct organization sale; supports procurement, annual contracts, invoicing, negotiated pricing.<\/p>\n\n\n\n

Disadvantages:<\/strong> sales\/provisioning systems required; not a consumer self-serve loophole.<\/p>\n\n\n\n

Gateway fees:<\/strong> bank\/ACH\/card\/invoice platform as negotiated.<\/p>\n\n\n\n

Complexity:<\/strong> medium-high backend, simple app.<\/p>\n\n\n\n

Review risk:<\/strong> low if the enterprise-only model is obvious and documented.<\/p>\n\n\n\n

Architecture E \u2014 Physical services: native external checkout<\/h2>\n\n\n\n
iOS -> cart\/booking -> Apple Pay\/card\/PSP -> fulfillment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Advantages:<\/strong> correct Apple model; no App Store commission.<\/p>\n\n\n\n

Disadvantages:<\/strong> merchant owns payment\/tax\/refund\/fraud stack.<\/p>\n\n\n\n

Apple fees:<\/strong> 0% App Store commission on the physical\/offline transaction.<\/p>\n\n\n\n

Gateway fees:<\/strong> PSP\/acquirer\/card-network costs.<\/p>\n\n\n\n

UX:<\/strong> Apple Pay can provide excellent native conversion.<\/p>\n\n\n\n

Review risk:<\/strong> low if the product is genuinely physical\/offline.<\/p>\n\n\n\n

20. Common myths \u2014 25 corrections<\/h1>\n\n\n\n

1.<\/strong> Myth: \u201cApple takes 30% of every app payment.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Apple commission depends on digital vs physical value, storefront, program, entitlement, subscription age, and transaction path. Physical\/offline transactions are generally outside IAP.<\/p>\n\n\n\n

2.<\/strong> Myth: \u201cIf I use Stripe, Apple cannot charge me.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> A PSP does not change product classification. Some regional alternative-payment programs still impose Apple commission.<\/p>\n\n\n\n

3.<\/strong> Myth: \u201cApple Pay means Apple takes 30%.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Apple Pay is a payment method; IAP is App Store digital commerce.<\/p>\n\n\n\n

4.<\/strong> Myth: \u201cA free app never pays Apple commission.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Free download can later sell commissionable digital IAP.<\/p>\n\n\n\n

5.<\/strong> Myth: \u201cIf my website processes payment, Apple can never charge a fee.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> In-app steering to a website can trigger regional Apple fees\/reporting. Independent web acquisition is a different flow.<\/p>\n\n\n\n

6.<\/strong> Myth: \u201cAll subscriptions must use IAP.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Enterprise, reader, companion, web-first existing-account, P2P, and regional rules can permit non-IAP models. In-app consumer digital subscription sales normally use IAP under default rules.<\/p>\n\n\n\n

7.<\/strong> Myth: \u201cApple takes commission from Uber rides.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Real-world transportation is a service consumed outside the app and uses non-IAP payment.<\/p>\n\n\n\n

8.<\/strong> Myth: \u201cApple takes commission from Amazon physical purchases.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Physical ecommerce checkout is outside IAP.<\/p>\n\n\n\n

9.<\/strong> Myth: \u201cB2B SaaS always needs IAP.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Direct organization\/group licensing for employees\/students has an enterprise-services exception.<\/p>\n\n\n\n

10.<\/strong> Myth: \u201cCalling my consumer plan B2B makes it enterprise.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Apple explicitly distinguishes consumer\/single-user\/family sales from direct organization\/group sales.<\/p>\n\n\n\n

11.<\/strong> Myth: \u201cReader apps can sell anything externally.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Reader status is limited to primary media categories and its account-link entitlement is tightly constrained.<\/p>\n\n\n\n

12.<\/strong> Myth: \u201cSmall Business Program means all my payments are 15%.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> It reduces eligible paid-app\/IAP commission; it does not turn physical PSP fees or every regional fee into 15%.<\/p>\n\n\n\n

13.<\/strong> Myth: \u201cEvery subscription automatically drops to 15% after one calendar year.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Apple’s standard rule is based on a subscriber accumulating one year of paid service, with detailed continuity rules.<\/p>\n\n\n\n

14.<\/strong> Myth: \u201cA WebView makes Stripe checkout compliant.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Rendering checkout in HTML does not change what is being sold; some entitlements expressly disallow WebView.<\/p>\n\n\n\n

15.<\/strong> Myth: \u201cA QR code can bypass IAP.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Guideline 3.1.1 expressly rejects proprietary unlock mechanisms including QR codes as substitutes for required IAP.<\/p>\n\n\n\n

16.<\/strong> Myth: \u201cAI credits are a physical compute service because servers do the work.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Credits paying for in-app digital functionality are digital app value under the default classification.<\/p>\n\n\n\n

17.<\/strong> Myth: \u201cOne teacher + many students is person-to-person.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Apple states one-to-few and one-to-many real-time services must use IAP under default rules.<\/p>\n\n\n\n

18.<\/strong> Myth: \u201cAll marketplaces avoid IAP.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Physical\/offline marketplaces do; digital in-app marketplaces generally do not.<\/p>\n\n\n\n

19.<\/strong> Myth: \u201cAdvertising is always external-payment eligible.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Sole-purpose management of ads shown outside the app is; buying a boost displayed in the same app uses IAP.<\/p>\n\n\n\n

20.<\/strong> Myth: \u201cSouth Korea alternative payment means 0% Apple.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Apple currently charges 26% on the sanctioned alternative in-app route.<\/p>\n\n\n\n

21.<\/strong> Myth: \u201cJapan external checkout is 0% Apple.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Current Japan regional terms specify Apple commissions on alternative in-app payments and actionable external links.<\/p>\n\n\n\n

22.<\/strong> Myth: \u201cThe EU has one permanent 2026 fee schedule.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> There is a major transition on October 1, 2026; pre-October and post-October models must be separated.<\/p>\n\n\n\n

23.<\/strong> Myth: \u201cThe U.S. 0% link-out status is guaranteed forever.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> It is the current result of active federal litigation pending a court-approved fee and Supreme Court proceedings.<\/p>\n\n\n\n

24.<\/strong> Myth: \u201cIf App Review approved it once, the payment design is permanently safe.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> Policy, agreements, laws, storefront rules, and app behavior change. Approval is not a perpetual exemption.<\/p>\n\n\n\n

25.<\/strong> Myth: \u201cThe best strategy is always to avoid Apple commission.\u201d<\/strong><\/p>\n\n\n\n

Correction:<\/strong> IAP can increase conversion and reduce merchant billing\/tax\/support burden. Optimize lifetime economics, not fee percentage alone.<\/p>\n\n\n\n

21. Developer FAQ \u2014 60 questions<\/h1>\n\n\n\n

1. Does Apple take 30% from Stripe?<\/h2>\n\n\n\n

Not simply because Stripe is used. For physical\/offline transactions, Apple App Store commission is generally 0%. For digital app value, Stripe cannot replace required IAP under default rules; in regional alternative-payment programs Apple may still charge its own commission in addition to Stripe’s fee.<\/p>\n\n\n\n

2. Can I put Stripe Checkout in a WebView?<\/h2>\n\n\n\n

Not as a generic workaround for required IAP. The product classification still controls, and some programs expressly forbid WebView for the external payment flow.<\/p>\n\n\n\n

3. Can I open Safari for payment?<\/h2>\n\n\n\n

For physical\/offline goods, yes as part of an ordinary external checkout. For digital goods, whether the app may steer to Safari depends on storefront\/category\/entitlement. Reader account links must open the default browser; U.S. storefront rules currently permit external CTAs without the former entitlement.<\/p>\n\n\n\n

4. Can I mention my website?<\/h2>\n\n\n\n

Yes in ordinary non-purchase contexts, but language that communicates or promotes an external digital purchase can be payment-policy relevant. Reader entitlement and regional programs have specific wording rules.<\/p>\n\n\n\n

5. Can I show website prices in my iOS app?<\/h2>\n\n\n\n

It depends on storefront and entitlement. Do not globally show external digital prices based on U.S. rules. The reader account-link entitlement specifically restricts price language attached to that link, while some regional purchase-promotion programs allow price communication under their terms.<\/p>\n\n\n\n

6. Can users create accounts in the app?<\/h2>\n\n\n\n

Generally yes. Reader apps may offer account creation for free tiers. If your app supports account creation, Apple requires users to be able to initiate account deletion in the app.<\/p>\n\n\n\n

7. Can users log in to accounts purchased elsewhere?<\/h2>\n\n\n\n

Often yes under reader, multiplatform, enterprise, companion, or other valid existing-customer models. The exact exception must fit the product.<\/p>\n\n\n\n

8. Can I disable signup on iOS?<\/h2>\n\n\n\n

Yes when a login-only experience is legitimate, but App Review still needs access\/demo credentials and the business model must make sense rather than being a disguised attempt to force prohibited payment steering.<\/p>\n\n\n\n

9. Can I make the app login-only?<\/h2>\n\n\n\n

Yes for many enterprise, reader, companion, and existing-customer applications. Explain the model clearly in App Review notes and provide a working test account.<\/p>\n\n\n\n

10. Can users subscribe on Android and use iPhone?<\/h2>\n\n\n\n

Multiplatform services can allow access to content\/subscriptions\/features acquired on other platforms. If the app also sells the same digital service on iOS under default rules, that in-app sale uses IAP.<\/p>\n\n\n\n

11. Can users subscribe on Windows and use iPhone?<\/h2>\n\n\n\n

Yes under the same existing-entitlement\/multiplatform logic when the app\/business model fits Apple’s rules.<\/p>\n\n\n\n

12. Can a company buy licenses for employees?<\/h2>\n\n\n\n

Yes. Apple’s enterprise-services exception allows direct organization\/group purchases for employees\/students and subsequent app access. Consumer\/single-user\/family sales are different.<\/p>\n\n\n\n

13. Can I invoice enterprise customers?<\/h2>\n\n\n\n

Yes for qualifying B2B\/enterprise contracts. Provision tenant\/seat entitlements and let users log in.<\/p>\n\n\n\n

14. Can I sell API credits?<\/h2>\n\n\n\n

If the credits are truly for an external developer API and the iOS app is a management companion, web billing can be appropriate. If those credits pay for in-app digital functionality, they are normally IAP digital consumables under default rules.<\/p>\n\n\n\n

15. Can I sell AI tokens or credits?<\/h2>\n\n\n\n

If consumed to run AI features in the iOS app, normally use IAP for the in-app sale. Website or enterprise purchase can be recognized where a valid web-first\/multiplatform\/enterprise model applies.<\/p>\n\n\n\n

16. Can I sell cloud compute credits?<\/h2>\n\n\n\n

Classify what they unlock. External infrastructure credits sold through a web developer portal can fit a companion model; credits bought in the app to unlock in-app digital functionality are IAP territory.<\/p>\n\n\n\n

17. Can I sell storage?<\/h2>\n\n\n\n

Cloud storage is one of Apple’s explicit free-stand-alone-companion examples. A web-paid storage service can have a free iOS companion with no in-app purchasing\/CTA under that rule. If you sell the storage upgrade in the iOS app, use IAP under default rules.<\/p>\n\n\n\n

18. Can I sell a Zoom-like subscription externally?<\/h2>\n\n\n\n

A web-first paid service with an iOS companion\/multiplatform client can be legitimate. But a consumer subscription sold in the iOS app is a digital SaaS subscription and normally uses IAP.<\/p>\n\n\n\n

19. Can I charge for one-to-one tutoring?<\/h2>\n\n\n\n

Yes through non-IAP payment when it is a real-time service between two individuals. Group tutoring does not qualify under that exception.<\/p>\n\n\n\n

20. Can I sell recorded courses?<\/h2>\n\n\n\n

If sold in the app for consumption in the app, they are digital content and normally use IAP. Institutional sales or valid web-first content models can differ.<\/p>\n\n\n\n

21. Can I charge for live group classes?<\/h2>\n\n\n\n

Under Apple’s default P2P rule, one-to-few and one-to-many real-time services must use IAP.<\/p>\n\n\n\n

22. Can I charge for gym memberships?<\/h2>\n\n\n\n

A membership for a physical gym\/service consumed outside the app can use Apple Pay\/cards\/PSP and has no App Store commission on the transaction. A digital-only workout subscription sold in the app is different.<\/p>\n\n\n\n

23. Can I accept donations?<\/h2>\n\n\n\n

Approved nonprofits can conduct fundraising under Apple’s nonprofit rules, including permitted Apple Pay flows. A payment tied to digital benefits is not a pure donation and can become IAP.<\/p>\n\n\n\n

24. Can I charge marketplace sellers?<\/h2>\n\n\n\n

Yes for legitimate marketplace\/business services, but classify what the seller is buying. An advertising boost shown in the same app is a digital IAP; a commission on a physical marketplace transaction is outside IAP.<\/p>\n\n\n\n

25. Can I take a commission on physical bookings?<\/h2>\n\n\n\n

Yes. Your platform’s commission\/take-rate is separate from Apple. The buyer transaction for a physical\/offline service is generally outside IAP.<\/p>\n\n\n\n

26. Can I use Apple Pay?<\/h2>\n\n\n\n

Yes where Apple Pay is appropriate, especially physical goods\/services and eligible donations. Apple Pay does not replace required IAP for digital in-app value.<\/p>\n\n\n\n

27. Can I use Google Pay?<\/h2>\n\n\n\n

If your PSP\/platform supports it in the relevant non-IAP context, payment rail choice is secondary to Apple’s product classification. Availability on iOS varies by provider\/market. Do not treat it as an IAP substitute for digital app value.<\/p>\n\n\n\n

28. Can I use PayPal?<\/h2>\n\n\n\n

Yes for physical\/offline\/permitted external transactions. Not as a generic replacement for required IAP.<\/p>\n\n\n\n

29. Can I use Razorpay?<\/h2>\n\n\n\n

Yes in appropriate non-IAP or approved regional payment flows, subject to Razorpay market\/product support and Apple’s applicable rules.<\/p>\n\n\n\n

30. Can I use Adyen or Braintree?<\/h2>\n\n\n\n

Same principle: yes for transactions where external payment is allowed\/required; no as a default-rule substitute for IAP digital commerce.<\/p>\n\n\n\n

31. Can I use Square?<\/h2>\n\n\n\n

Yes for eligible real-world\/physical commerce; classification still controls.<\/p>\n\n\n\n

32. Can Apple reject my app over payment design?<\/h2>\n\n\n\n

Yes. Common causes include non-IAP digital checkout, unapproved external CTAs, misuse of an exception, hidden flows, missing regional disclosures, and an untestable IAP implementation.<\/p>\n\n\n\n

33. Can Apple remove my developer account?<\/h2>\n\n\n\n

Serious or repeated deception, fraud, or deliberate policy circumvention can escalate beyond a single rejection. Apple explicitly warns that misleading entitlement\/payment practices can lead to app removal and possible Developer Program removal.<\/p>\n\n\n\n

34. Can I remotely enable Stripe after review?<\/h2>\n\n\n\n

Do not do this to conceal a noncompliant digital purchase path. Hidden\/dormant\/undocumented payment functionality is exactly the kind of evasion to avoid.<\/p>\n\n\n\n

35. Can I use a QR code that opens my website checkout?<\/h2>\n\n\n\n

Not as a substitute for required IAP. Apple’s guideline explicitly lists QR codes among proprietary unlock methods that cannot replace IAP for app functionality.<\/p>\n\n\n\n

36. Can I email users a web purchase offer?<\/h2>\n\n\n\n

Apple’s default guideline permits developers to communicate outside the app with users about purchasing methods other than IAP. Email\/SMS marketing still has privacy, consent, anti-spam, and local-law obligations.<\/p>\n\n\n\n

37. Can my website be cheaper than IAP?<\/h2>\n\n\n\n

Web pricing strategy is commercially possible, but what the app may say\/show\/link about that price depends on storefront and program. Also assess Apple’s regional business terms and any platform agreement constraints applicable to the transaction.<\/p>\n\n\n\n

38. Do U.S. apps need the External Link Account Entitlement to link out?<\/h2>\n\n\n\n

Current App Review Guidelines say the entitlement is not required<\/strong> for buttons, external links, or other calls to action in U.S. storefront apps.<\/p>\n\n\n\n

39. Does Apple currently charge a U.S. external-link commission?<\/h2>\n\n\n\n

As verified September 5, 2026, the Ninth Circuit says Apple should not charge linked-out commission until the district court approves an appropriate fee, and no such future fee has yet been approved. The case remains active, so verify again before launch.<\/p>\n\n\n\n

40. Is Apple’s proposed 15% U.S. link-out fee current law\/fee?<\/h2>\n\n\n\n

No. It is a proposal in ongoing litigation as of this guide’s verification date, not the currently approved linked-out fee.<\/p>\n\n\n\n

41. Are EU external payments 0% Apple?<\/h2>\n\n\n\n

No, not generally. Current EU alternative terms impose layered Apple fees, and the unified terms announced for October 1, 2026 also specify commissions on alternative in-app and actionable linked-out digital sales.<\/p>\n\n\n\n

42. What changes in the EU on October 1, 2026?<\/h2>\n\n\n\n

Apple’s announced unified model replaces the previous layered terms with new commission schedules, including 26% standard IAP, 20% standard alternative in-app, 15% standard actionable linked-out sales, and 5% CTC for specified digital transactions outside the App Store, with reduced rates\/waivers in defined cases.<\/p>\n\n\n\n

43. Are Japan external payments 0% Apple?<\/h2>\n\n\n\n

No. The current model has 21%\/10% App Store commission on relevant digital sales and 15%\/10% store-services commission on relevant actionable link-outs; IAP adds a separate 5% Apple processing component.<\/p>\n\n\n\n

44. Are Brazil external payments 0% Apple?<\/h2>\n\n\n\n

No. Brazil’s current regional fee model similarly retains Apple commission and reporting obligations.<\/p>\n\n\n\n

45. Is South Korea alternative payment 0% Apple?<\/h2>\n\n\n\n

No. Apple currently states a 26% commission on the sanctioned third-party in-app payment route.<\/p>\n\n\n\n

46. Can I use IAP and South Korea alternative payment in the same app?<\/h2>\n\n\n\n

Under the current South Korea entitlement, no. Apple says the entitlement-enabled app cannot use Apple’s IAP and requires a separate Korea-only binary.<\/p>\n\n\n\n

47. Can any Netherlands app use third-party digital checkout?<\/h2>\n\n\n\n

The special Netherlands entitlement described here is specifically for dating apps. Do not generalize it to all categories.<\/p>\n\n\n\n

48. Does a reader app have to use IAP?<\/h2>\n\n\n\n

A reader app can let users sign in and access previously purchased eligible media content\/subscriptions. If it chooses to sell qualifying digital content inside the app, the ordinary IAP rules apply unless a regional mechanism changes the purchase route.<\/p>\n\n\n\n

49. Can a reader app link directly to checkout?<\/h2>\n\n\n\n

The classic External Link Account Entitlement is an account-creation\/management link with strict rules, not a generic checkout button. U.S. and regional external-purchase rules can separately permit broader purchase promotion.<\/p>\n\n\n\n

50. Can a social-media app call itself a reader because it has video?<\/h2>\n\n\n\n

Not simply because it displays media. Apple says media must be the app’s primary functionality for reader eligibility and gives social networking with streamed audiovisual content as a non-qualifying example.<\/p>\n\n\n\n

51. Can my app sell NFTs with Stripe?<\/h2>\n\n\n\n

NFT rules distinguish NFT services, ownership, and functionality. Apple permits IAP for NFT minting\/listing\/transferring and restricts using NFT ownership to unlock app functionality. External-purchase links are storefront-specific; get specialized review for novel crypto\/NFT flows.<\/p>\n\n\n\n

52. Can a crypto exchange use IAP to buy cryptocurrency?<\/h2>\n\n\n\n

Cryptocurrency exchange transactions are governed by Apple’s crypto\/financial-service rules and licensing requirements, not treated as ordinary IAP virtual goods. Premium digital app features remain a separate classification.<\/p>\n\n\n\n

53. Can an insurance app use IAP?<\/h2>\n\n\n\n

Apple’s guideline says insurance apps must be free, comply with law, and may not use IAP. The regulated insurance transaction is handled through the provider’s permitted systems.<\/p>\n\n\n\n

54. Can a brokerage use IAP for stock purchases?<\/h2>\n\n\n\n

No; securities trading is a regulated financial transaction, and Apple has separate provider\/licensing rules. A premium digital analytics feature sold in the app is a separate question.<\/p>\n\n\n\n

55. Can a remote-desktop app avoid IAP?<\/h2>\n\n\n\n

Potentially for transactions occurring on the host device if the app strictly meets Guideline 4.2.7’s remote-desktop conditions. Do not stretch that rule to an ordinary thin client for cloud apps.<\/p>\n\n\n\n

56. Do I need receipt validation?<\/h2>\n\n\n\n

For IAP, use current StoreKit\/App Store Server APIs and authoritative transaction verification; do not gate durable paid access on an unverified local flag. \u201cReceipt validation\u201d is often used generically, but modern StoreKit transaction\/server verification should drive the architecture.<\/p>\n\n\n\n

57. Do I need webhooks\/server notifications?<\/h2>\n\n\n\n

For production subscriptions, yes. Use App Store Server Notifications for Apple lifecycle events and PSP webhooks for web billing, process them idempotently, and reconcile against authoritative state.<\/p>\n\n\n\n

58. Should Apple and Stripe subscriptions share the same database table?<\/h2>\n\n\n\n

They should share a normalized entitlement\/subscription domain model, while preserving provider-specific transaction\/event tables. Do not throw away the source identifiers or raw audit data.<\/p>\n\n\n\n

59. Should I store the App Store storefront on each transaction?<\/h2>\n\n\n\n

Yes when regional commerce logic may matter. Storefront, agreement\/policy version, payment source, and external-link attribution are important for compliance, finance, and reporting.<\/p>\n\n\n\n

60. What is the safest way to minimize Apple commission without rejection?<\/h2>\n\n\n\n

Choose a business model that genuinely qualifies: physical\/offline service, enterprise organization sale, qualifying real-time one-to-one service, reader\/companion\/web-first existing-customer model, or an explicit regional program. Then document it clearly and implement the exact UI\/entitlement\/reporting rules. Do not hide the payment route.<\/p>\n\n\n\n

22. Before Submitting an App That Has Payments \u2014 master checklist<\/h1>\n\n\n\n

Business-model classification<\/h2>\n\n\n\n

\u2610 We can state in one sentence exactly what the customer buys.<\/p>\n\n\n\n

\u2610 Each SKU is classified as physical\/offline, digital in-app, enterprise, P2P, reader, companion, advertising management, financial, donation, or another explicit class.<\/p>\n\n\n\n

\u2610 We do not assume the entire app has one classification if it sells mixed products.<\/p>\n\n\n\n

\u2610 We have documented why each non-IAP digital-looking transaction fits an Apple exception or regional program.<\/p>\n\n\n\n

Storefront and regional rules<\/h2>\n\n\n\n

\u2610 We know which App Store storefronts the binary supports.<\/p>\n\n\n\n

\u2610 Payment UI is keyed to StoreKit storefront\/program eligibility, not IP geolocation alone.<\/p>\n\n\n\n

\u2610 U.S. external-link behavior is isolated from worldwide\/default behavior.<\/p>\n\n\n\n

\u2610 EU logic distinguishes pre-Oct 1, 2026<\/strong> terms from the new unified terms.<\/p>\n\n\n\n

\u2610 Japan\/Brazil\/Korea\/Netherlands special flows use the correct entitlement and OS\/version requirements.<\/p>\n\n\n\n

\u2610 We have a policy-version feature flag so a future legal\/Apple change can be deployed safely.<\/p>\n\n\n\n

IAP and StoreKit<\/h2>\n\n\n\n

\u2610 Required digital features use IAP unless a verified exception applies.<\/p>\n\n\n\n

\u2610 App Store Connect products are complete, submitted, visible, and testable.<\/p>\n\n\n\n

\u2610 Product IDs map to internal plan IDs; they are not the domain model.<\/p>\n\n\n\n

\u2610 Purchases are verified authoritatively.<\/p>\n\n\n\n

\u2610 App Store Server Notifications are processed idempotently.<\/p>\n\n\n\n

\u2610 Restorable products have a working Restore Purchases path.<\/p>\n\n\n\n

\u2610 Subscription group \/ upgrade \/ downgrade \/ crossgrade behavior is intentional.<\/p>\n\n\n\n

\u2610 Billing Grace Period and retry states do not accidentally revoke valid access.<\/p>\n\n\n\n

\u2610 Refund\/revocation events are handled.<\/p>\n\n\n\n

\u2610 Family Sharing behavior is handled if enabled.<\/p>\n\n\n\n

External gateway \/ website<\/h2>\n\n\n\n

\u2610 The gateway is used only where external payment is allowed or required.<\/p>\n\n\n\n

\u2610 We know who handles tax, refunds, chargebacks, fraud, and customer support.<\/p>\n\n\n\n

\u2610 External checkout does not masquerade as a physical purchase.<\/p>\n\n\n\n

\u2610 Reader account links meet the exact domain\/browser\/wording\/URL rules.<\/p>\n\n\n\n

\u2610 South Korea external payment is native, not WebView, and uses approved configuration.<\/p>\n\n\n\n

\u2610 Regional actionable links implement required StoreKit APIs\/tokens\/disclosures.<\/p>\n\n\n\n

\u2610 We can generate required alternative-payment transaction reports to Apple.<\/p>\n\n\n\n

Backend entitlement architecture<\/h2>\n\n\n\n

\u2610 Apple and web payments feed one normalized entitlement service.<\/p>\n\n\n\n

\u2610 Raw provider events are retained for audit\/replay.<\/p>\n\n\n\n

\u2610 Event handlers are idempotent.<\/p>\n\n\n\n

\u2610 We store source, plan, status, expiry, transaction lineage, and external customer\/subscription IDs.<\/p>\n\n\n\n

\u2610 Storefront and agreement\/policy version are persisted when relevant.<\/p>\n\n\n\n

\u2610 A scheduled reconciliation job detects drift between providers and entitlement state.<\/p>\n\n\n\n

\u2610 Account\/organization roles cannot accidentally grant paid access without an entitlement decision.<\/p>\n\n\n\n

App Review<\/h2>\n\n\n\n

\u2610 Review Notes explain the business\/payment model in plain language.<\/p>\n\n\n\n

\u2610 A valid demo account or full demo mode is provided if login is required.<\/p>\n\n\n\n

\u2610 Backend services are live during review.<\/p>\n\n\n\n

\u2610 Non-obvious features and IAP are explained.<\/p>\n\n\n\n

\u2610 No hidden, dormant, reviewer-only, or remotely activated payment path exists.<\/p>\n\n\n\n

\u2610 Screenshots\/metadata do not advertise a payment flow the binary cannot legally present.<\/p>\n\n\n\n

\u2610 Regional payment UI is testable and appears only in eligible storefronts.<\/p>\n\n\n\n

\u2610 Account creation includes in-app account-deletion initiation.<\/p>\n\n\n\n

\u2610 Login complies with Guideline 4.8 where applicable.<\/p>\n\n\n\n

Legal, tax, and customer terms<\/h2>\n\n\n\n

\u2610 Privacy policy identifies payment\/account data flows.<\/p>\n\n\n\n

\u2610 Terms of service explain billing, renewal, cancellation, and refunds.<\/p>\n\n\n\n

\u2610 External-payment tax responsibility is assigned and implemented.<\/p>\n\n\n\n

\u2610 Required VAT\/GST\/sales-tax registrations and invoices are handled.<\/p>\n\n\n\n

\u2610 Refund, cancellation, and dispute flows work for both Apple and external payment sources.<\/p>\n\n\n\n

\u2610 Regulated products (health, finance, crypto, insurance) have separate legal\/compliance review.<\/p>\n\n\n\n

23. SEO and publishing pack<\/h1>\n\n\n\n

SEO title:<\/strong> Apple App Store Commission & IAP Guide 2026: External Payments and Legal 0% Architectures<\/p>\n\n\n\n

Meta description:<\/strong> A current 2026 master guide to Apple App Store commission, 15%\/30% fees, IAP, Stripe and external payments, reader\/B2B\/SaaS rules, U.S.\/EU\/Japan\/Korea\/Brazil differences, and policy-compliant 0% Apple commission architectures.<\/p>\n\n\n\n

URL slug:<\/strong> apple-app-store-commission-iap-external-payments-zero-percent-guide-2026<\/p>\n\n\n\n

Suggested H1:<\/strong> Apple App Store Commission, In-App Purchase, External Payments & Legal 0% Commission Architecture \u2014 2026 Master Guide<\/p>\n\n\n\n

Recommended H2\/H3 hierarchy<\/h2>\n\n\n\n

\u2022 H2: What Apple App Store Commission Really Means<\/p>\n\n\n\n

\u2022 H3: When Apple Charges Commission<\/p>\n\n\n\n

\u2022 H3: When Apple Does Not Charge Commission<\/p>\n\n\n\n

\u2022 H3: Commission vs Taxes vs Processing Fees<\/p>\n\n\n\n

\u2022 H2: In-App Purchase (IAP) Explained<\/p>\n\n\n\n

\u2022 H3: When IAP Is Mandatory<\/p>\n\n\n\n

\u2022 H3: When IAP Is Optional<\/p>\n\n\n\n

\u2022 H3: When IAP Should Not Be Used<\/p>\n\n\n\n

\u2022 H2: Apple Pay vs Apple IAP<\/p>\n\n\n\n

\u2022 H2: Stripe, PayPal, Razorpay, Adyen and External Gateways<\/p>\n\n\n\n

\u2022 H2: Website Payments and External Links<\/p>\n\n\n\n

\u2022 H2: How to Legally Reach 0% Apple Commission<\/p>\n\n\n\n

\u2022 H2: Apple Payment Rules by Region<\/p>\n\n\n\n

\u2022 H3: United States<\/p>\n\n\n\n

\u2022 H3: European Union<\/p>\n\n\n\n

\u2022 H3: Japan<\/p>\n\n\n\n

\u2022 H3: Brazil<\/p>\n\n\n\n

\u2022 H3: South Korea<\/p>\n\n\n\n

\u2022 H3: Netherlands Dating Apps<\/p>\n\n\n\n

\u2022 H2: SaaS and B2B Payment Architecture<\/p>\n\n\n\n

\u2022 H2: Hybrid IAP + Web Billing Architecture<\/p>\n\n\n\n

\u2022 H2: Subscription Commission and StoreKit Lifecycle<\/p>\n\n\n\n

\u2022 H2: App Review Rejection Risks<\/p>\n\n\n\n

\u2022 H2: Economic Comparison<\/p>\n\n\n\n

\u2022 H2: 60-Scenario Matrix<\/p>\n\n\n\n

\u2022 H2: Developer FAQ<\/p>\n\n\n\n

\u2022 H2: App Submission Checklist<\/p>\n\n\n\n

Featured-snippet answers<\/h2>\n\n\n\n

Does Apple always take 30%?<\/strong><\/p>\n\n\n\n

No. Apple’s fee depends on the product and storefront. Physical goods and real-world services generally pay 0% App Store commission; Small Business Program IAP can be 15%; qualifying subscription renewals move to a 15% effective commission under the standard model; and regional payment programs use other fee structures.<\/p>\n\n\n\n

Can an iOS app use Stripe?<\/strong><\/p>\n\n\n\n

Yes when external payment is allowed \u2014 for example physical goods, real-world services, qualifying one-to-one services, enterprise\/web transactions, or an approved regional alternative-payment program. Stripe cannot simply replace required IAP for digital in-app value under default rules.<\/p>\n\n\n\n

Can users pay on a website and use the iOS app?<\/strong><\/p>\n\n\n\n

Often yes. Reader, multiplatform, enterprise, and free companion models can recognize existing web purchases. Whether the app may actively link to or promote the website checkout depends on the App Store storefront and applicable entitlement\/program.<\/p>\n\n\n\n

When can Apple commission be 0%?<\/strong><\/p>\n\n\n\n

Common examples include physical\/offline sales, qualifying one-to-one real-time services, direct enterprise organization licenses, compliant existing web subscriber access, approved companion\/reader architectures, and \u2014 currently \u2014 U.S. linked-out purchases while the federal court has not approved a future Apple fee.<\/p>\n\n\n\n

FAQ schema-ready question set<\/h2>\n\n\n\n

The 60 questions in Section 21 are written as concise standalone questions and can be mapped directly to FAQPage JSON-LD where search-engine policy permits. Do not mark up answers that are not visible on the published page, and do not assume FAQ rich results are guaranteed.<\/p>\n\n\n\n

24. Final quick reference<\/h1>\n\n\n\n

Apple commission can often be 0% when<\/h2>\n\n\n\n

\u2022 physical goods are sold;<\/p>\n\n\n\n

\u2022 real-world\/offline services are sold;<\/p>\n\n\n\n

\u2022 eligible real-time one-to-one services are sold;<\/p>\n\n\n\n

\u2022 enterprise\/B2B licenses are sold directly to organizations\/groups for employees\/students;<\/p>\n\n\n\n

\u2022 existing web subscribers merely log in under a compliant reader\/multiplatform\/companion model;<\/p>\n\n\n\n

\u2022 an eligible reader or companion architecture is used correctly;<\/p>\n\n\n\n

\u2022 approved nonprofit\/P2P-gift or other explicit exceptions apply;<\/p>\n\n\n\n

\u2022 a current regional rule explicitly produces 0% Apple fees \u2014 notably current U.S. linked-out purchases as of the verification date, subject to active litigation.<\/p>\n\n\n\n

Apple commission commonly becomes relevant when<\/h2>\n\n\n\n

\u2022 digital content;<\/p>\n\n\n\n

\u2022 digital functionality;<\/p>\n\n\n\n

\u2022 app subscriptions;<\/p>\n\n\n\n

\u2022 virtual goods;<\/p>\n\n\n\n

\u2022 digital consumables;<\/p>\n\n\n\n

\u2022 premium features;<\/p>\n\n\n\n

\u2022 game currency;<\/p>\n\n\n\n

\u2022 in-app AI credits;<\/p>\n\n\n\n

\u2022 same-app advertising\/boosts<\/p>\n\n\n\n

are sold through or in connection with the iOS app under a route governed by Apple’s digital-commerce terms.<\/p>\n\n\n\n

Final rule to remember<\/h2>\n\n\n\n
1. CLASSIFY WHAT IS SOLD.
2. IDENTIFY WHERE THE VALUE IS CONSUMED.
3. CHECK APP CATEGORY \/ EXCEPTION.
4. CHECK THE APP STORE STOREFRONT.
5. CHECK THE ENTITLEMENT + AGREEMENT VERSION.
6. ONLY THEN CHOOSE IAP, APPLE PAY, STRIPE, PAYPAL, RAZORPAY, ADYEN, ETC.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Regional rules and entitlements can change the answer.<\/strong><\/p>\n\n\n\n

25. Official Apple reference links and high-authority legal sources<\/h1>\n\n\n\n

Core Apple policy<\/h2>\n\n\n\n

1.<\/strong> App Review Guidelines<\/a> \u2014 especially 2.1, 2.3, 3.1.1-3.1.5, 4.2.7, 4.8, 4.9, 5.1.1.<\/p>\n\n\n\n

2.<\/strong> In-App Purchase types \u2014 App Store Connect Help<\/a><\/p>\n\n\n\n

3.<\/strong> StoreKit documentation<\/a><\/p>\n\n\n\n

4.<\/strong> App Store business models<\/a><\/p>\n\n\n\n

5.<\/strong> Auto-renewable subscriptions<\/a><\/p>\n\n\n\n

6.<\/strong> View subscription data \/ proceeds rates<\/a><\/p>\n\n\n\n

7.<\/strong> App Store Small Business Program<\/a><\/p>\n\n\n\n

8.<\/strong> Apple Developer Program enrollment and fees<\/a><\/p>\n\n\n\n

9.<\/strong> Reader apps \/ External Link Account Entitlement<\/a><\/p>\n\n\n\n

10.<\/strong> External Purchase \u2014 StoreKit<\/a><\/p>\n\n\n\n

11.<\/strong> Offering account deletion in your app<\/a><\/p>\n\n\n\n

Regional payment\/distribution programs<\/h2>\n\n\n\n

12.<\/strong> Changes for apps in the European Union<\/a><\/p>\n\n\n\n

13.<\/strong> Communication and promotion of offers on the App Store in the EU<\/a><\/p>\n\n\n\n

14.<\/strong> Store Services tiers in the EU<\/a><\/p>\n\n\n\n

15.<\/strong> Music Streaming Services Entitlement \u2014 EEA<\/a><\/p>\n\n\n\n

16.<\/strong> Changes to iOS in Japan<\/a><\/p>\n\n\n\n

17.<\/strong> Payment options on the App Store in Japan<\/a><\/p>\n\n\n\n

18.<\/strong> Changes to iOS in Brazil<\/a><\/p>\n\n\n\n

19.<\/strong> Payment options on the App Store in Brazil<\/a><\/p>\n\n\n\n

20.<\/strong> Third-party payment providers in South Korea<\/a><\/p>\n\n\n\n

21.<\/strong> Dating apps in the Netherlands<\/a><\/p>\n\n\n\n

22.<\/strong> StoreKit external purchases or offers entitlement<\/a><\/p>\n\n\n\n

U.S. legal status<\/h2>\n\n\n\n

23.<\/strong> Epic Games, Inc. v. Apple Inc. \u2014 Ninth Circuit opinion, Dec. 11, 2025<\/a><\/p>\n\n\n\n

24.<\/strong> U.S. Supreme Court docket 25-1311 \u2014 Apple Inc. v. Epic Games, Inc.<\/a><\/p>\n\n\n\n

25.<\/strong> U.S. Supreme Court stay docket 26A194<\/a><\/p>\n\n\n\n

External payment-cost reference used in economics example<\/h2>\n\n\n\n

26.<\/strong> Stripe pricing<\/a> \u2014 used only for the illustrative external-processing comparison; actual merchant pricing varies.<\/p>\n\n\n\n

26. Completeness audit<\/h1>\n\n\n\n

This guide has explicitly covered:<\/p>\n\n\n\n

\u2022 Apple Developer Program membership vs commission vs payment processing vs PSP fees vs taxes;<\/p>\n\n\n\n

\u2022 standard 30% \/ 15% models and subscription-after-one-year mechanics;<\/p>\n\n\n\n

\u2022 Small Business Program threshold\/associated-account logic;<\/p>\n\n\n\n

\u2022 all four IAP types;<\/p>\n\n\n\n

\u2022 Apple Pay vs IAP;<\/p>\n\n\n\n

\u2022 Stripe, Razorpay, PayPal, Adyen, Braintree, Square, and card-payment classification;<\/p>\n\n\n\n

\u2022 website purchase, login-only, external links, pricing text, CTAs, WebViews, QR codes;<\/p>\n\n\n\n

\u2022 reader, companion\/free stand-alone, multiplatform, enterprise\/B2B, P2P, ad-management exceptions;<\/p>\n\n\n\n

\u2022 physical goods\/services, travel, transportation, healthcare, education, marketplace, donations, finance, crypto\/NFT, remote desktop, VPN, SaaS, cloud, developer tools, AI;<\/p>\n\n\n\n

\u2022 U.S., EU\/EEA, Japan, Brazil, South Korea, Netherlands special rules;<\/p>\n\n\n\n

\u2022 current EU pre-October terms and the October 1, 2026 announced transition;<\/p>\n\n\n\n

\u2022 current U.S. court status and the fact that a proposed future fee is not yet the current approved fee;<\/p>\n\n\n\n

\u2022 60-scenario decision matrix;<\/p>\n\n\n\n

\u2022 10 architecture blueprints plus hybrid entitlement schema;<\/p>\n\n\n\n

\u2022 subscription lifecycle, offers, grace, restore, Family Sharing;<\/p>\n\n\n\n

\u2022 App Review rejection patterns and compliant alternatives;<\/p>\n\n\n\n

\u2022 economic comparisons at $10K, $100K, $500K, $1M, and $5M;<\/p>\n\n\n\n

\u2022 five founder architecture choices;<\/p>\n\n\n\n

\u2022 25 myths;<\/p>\n\n\n\n

\u2022 60 developer FAQs;<\/p>\n\n\n\n

\u2022 submission checklist;<\/p>\n\n\n\n

\u2022 SEO title, meta description, slug, hierarchy, featured snippets, and FAQ schema-ready question set.<\/p>\n\n\n\n

Research stop condition:<\/strong> The material payment classifications are supported by current Apple primary documentation; fast-changing regional rules were checked against Apple’s current support pages; and the consequential U.S. link-out fee status was cross-checked against the Ninth Circuit opinion and current Supreme Court docket. Remaining uncertainty is explicitly identified where policy is pending future effective dates or active litigation.<\/p>\n\n\n\n

Last verified: September 5, 2026<\/h1>\n\n\n\n

Apple’s policies, agreements, regional regulatory programs, and court-imposed U.S. rules can change. Before shipping a payment-flow change, re-check the applicable App Review Guidelines, developer agreement, regional support page, and entitlement terms for the exact storefront and app version<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Current iOS\/iPadOS payment-policy, architecture, and App Review reference Last verified September 5, 2026 Primary authority Apple Developer documentation + App Review Guidelines U.S. legal status Cross-checked against… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-78467","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/78467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=78467"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/78467\/revisions"}],"predecessor-version":[{"id":78468,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/78467\/revisions\/78468"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=78467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=78467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=78467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}