App Store 4.10 rejection: Charging for built-in capabilities

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps charging for access to built-in device features or Apple services and technologies.

You can build a paid product using device features, but Apple’s 4.10 prohibits monetizing the built-in capability itself. The rule names capabilities and services such as the camera, notifications, gyroscope, Apple Music access, iCloud storage, and Screen Time APIs.

Identify what the paywall sells

Compare the paid benefit with the system feature underneath it. Is the person paying for your own useful functionality, or simply to obtain access to a capability Apple already provides? We’d read the paywall literally and then test the free and paid states.

Redesign the offer

Remove a charge that gates the built-in capability or service itself. Make any legitimate paid value accurate and specific, and verify it against the relevant service terms. A renamed plan doesn’t change what is being sold.

Test access before and after payment and review the listing’s claims. Explain the corrected offer and the distinction between your app’s functionality and the system capability. Apple decides how the rule applies to the actual implementation, so provide a reproducible example rather than a broad monetization argument.

Messages this guide can help with

App Store 4.10 rejection; app store 4.10 denial; Guideline 4.10; Charging for built-in capabilities

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review