In-App Purchases and Subscriptions: Choosing the Right Model
One-time purchase or subscription for monetizing your app? What to watch regarding store rules, server-side validation and user experience, explained step by step.
There are several ways to earn from your app: paid downloads, ads, in-app purchases and subscriptions. For digital content and features, the stores generally require their own payment systems to be used. In this article we cover the two most common models and points to watch during implementation.
Know the models
- Consumables: products that run out as they are used, such as game currency or credits.
- Non-consumables: one-time products such as an ad-free version or unlocking a permanent feature.
- Subscriptions: access that renews monthly or yearly and keeps delivering value.
Which one suits you?
If value is delivered once, a one-time purchase is natural. If you offer ongoing new content, a service or a benefit with server costs, a subscription makes more sense. Do not choose a subscription only because revenue is easier to forecast; if users do not feel they get value every month, they cancel.
Follow store rules
Apple and Google set rules for selling digital goods, subscription disclosure and cancellation flows. Different rules may apply to physical goods and services (for example a product shipped by courier). Read the rules from the current guidelines and check them before submission; a wrong payment flow can lead to rejection.
- Show price, duration and renewal terms clearly.
- Always offer a "Restore purchases" option.
- Make it clear how the user can cancel the subscription.
Server-side validation
Do not accept that a purchase succeeded based only on information from the client. Send the receipt or purchase token to your own server, verify it with the store's validation services and grant access only then. If you listen to the stores' server notifications, you learn about events such as renewals, cancellations and refunds.
User experience
A paywall should not scare the user. Show the value first, then present the purchase screen. If you offer a trial, state the end date clearly. A hard-to-find cancellation flow may bring revenue in the short term but damages the store rating and trust.
Testing and measurement
Try purchase, renewal and cancellation flows in the stores' test environments. Track the share of users who view the paywall, start a purchase and complete it. Test pricing and package presentation with one change at a time.
Legal and financial side
Taxation of your sales revenue, invoicing and store commissions vary by business. You should work with your accountant on this; we can only help with the technical implementation.
Conclusion
A good revenue model is one that offers users fair value and is built soundly in technical terms. To set up purchase and subscription infrastructure in your app, see our mobile app service or get in touch.





















