Guideline 3.1.1 in-app purchase rejection: what it means and how to fix it
What 3.1.1 and 3.1.1(a) say, which storefronts allow links to other ways to pay, the exceptions in 3.1.3, how to fix the usual causes and what to tell App Review.
By our team. Published . 8 sources.
A guideline 3.1.1 rejection means App Review found a way to pay for, or unlock, digital features or content in your app that doesn't go through Apple's in-app purchase. Typically that is a web checkout, a "Subscribe on our website" button, a licence key or promo code that unlocks premium features, or a paywall that sends people to Stripe. The fix is to sell those digital items with in-app purchase, or to remove the outside payment route from the storefronts where it isn't allowed, unless your app falls under one of the specific exceptions Apple lists.
The rules are no longer the same everywhere. Apps on the United States storefront may now include buttons and links to other ways to pay, and the EU and Japan have their own programmes. Most rejections we see come from apps that assume the US rule applies worldwide, or that an exception covers them when it doesn't.
Send us your rejection
Paste what App Review sent you. We read it against the guideline and reply with what it will take and a fixed price, the same working day if it reaches us before 2pm UK time. Free, and no access needed yet.
What does guideline 3.1.1 say?
The core rule hasn't changed: "If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase. Apps may not use their own mechanisms to unlock content or functionality, such as license keys, augmented reality markers, QR codes, cryptocurrencies and cryptocurrency wallets, etc." [1]
The same guideline also says that "any credits or in-game currencies purchased via in-app purchase may not expire, and you should make sure you have a restore mechanism for any restorable in-app purchases", and that "digital gift cards, certificates, vouchers, and coupons which can be redeemed for digital goods or services can only be sold in your app using in-app purchase" [1].
3.1.1(a), Link to Other Purchase Methods, is where the regional rules live. It says developers "may apply for entitlements to provide a link in their app to a permitted destination in order to purchase digital content or services", and that "these entitlements are not required for developers to include buttons, external links, or other calls to action in their United States storefront apps" [1]. It ends: "In all other storefronts, except for the United States storefront, where this prohibition does not apply, apps and their metadata may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase" [1].
Where can my app link to other ways to pay?
This is the part that changes most often, so check Apple's own page for your storefront before relying on any of it. As of 17 November 2026, Apple's published rules say:
| Storefront | What Apple's pages allow | Source |
|---|---|---|
| United States | No entitlement is needed for "buttons, external links, or other calls to action" to other ways to buy. Apple made this change on 1 May 2025 "for compliance with a United States court decision" | [1], [2] |
| European Union | Alongside in-app purchase, in-app payment through another processor and "out-of-app offers" to a website, another app or an alternative marketplace, using the StoreKit External Purchases or Offers Entitlement. Commissions apply, and once chosen, the option must be kept "across all EU storefronts for 12 months" | [4] |
| Japan | Alternative payment options, including out-of-app offers, with the StoreKit External Purchases or Offers Entitlement, on iPhone with iOS 26.2 or later. Apple In-App Purchase must be offered on the same screen and "displayed at least as prominently as any other payment option shown" | [5] |
| Netherlands (dating apps only) | A third-party payment system or a link to your website, under separate StoreKit entitlements for dating apps | [6] |
| Everywhere else | No buttons, links or calls to action to other purchase methods, unless one of the 3.1.3 exceptions below applies | [1] |
Two points catch people out on the US change. First, the guideline's US wording is about "buttons, external links, or other calls to action" that point elsewhere [1]; it does not say an app may run its own card checkout for digital goods inside the app. Second, a US-only rule doesn't help an app that is also live in the UK, Australia or Canada: the link has to be limited to the storefronts where it is allowed, and the review notes should say how.
What are the exceptions?
Guideline 3.1.3 lists apps that "may use purchase methods other than in-app purchase". Outside the United States, apps in this section still "cannot, within the app, encourage users to use a purchasing method other than in-app purchase", except as set out in 3.1.1(a) and 3.1.3(a), though developers "can send communications outside of the app to their user base" [1].
- 3.1.3(a) Reader apps. Apps may let people access "previously purchased content or content subscriptions (specifically: magazines, newspapers, books, audio, music, and video)". Outside the US, a link to create or manage an account on your website needs the External Link Account Entitlement [1]. To be eligible the app must not offer in-app purchases on iOS, iPadOS or tvOS while using it, and the link must not mention prices [7].
- 3.1.3(b) Multiplatform services. People can use content bought on your website or another platform, "provided those items are also available as in-app purchases within the app" [1].
- 3.1.3(c) Enterprise services. Apps sold only to organisations for their staff or students. "Consumer, single user, or family sales must use in-app purchase" [1].
- 3.1.3(d) Person-to-person services. Real-time services between two people, such as tutoring or fitness training, may use other payment methods. "One-to-few and one-to-many real-time services must use in-app purchase" [1].
- 3.1.3(e) Goods and services outside of the app. Physical goods and services "consumed outside of the app" must use other payment methods, "such as Apple Pay or traditional credit card entry" [1]. This is why a shop, a taxi app or a gym booking app takes cards directly.
- 3.1.3(f) Free stand-alone apps. Free companions to a paid web tool for VoIP, cloud storage, email or web hosting, "provided there is no purchasing inside the app, or calls to action for purchase outside of the app" [1].
- 3.1.3(g) Advertising management apps. Apps that only let advertisers buy and manage campaigns. Buying "boosts" for posts in a social app still needs in-app purchase [1].
Two neighbouring rules also come up. 3.1.4 Hardware-specific content lets an app unlock features that depend on specific hardware without in-app purchase [1]. 3.1.5 is about cryptocurrencies (wallets, mining, exchanges), not physical goods [1].
Why was my app rejected under 3.1.1?
In the 3.1.1 rejections we fix, the cause is usually one of these:
- A web checkout or "Upgrade on our website" link shown to people outside the US, or shown worldwide because the app doesn't check the storefront.
- A licence key, promo code or QR code that unlocks premium features bought somewhere else.
- A login-only app that sells a consumer subscription on the web, with no in-app purchase, and doesn't qualify as a reader app or enterprise service.
- Credits or tokens sold on the web and spent in the app, or credits that expire.
- App Store metadata (description, screenshots, promotional text) that mentions cheaper prices on your website. Apple's rule covers "apps and their metadata" [1].
- Mixed goods. A marketplace that sells physical items by card (allowed under 3.1.3(e)) and also sells a digital "premium seller" plan by card (not allowed).
- A missing Restore Purchases option for non-consumable purchases or subscriptions.
How do I fix it?
- List every way money changes hands. In the app, in any web view, in emails the app triggers, and in the App Store listing. Mark each one as digital (used in the app) or physical/real-world.
- Decide which rule applies to each digital item. Is it covered by an exception in 3.1.3? Is the app on a storefront that allows links (US, or EU and Japan with the entitlement)? If neither, it needs in-app purchase.
- Add in-app purchase where it is required. Set up the products in App Store Connect, make sure the Paid Apps Agreement is active and test in the sandbox [8]. Section 3 says pricing is up to you, as long as it isn't a clear rip-off [1].
- Limit external links to the storefronts that allow them. Check the user's App Store storefront with StoreKit before showing the link, and say how in the review notes.
- Remove purchase wording from metadata for storefronts where it isn't allowed.
- Add Restore Purchases where purchases are restorable.
- Resubmit with a reply that explains each change.
What should I write in the reply to App Review?
Explain the business model and exactly where each purchase lives. Apple says that "if your business model isn't obvious, make sure to explain in its metadata and App Review notes", and that if it can't understand how your in-app purchases work "it will delay your review and may trigger a rejection" [1]. For example:
If you believe an exception applies, name it and say why in one or two sentences. Don't argue that the rule is unfair; the reviewer can't change it.
How do I stop it happening again?
- Keep a written payments map: every product, whether it is digital or physical, and which rule covers it.
- Gate any external purchase link on the user's storefront, and check what the app shows in a US storefront and a non-US one before each release.
- Check the App Store description and screenshots for website prices or "cheaper on our site" wording.
- Re-read 3.1.1(a) before each release that touches payments. Apple's most recent change to it was published on 16 October 2026 [3].
Pre-submission checklist for guideline 3.1.1
- Every digital feature, subscription, credit pack or content unlock is sold with in-app purchase, unless a named 3.1.3 exception applies.
- No licence keys, promo codes or QR codes unlock paid features bought elsewhere.
- External purchase links appear only on storefronts where Apple allows them, with the right entitlement where one is required.
- Physical goods and real-world services use Apple Pay or card payment, not in-app purchase.
- Credits bought with in-app purchase don't expire.
- Restore Purchases works.
- The App Store listing doesn't mention buying on your website, except where allowed.
- The review notes explain the business model and how to reach every purchase.
Questions we get asked
- Can my app link to my website to pay now?
- On the United States storefront, yes: Apple's guidelines say no entitlement is needed for buttons, external links or other calls to action there. In the EU and Japan you can offer out-of-app offers with the StoreKit External Purchases or Offers Entitlement, under Apple's terms for those regions. On other storefronts, links to other ways to pay for digital goods are still not allowed unless a 3.1.3 exception applies.
- Does the US change mean I can drop in-app purchase in the US?
- The guideline change covers buttons, external links and calls to action that point to other ways to buy. The opening rule of 3.1.1, that unlocking features in the app uses in-app purchase, is still in the guideline. Read the current text carefully and keep the claim in your review notes narrow.
- Is my app a reader app?
- Only if its main purpose is giving access to previously purchased magazines, newspapers, books, audio, music or video. Apps where media is a side feature, such as a social app that streams video, are not reader apps. Reader apps can use the External Link Account Entitlement for an account link, but not while also offering in-app purchases on iOS, iPadOS or tvOS.
- Do physical products need in-app purchase?
- No. Guideline 3.1.3(e) says physical goods and services consumed outside the app must use other payment methods, such as Apple Pay or card entry. Anything used inside the app, such as a premium plan or digital content, still needs in-app purchase.
- Can I sell credits on my website and let people spend them in the app?
- Under 3.1.3(b), people can use items bought on your website or another platform only if those items are also available as in-app purchases in the app. Credits bought through in-app purchase may not expire.
- Can I unlock premium features with a promo code?
- Not with your own codes. Guideline 3.1.1 says apps may not use their own mechanisms such as licence keys or QR codes to unlock content or functionality. Sell the unlock with in-app purchase instead.
Sources
Checked on 17 November 2026.
- 1.Apple Developer, "App Review Guidelines" (3, 3.1.1, 3.1.1(a), 3.1.3(a) to (g), 3.1.4, 3.1.5; last updated 16 October 2026): https://developer.apple.com/app-store/review/guidelines/
- 2.Apple Developer News, "Updated guidelines now available" (1 May 2025): https://developer.apple.com/news/?id=9txfddzf
- 3.Apple Developer News, "Updated App Review Guidelines are now available" (16 October 2026): https://developer.apple.com/news/?id=92th7e5i
- 4.Apple Developer, "Payment options on the App Store in the EU": https://developer.apple.com/support/communication-and-promotion-of-offers-on-the-app-store-in-the-eu/
- 5.Apple Developer, "Payment options on the App Store in Japan": https://developer.apple.com/support/payment-options-on-the-app-store-in-japan/
- 6.Apple Developer, "Distributing dating apps in the Netherlands": https://developer.apple.com/support/storekit-external-entitlement/
- 7.Apple Developer, "Distributing 'reader' apps with a link to your website": https://developer.apple.com/support/reader-apps/
- 8.Apple Developer, App Review Help, "Configure In-App Purchases for review in the sandbox": https://developer.apple.com/help/app-review/before-submitting-for-review/configure-in-app-purchases