App Store RejectionGuideline 3.1.1 — In-App Purchase

You linked to your website to handle payment. Apple rejected it.

Guideline 3.1.1 means that if you sell digital content or features inside your app, the purchase must go through Apple's In-App Purchase system — not your own payment page.

What Apple said

“Your app includes buttons, external links, or other calls to action that direct users to a payment mechanism other than in-app purchase to unlock features, purchase digital content, or subscribe to a service. This is not in compliance with App Store Review Guideline 3.1.1.”

What this actually means

Apple requires all purchases of digital goods and services — subscriptions, premium features, consumable credits, downloadable content — to be processed through their In-App Purchase (IAP) system when sold inside an iOS app. You cannot include a 'Buy on our website' button, a Stripe payment link, or any external checkout flow for digital goods. Physical goods and services consumed outside the app (like ride-sharing or food delivery) are exempt.

What Apple needs to see

  • All digital purchases, subscriptions, or feature unlocks completed entirely through Apple's StoreKit In-App Purchase API
  • No buttons, links, or text that directs users to an external website or payment processor to complete a digital purchase
  • No mention of pricing available elsewhere that implies a cheaper option outside the App Store
  • Your app's Terms of Service should reflect IAP as the purchase mechanism for in-app digital goods
  1. 1Audit every screen in your app for buttons, links, or text that reference external checkout, Stripe, PayPal, or your website's pricing page and remove or disable them.
  2. 2Implement StoreKit 2 (iOS 15+) or the original StoreKit to create product identifiers in App Store Connect for every paid feature or subscription tier your app offers.
  3. 3Replace your existing payment flow with a native IAP sheet so users can complete purchases without leaving the app.
  4. 4Update your app's Terms of Service — BaseTerms can generate a compliant ToS that accurately describes your IAP-based purchase model — and link to it within your app settings.
  5. 5Test the full purchase, restore, and refund flow thoroughly in the Sandbox environment before resubmitting, as reviewers will attempt to tap every purchasable element.

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page
Marketing Page
Generate my compliance pages — $9

Common questions

My app is a SaaS tool. Can users subscribe on my website and just log in on iOS?
Yes, with nuance. If users subscribe on your website and your app simply authenticates them, that is generally permitted — you just cannot have a button inside the app that says 'Subscribe' and routes to your website. The distinction is whether the purchase is initiated from within the app.
What about the court ruling that said Apple must allow external payment links?
A US court order (the Epic v. Apple case) resulted in Apple allowing certain external payment links in the US App Store under specific conditions, with Apple still collecting a commission. This is a narrow, evolving exception — you must apply for an entitlement and follow strict UI rules. For most developers, IAP remains the safest and simplest path.
Does 3.1.1 apply to B2B or enterprise apps?
Apps distributed exclusively through the Apple Business Manager to a specific organization have more flexibility. Consumer apps and any app available on the public App Store are fully subject to 3.1.1.

Ready to pass review?

Generate all your compliance pages in 60 seconds.

Get started — $9