Guideline explainers

App Store Guideline 5.3 explained: Gaming, Gambling, and Lotteries

Guideline 5.3 is an App Review legal rule about gaming, gambling, and lotteries. For iOS developers, the practical risk is usually not the guideline number itself; it is whether the submitted build, product page, screenshots, policies, and review notes make compliance easy for Apple to verify. Use this explainer to turn the rule into a pre-submission checklist, a resubmission fix plan, and a concise reviewer reply for payments and monetization.

Developers searching for App Store Guideline 5.3 help, rejection causes, or fix guidance. Guideline 5.3 Official Apple source

What this guideline means in practice

Guideline 5.3 sits in Apple's Legal section and is most relevant to payments and monetization.

This page summarizes the review risk in practical terms and links to the official Apple source for the exact rule text.

Apple will check whether paid digital content, subscriptions, credits, and unlocks use the correct purchase flow.

What Apple is likely checking

Apple will check whether paid digital content, subscriptions, credits, and unlocks use the correct purchase flow.

Reviewers need to find paid features and understand what is included before purchase.

Metadata and paywall language should make purchase requirements clear.

Common rejection triggers

Digital goods are sold through an external purchase path when Apple's IAP system is expected.

Configured IAP products cannot be found during review.

The paywall, product descriptions, or screenshots do not explain what requires payment.

Fix checklist before resubmission

Make IAP products visible and functional in the reviewed build.

Document the exact purchase path in App Store Connect review notes.

Align subscription, pricing, and product copy across the app and App Store metadata.

Reviewer reply angle

If Apple cited Guideline 5.3, reply with the exact change you made and where the reviewer can verify it.

If you believe the app already complies, provide concise evidence, navigation steps, and any supporting documentation instead of a generic appeal.

Keep the tone factual and cooperative. Avoid promising approval or arguing beyond what the submitted build and metadata can prove.

Check your app against Guideline 5.3

AcceptMyApp can compare your metadata, screenshots, privacy pages, app context, and rejection text against Apple guideline risks before you resubmit.

Get started