App Store 2.3.2 rejection: Showing which features cost extra
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps advertising in-app purchases, paid content, or subscriptions in store metadata.
A screenshot can make a paid feature look included with the download. Apple’s 2.3.2 requires the listing and previews to make extra purchases clear. Promoted in-app purchases also have their own public metadata and purchase-flow requirements.
Follow the offer as a new user
Compare each advertised feature with what a fresh account gets for free. Check descriptions, image captions, previews, and the display names and screenshots of promoted purchases. We’d read these without the knowledge of someone who designed the pricing.
Make the paid boundary clear
Identify content or functionality requiring another purchase in the relevant store materials. Keep promoted purchase text and images suitable for a public audience.
If you promote an in-app purchase on the store, ask your developer to verify the store-initiated purchase handling Apple documents, including the transaction observer behavior. Opening the app from that offer must lead into a functioning purchase flow.
Test both ordinary app entry and entry from a promoted purchase. Verify that the product shown matches the access received. Tell Apple which assets changed and how to exercise the corrected purchase route.
Messages this guide can help with
App Store 2.3.2 rejection; app store 2.3.2 denial; Guideline 2.3.2; Showing which features cost extra
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 2.3.2 Checked 22 September 2026