App monetisation · 17 Nov 2026 · 6 min read
In-app purchases and subscriptions: basics for founders
Selling digital things inside an app means working with the store's billing, its rules and its support process. This guide explains the moving parts before you design the paywall.
The short answer
In-app purchases are digital goods or access sold inside an app through the store's own billing. The common types are consumables, one-time purchases and auto-renewing subscriptions. The stores set rules on how you describe prices, offer restores and handle refunds, and those rules change, so read the current documentation before you design anything.
In-app purchases start with what you are selling
In-app purchases are payments made inside the app for something digital: extra credits, a feature purchase, removing adverts, a content pack or ongoing access. Before you pick a type, decide what the user actually receives and for how long they keep it. The answer drives the technical set-up, the store product type and what you must tell the user at the point of sale.
Physical goods and real-world services, such as a delivery or a taxi ride, are generally outside this system and are paid for in other ways. The stores' rules about what counts as a digital good and what must use their billing are detailed and they change, so check the current guidelines for each store and ask a qualified adviser if your model is unusual.
What types of in-app purchase exist
| Type | What the user gets | Typical example |
|---|---|---|
| Consumable | Something that is used up and can be bought again | Credits, lives, boosts |
| Non-consumable | A permanent purchase that stays with the account | Removing adverts, adding a pro feature |
| Auto-renewing subscription | Access for a period that renews until cancelled | A fitness plan, a learning library, a premium tier |
| Non-renewing or fixed-term access | Access for a set time with no automatic renewal | A season pass or a one-year course |
Names and exact options differ slightly between Apple and Google, and both add features over time. Treat the table as the idea and the store documentation as the specification. Which type fits depends on whether the value is used once, kept for good or delivered over time.
What the stores require
Both stores have rules for digital purchases, and review can fail on any of them. The themes that come up again and again are these:
- Digital content and features sold inside the app generally have to use the store's own billing system. Exceptions exist and vary by region and over time, so check the current policy for your case.
- Price and term must be clear before the user commits: how much, how often, what is included and how to cancel.
- Users must be able to restore what they have already bought, for example on a new phone, without paying again.
- Free trials and introductory offers must say what happens when they end.
- The store keeps a share of the revenue and publishes the details, which change. Read the current terms before you build a pricing model around them.
Rejections for purchase flows are common enough to be worth planning around. The same review applies to updates, so a changed paywall can be rejected too.
How subscriptions behave over time
A subscription is not a single payment. It is a relationship with a life cycle, and your app has to follow it:
- Start. The user subscribes, possibly with a free trial or an introductory price.
- Renewal. The store charges automatically at each period end and tells your system.
- Failure. If the payment fails, the stores usually allow some retry or grace period. Check how long the current rules allow and decide what the user sees meanwhile.
- Cancellation. Users cancel in their store account, not in your app, and keep access until the paid period ends.
- Resubscribe and upgrade. Users may come back, change plan or switch between tiers.
Your app should always ask what the user currently has, rather than assuming. Many bugs come from an app that remembers a purchase from last month and never learns it ended.
How refunds and restores work
Refunds are handled by the store, not by you. The user asks Apple or Google, the store decides, and your system finds out afterwards, usually through a notification sent to your server. When a refund arrives, the app should remove the benefit. If you give the benefit only on the device without a server check, you will never hear about the refund.
Restores solve a different problem: the user bought something, then reinstalled or changed device. The app needs a clearly labelled way to restore, and the purchase record held by the store lets it re-grant what was already paid for. For subscriptions across several devices or both platforms, you will usually want an account system that links the purchase to the user, which is a backend job described in app backend basics.
Check purchases on the server, not just in the app
If a feature is valuable, assume someone will try to get it without paying. Checking the purchase record with the store from your own server, and granting access from there, is much safer than trusting the app alone. Our guide to mobile app security basics for founders covers the wider habits around keys, tokens and data.
The same server can store which user holds which entitlement, record when it changes and support customer service when someone writes to say their purchase did not arrive.
Design the purchase flow carefully
The purchase screen is where trust is won or lost. Show the plain facts first: the price, the period, what is included and how to cancel. Do not hide the restore option, and do not make a close button hard to find. Placement matters too. Offering a purchase after the user has felt the value of the app converts better in many products than a paywall on the first screen, though this depends on your category and should be tested rather than assumed.
General design habits from app UX basics for first-time founders apply here: short flows, clear labels and no surprises. Remember that prices are shown in the user's local currency and tax treatment varies, so read the price from the store at run time instead of typing it into the app.
Test purchases without spending money
Both stores provide test environments with test accounts so that you can run through purchases, renewals and cancellations without real charges. Subscription periods are shortened in testing, which lets you see a renewal in minutes. Test the unhappy paths too: cancelled payment, interrupted network, a refund and a restore on a second device.
Links from outside the app, such as an email offering a discount, add another case. When they open the app on a particular screen, make sure the purchase state is still read correctly. See deep links and universal links explained.
Releases, price changes and where to go next
New products, changed trial lengths and new tiers usually need an app update as well as store configuration, so plan them with your release schedule. The guide to app updates and versioning explains how that works, including how to keep older versions working.
If you are scoping an app with payments, the mobile app development service page explains how Liftup Technologies approaches app builds. Tax and legal questions about selling digital goods are for a qualified adviser, because they differ by country.
Related guides
- Mobile app development
- App updates and versioning explained
- Mobile app security basics for founders
- App ux basics for first time founders
- Deep Links and Universal Links Explained for App Owners
- App Backend Basics: APIs, Databases and Hosting for Founders
Questions and answers
What types of in-app purchase exist?
The usual types are consumables, which are used up and can be bought again, non-consumables, which are permanent purchases, and auto-renewing subscriptions, which give access for a period and renew until cancelled. Some stores also support fixed-term access with no automatic renewal.
What do the app stores require for in-app purchases?
Digital goods sold in an app generally have to use the store's billing, price and term must be clear before purchase, users need a way to restore past purchases and trials must say what happens afterwards. Details and exceptions change, so read each store's current guidelines.
How do I handle refunds and restores?
Refunds are decided by the store, and your server learns about them through a notification, so the app should remove the benefit when one arrives. Restores let a user regain past purchases on a new device. Offer a clearly labelled restore option and check entitlements from the server.
How do users cancel a subscription?
They cancel in their store account settings, not usually inside your app. They normally keep access until the paid period ends. Your app can explain where to cancel and should check the current subscription state instead of assuming.
Do I need a backend for in-app purchases?
Small apps can start without one, but a backend is the safer route. A server can verify purchases with the store, record who holds what and handle refunds and multi-device access. The more valuable the feature, the stronger the case for it.
Can I test purchases without real payments?
Yes. Both stores offer test environments and test accounts. Test renewals, cancellations, failed payments, refunds and restores on a second device, not just the first successful purchase.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.