How to Fix App Store Guideline 3.1.1 In-App Purchase Rejection
Map digital entitlements, external payment paths, and purchase messaging after an Apple Guideline 3.1.1 rejection.
Direct answer
Map the exact entitlement before changing anything: what the user buys, where payment happens, and what becomes available inside the app. Digital features or content unlocked in the app generally require the permitted App Store purchase path unless a current rule or entitlement applies. External-link rules can vary by storefront and entitlement, so verify the current Apple text for the storefronts you distribute in.
Match the wording in your rejection
A code, key, token, QR code, or wallet unlocks digital functionality
Apple likely sees an alternative mechanism bypassing In-App Purchase for a digital entitlement.
A button or link sends users to an external purchase flow
Check the current storefront-specific rule and any required entitlement; do not assume one global answer.
The purchase or restore control is unavailable during review
Verify product status, agreements, sandbox account state, storefront availability, binary association, restore behavior, and backend entitlement delivery.
What this rejection usually means
Guideline 3.1.1 generally applies when digital content or functionality is unlocked inside the app through a mechanism Apple believes should use In-App Purchase. The recovery starts with an entitlement map: what the user buys, where payment happens, and where access becomes available.
Likely rejection signals
- External checkout unlocks digital features in the iOS app
- License key, QR code, token, or wallet grants access
- Buttons or copy direct users to another purchase method
- Restore purchase, subscription status, or reviewer access is broken
Recovery plan
- Map every paid entitlement from purchase through activation and access inside the app.
- Classify the product accurately: digital feature, physical good, person-to-person service, reader content, enterprise service, or another documented category.
- Remove disallowed external purchase calls to action and implement In-App Purchase where required.
- Verify purchase, restore, cancellation-state, family-sharing, and clean-account behavior as applicable.
- Explain any claimed exception with facts and a reviewer-verifiable test path.
Evidence to prepare
- Entitlement and payment-flow diagram
- Screen recording of purchase and restore flows
- Product identifiers and review sandbox instructions
- Documentation supporting any applicable exception
Appeal or fix first?
Clarify or appeal when the purchase is outside 3.1.1’s digital-content scope or a documented exception clearly applies. Explain the business model factually.
Fix first when external payment directly unlocks digital functionality in the iOS app or the app steers users to an unapproved purchase path.
Reviewer response framework
Your response should be factual, short, and limited to the submitted build. Cover these points:
- Describe what is sold and where it is consumed.
- State the verified payment-flow change or applicable rule category.
- Provide sandbox access and a complete test path.
- Avoid broad claims that your business is exempt.
Frequently asked questions
Does every payment in an iOS app require In-App Purchase?
No. The treatment depends on what is sold and consumed. Digital content and functionality unlocked in the app are central to 3.1.1, while other categories have different rules.
Can I simply hide the external payment button during review?
No. Hidden or review-specific behavior creates additional compliance risk and does not resolve the product’s actual payment flow.
Need a rejection-specific plan?
Start with the free diagnosis. The $29 Fix Pack adds the prioritized remediation plan, evidence checklist, reviewer-ready reply, and preflight.
Source: Apple App Review Guidelines — 3.1.1 In-App Purchase. Platform policies change. Verify the official rule before submitting. Resubmit AI provides technical and editorial decision support, not an approval guarantee or legal advice.