Home / Blog / In-app subscriptions: a practical checklist for iOS and Andr

In-app subscriptions: a practical checklist for iOS and Android

6 min read · Published 2026-11-17 · Pixelary Labs

Subscriptions are the most common reason a first release gets stuck in review. The code is rarely the hard part. The hard parts are the store configuration, the wording of the paywall and the way purchases are restored and verified.

Decide the plans before you write code

Write down each plan, what it includes, its price in each market and whether there is a free tier. Changing this after launch is possible, but every change touches store products, the paywall and your support answers.

Keep the number of plans small. Two or three clear choices convert better than a long list, and they are easier to test.

Set up the store products properly

Each subscription has an identifier in App Store Connect and Google Play Console. Create them early, check that they are approved, and use the same identifiers in your app configuration. Sandbox and test accounts let you buy without paying real money.

Both stores take a commission on subscriptions, and small businesses can qualify for reduced rates. Check the current terms on each store, because the figures change and they affect your pricing.

Make the paywall honest

Reviewers look closely at paywalls. The price, the billing period, what is included and how to cancel should be visible without hunting. Vague wording or a hidden free trial is a common reason for rejection.

Show a restore purchases option. It is required on iOS, and users switching phones depend on it.

Verify and track purchases on your side

Do not trust the device alone. Verify purchases with the store's server data, store the subscription status against the user's account, and handle renewals, cancellations and refunds. A mismatch between what the user paid for and what the app unlocks becomes a support problem quickly.

Account deletion is part of the same story. If a user deletes their account, the app must also handle any linked sign-in providers, as the stores require.

Test before submission

Test the full path on real devices with sandbox accounts: buying, cancelling, restoring on a second device, expired subscriptions and a failed payment. Most review problems are found in this step.

Give reviewers a demo account with clear notes on how to reach the paid features. A reviewer who cannot see the premium functions will reject the app.

Next step

If you are planning a subscription app, we can plan the store setup, paywall and purchase handling in the discovery sprint, before the build starts.

Planning something like this?

Plan your subscriptions in a discovery sprint. We reply within two working days.

Start a project