Guideline 3.1.1 digital goods IAP rejection checklist
A 3.1.1 rejection is not just a broken product ID. It is a mismatch between what the user buys, where it is consumed, and how payment is routed.
Classify every paid item before changing code. Apple Guideline 3.1.1 governs in-app purchase for digital goods and services, and Apple provides In-App Purchase setup guidance. AppReviewReady interpretation: the repair is a payment-route matrix, not a single paywall copy edit.
Classify what the user buys
List subscriptions, credits, tokens, unlocks, content libraries, AI outputs, account upgrades, coaching plans, cloud features, community access, downloads, and services. Mark whether each value is consumed inside the app, outside the app, or both.
Do not classify a payment by the processor used today. Classify it by the user value and where that value appears.
Map every payment route
- In-app paywall, website checkout, email link, account portal, QR code, support invoice, and third-party SDK.
- Upgrade, downgrade, restore, refund, grace, billing retry, and expired entitlement states.
- Reader-app, external purchase link, physical goods, real-world services, and enterprise exceptions where relevant.
- Marketing copy that points users away from IAP.
- Server entitlements that unlock app value after any external purchase.
Choose the correct repair
If the value is a digital good consumed in the app and no exception applies, implement StoreKit and remove external purchase prompts from the app surface. If an exception applies, document the entitlement, region, and exact user path.
AppReviewReady interpretation: hiding a checkout link while keeping server-side app unlocks can still be risky if the app guides users to external purchase indirectly.
Test entitlement behavior after the payment change
- Purchase, restore, cancel, refund, expire, and switch accounts.
- Open the app after buying on another device or platform.
- Verify locked content does not advertise an external workaround.
- Check metadata, screenshots, support docs, and onboarding copy.
- Confirm App Review can reach a paid or sandbox state without production payment confusion.
3.1.1 payment matrix
The response should explain the corrected route for each affected good, not only say that IAP was added.
After approval, add payment-route checks to release QA. New bundles, AI credits, content drops, and account tiers can reintroduce 3.1.1 risk even when the original rejection was fixed.
If the app has both physical and digital value, split the receipt and entitlement logic. A real-world class, mailed product, or service appointment can coexist with digital content, but the app must not hide a digital unlock inside a physical-good label.
Check marketing emails, help articles, and onboarding screens after the fix. Reviewers can notice app copy that still instructs users to subscribe on the web even when the visible paywall was changed.
For teams migrating from web billing to IAP, plan account reconciliation before submission. Existing web subscribers should get a clear in-app state that does not pressure new users toward the old external flow.
Digital goods matrix: Item: [name] Consumed in app: [yes/no] Payment route: [IAP/web/other] Exception claimed: [none/type] Entitlement source: [StoreKit/server] External copy removed: [yes/no] Reviewer test: [steps]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check 3.1.1 payment risk
Map digital goods, exceptions, payment routes, and entitlement states before resubmission.
Open the tool