# Guideline 2.3.2 - Accurate Metadata: In-App Purchases Not Clearly Indicated

**Guideline:** 2.3.2 · **Store:** Apple App Store · **Severity:** low · **Fix difficulty:** easy · **Typical turnaround:** 1-2 hours

Canonical URL: https://appstorereject.com/rejections/apple/2/guideline-232-accurate-metadata-in-app-purchases-not-clearly-indicated

## Description

Apple is rejecting your app because the app description and screenshots do not clearly communicate that certain features require an in-app purchase. If your app is free to download but locks core features behind IAP, users should know this before they download. This rejection targets the bait-and-switch pattern where a free app's screenshots show premium features in full action, but users discover after download that those features require payment. Apple's position is that the App Store listing must set accurate expectations about what the free experience includes. The rejection is commonly triggered when: (1) screenshots prominently feature premium-only content without any indication of IAP, (2) the app description focuses on premium features without mentioning they're paid, or (3) the app's free functionality is so limited that the listing is misleading about the actual free experience.

## Common variations

- Screenshots showcase features only available through in-app purchase
- App description does not clearly indicate paid features
- Core features require IAP but this is not communicated in metadata
- Users may be misled about the app's free functionality
- Premium features not distinguished from free features in listing

## Example rejection email

```
Guideline 2.3.2 - Performance - Accurate Metadata

Your app's description and screenshots do not clearly indicate that in-app purchases are required to access the app's core features. Specifically, the app's screenshots showcase features that are only available through in-app purchase, which could mislead users about the app's free functionality.

Next Steps:
Please update your app's metadata to clearly indicate which features require in-app purchases. Consider adding text overlays to screenshots that show premium features, or updating the description to clearly distinguish between free and paid functionality.
```

## Resolution steps

## Quick Assessment
- **Risk level:** Low
- **Resolution path:** Update App Store metadata (no new binary needed)
- **Typical turnaround:** 1-2 hours

## The Fix

1. **Audit your screenshots** -- Identify which screenshots show premium-only features. Either replace them with screenshots of the free experience, or add clear visual indicators (e.g., a small 'Premium' badge overlay) on screenshots showing paid features.

2. **Update the app description** -- Add a clear section listing what's included free vs. what requires IAP. Something like: 'Free features include: X, Y, Z. Premium features (available via in-app purchase): A, B, C.'

3. **Lead with free features** -- Your first 2-3 screenshots and the first paragraph of your description should represent what free users actually get.

4. **Check the promotional text** -- The promotional text field at the top of your listing should not promise features that require payment.

5. **Verify in-app purchase descriptions** -- Each IAP listed in App Store Connect should have a clear description of what it unlocks.

## Prevention
- Always lead your App Store listing with the free experience
- If screenshots show premium features, label them clearly
- Write the description assuming users will only use the free tier
- Review your listing from a first-time user's perspective before submission

## Before / after examples

**Before:** Screenshot 1 shows the full photo editing suite with 40+ filters -- but 35 of those filters require a $4.99 IAP unlock
**After:** Screenshot 1 shows the 5 free filters available to all users. Screenshot 4 shows the premium filter pack with a 'Premium' badge overlay and the IAP price
**Why it works:** Lead with the free experience and clearly label any premium content shown in marketing materials.

## Common questions

**How long does this typically take to fix?**

Typical turnaround is 1-2 hours (difficulty: easy). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-232-accurate-metadata-in-app-purchases-not-clearly-indicated*