12 Subscription Paywall Details to Review Before Launching a Mobile App
Twelve paywall details for subscription apps, from price and trial disclosure to restore purchases and cancellation, with what Apple and Google require.
What should a mobile app paywall get right?
A compliant, trustworthy paywall states what the subscriber gets, the full price actually charged and how often, that it renews automatically, the trial length and what happens when it ends, and how to cancel. It offers a visible way to restore purchases and to continue without paying where the app allows, avoids designs that cause accidental purchases, and is fully localised. Apple and Google both review paywalls against their own rules, and unclear paywalls are a common reason for rejection, refunds and complaints.
This list is for founders, product managers and mobile developers preparing a subscription app for launch. It distinguishes binding store requirements from good practice. Store rules were checked against Apple's App Review Guidelines and Google Play's subscriptions policy on 28 October 2026; they change, so re-check before submitting. For choosing a business model in the first place, see how to monetise a mobile app.
What the subscriber gets
1. A clear description of the value. Apple's guideline 3.1.2(c) says that before asking a customer to subscribe, you should clearly describe what the user will get for the price: how much storage, which features, what kind of access. Name the specific features unlocked, not "Go Premium".
2. Ongoing value for a recurring charge. Apple requires auto-renewable subscriptions to provide ongoing value, last at least seven days and work across the user's devices. If the value is a one-off unlock, a one-time purchase may suit better.
3. No extra tasks to get what was paid for. Apple's guidelines say subscribers should get what they paid for without extra tasks such as posting on social media or uploading contacts.
Price and terms
4. The actual amount charged, prominently. Show the price billed and the billing period ("₹2,999 per year"). A per-month equivalent can appear as secondary information. Google Play lists annual plans that prominently show a monthly price instead of the actual charge as a violation.
5. Auto-renewal stated plainly. Say that the subscription renews automatically until cancelled. Google Play cites monthly subscriptions that do not tell users they will renew and be charged each month as a violation.
6. Trial terms in full. Google Play requires the trial length, what it unlocks, when it converts to a paid subscription, the price after the trial and how to cancel before it ends. Do not label a product "Free Trial" if it renews into a paid charge; Google lists that as a violation too.
7. Localised prices and text. Google Play requires subscription pricing and terms to be fully localised, including language and currency. Use the store's localised price strings rather than converting prices yourself.
Controls the user needs
8. Restore purchases. Apple says you should have a restore mechanism for restorable in-app purchases. Put "Restore purchases" on the paywall or in settings so people who reinstall or change devices can regain access.
9. Manage and cancel. Google Play requires an easy online way to cancel or manage the subscription from the app's account settings or an equivalent page, such as a link to the Play subscription centre. On iOS, link to the system subscription management screen. See cancellation flow design for the same principles on the web.
10. A visible way to continue without subscribing. If the app has free features, make the close or "continue with free" option clear. Hidden close buttons frustrate users and invite review complaints; Apple's guidelines prohibit tricking users into subscribing.
Design and operations
11. No accidental purchases. Google lists purchase flows where repeated taps in the same area lead to accidental subscriptions as a violation. Do not put the purchase button where the onboarding "Next" button was, and make the selected plan obvious.
12. Entitlements that match the store. Your backend must know who is subscribed, including renewals, cancellations, refunds, billing retries and grace periods, using the stores' server notifications and purchase verification. A paywall that unlocks features based only on what the device says can be bypassed and drifts out of sync. Plan this with the rest of the first release.
Launching a subscription app?
ZSpace Labs designs and builds iOS and Android apps with store billing, entitlement handling and paywall flows that follow store rules. See our mobile app development service.
Pre-submission checklist
"Required" means the store's own rules ask for it; "good practice" is our recommendation.
| Detail | Apple | Google Play |
|---|---|---|
| 1. What the user gets, described | Required (3.1.2(c)) | Required (offer terms) |
| 2. Ongoing value; period of at least 7 days | Required (3.1.2(a)) | Good practice |
| 3. No extra tasks to unlock paid features | Required (3.1.2(a)) | Good practice |
| 4. Actual charged price prominent | Good practice; no misleading terms | Required (listed violation) |
| 5. Auto-renewal stated | Required by store terms | Required |
| 6. Full trial terms | Trial set up in App Store Connect; describe clearly | Required |
| 7. Localised price and text | Use store price strings | Required |
| 8. Restore purchases | Required for restorable purchases (3.1.1) | Good practice |
| 9. Manage and cancel link | Good practice | Required |
| 10. Continue without subscribing (if free tier) | No tricks (3.1.2(a)) | Good practice |
| 11. No accidental purchase layouts | No bait-and-switch | Required (listed violation) |
| 12. Server-side entitlements | Good practice | Good practice |
Common mistakes
- Showing a paywall before the user has seen any value, then measuring only conversion rate rather than refunds and retention.
- Small, low-contrast text for the price and renewal terms.
- Testing only one country and currency.
- Forgetting to handle refunds and revoked purchases on the backend.
- Changing paywall copy without re-checking store rules, especially for trials.
Conclusion
A good paywall is clear about value, price, renewal, trial and cancellation, gives people a way to restore and to leave, and is backed by reliable server-side entitlements. That keeps you within store rules and reduces refunds and complaints. For the privacy disclosures that go alongside, see mobile app privacy before launch.
Sources
Apple App Review Guidelines, 3.1.1 In-App Purchase and 3.1.2 Subscriptions. Google Play Console Help, subscriptions policy. Accessed 28 October 2026.
Common questions.
Apple's App Review Guidelines say you should make sure you have a restore mechanism for any restorable in-app purchases, which includes subscriptions. A visible Restore Purchases option on the paywall or in settings is the usual way to meet that.