In-app purchase

Also known as: IAP

On this page 7

An in-app purchase (IAP) is a transaction in which a user buys digital goods, features or subscriptions from inside a mobile app, with payment processed by the platform billing system such as Apple StoreKit or Google Play Billing. In mobile distribution, IAP is the dominant monetization model, because it lets an app be downloaded free and earn revenue later from the users who value it most.

The mechanism ties an app closely to its store: the platform handles payment, tax and refunds, takes a commission on each sale and defines which products must use its billing system. Understanding IAP therefore requires both a technical view of purchase flows and a commercial view of store policy, which keeps changing under regulatory pressure.

How an in-app purchase transaction works

An in-app purchase follows a product, purchase, verification and fulfillment sequence. The developer first defines products with identifiers and prices in App Store Connect or Google Play Console. At runtime, the app queries the store for localized product details, presents them, and calls the platform API when the user decides to buy.

The store then shows its own payment sheet, authenticates the user and charges the stored payment method. The app receives a signed transaction or purchase token, which a well-designed system verifies on its own server before unlocking content. Finally the app completes the transaction: on Google Play, purchases must be acknowledged within three days or they are refunded automatically.

The table below lists the stages and the responsibility at each step.

StageResponsible partyKey detail
Product setupDeveloper in the store consoleIdentifiers, price tiers, descriptions
Product queryApp calling the store SDKReturns localized prices and currency
PaymentStore payment sheetAuthentication, tax and charging
VerificationDeveloper serverSignature and status check with store APIs
FulfillmentApp and backendGrant content, then finish or acknowledge
Stages of an in-app purchase flow

Types of in-app purchase products

Stores classify IAP products by how long the entitlement lasts and whether it can be bought again. The classification determines how the app restores purchases, how refunds behave and which server notifications matter. Choosing the wrong type is a common design error that is difficult to correct after launch.

TypeBehaviorTypical use
ConsumableUsed up and can be bought repeatedlyGame currency, extra lives, credits
Non-consumableBought once, owned permanentlyAd removal, premium unlock, level packs
Auto-renewable subscriptionRenews each period until canceledStreaming, cloud storage, productivity tools
Non-renewing subscriptionFixed duration, no automatic renewalSeason passes, time-limited access
In-app purchase product types

Non-consumables and subscriptions must be restorable on a new device, which is why iOS apps typically show a Restore Purchases control. Auto-renewable subscriptions add further states such as free trials, introductory prices, grace periods, billing retry and account hold, each signaled through server notifications.

Store commissions and billing rules

Both major stores apply a standard commission of 30% on digital goods, with a reduced rate of 15% for qualifying smaller developers and for many subscriptions. Store rules require IAP for digital content consumed in the app, while physical goods and real-world services such as ride hailing or food delivery use ordinary payment processors.

Regulation has changed these rules in several markets. The EU Digital Markets Act and court decisions in other jurisdictions have opened room for alternative payment options and links to external purchase pages, typically with different fee structures and disclosure requirements. Because the details differ by country and are still evolving, teams should confirm current terms in each store before designing a payment strategy.

RouteApplies toMain trade-off
Store billing (IAP)Digital goods in most marketsHigh conversion, store commission
Alternative in-app billingMarkets where regulation permits itLower fee, extra compliance work
External purchase linkPermitted regions and app categoriesOwn checkout, more user friction
Direct card paymentPhysical goods and servicesNo store fee, no store refund handling
Payment routes for mobile apps

Implementing in-app purchase securely

Secure IAP depends on server-side validation rather than trusting the client. Jailbroken or rooted devices can tamper with app logic, so any entitlement granted solely on the device can be forged. The backend should verify signed transactions through the App Store Server API or the Google Play Developer API, store entitlements against a user account and listen for server notifications.

Server notifications, called App Store Server Notifications on iOS and Real-time Developer Notifications on Google Play, report renewals, refunds, cancellations and billing problems. Without them, a backend continues granting access after a refund or misses a renewal. The table below maps frequent defects to their causes and fixes.

SymptomLikely causeFix
Users charged but not unlockedTransaction not processed after app restartHandle pending transactions at launch
Automatic refunds on AndroidPurchase never acknowledgedAcknowledge after successful fulfillment
Free premium on rooted devicesClient-only validationVerify on the server
Access after refundNotifications ignoredProcess refund and revocation events
Lost purchases on new phoneNo restore pathImplement restore and account linking
Common in-app purchase defects

Limitations and design considerations

In-app purchase brings convenience and trust to users but limits the developer. The store owns the payment relationship, so the developer often lacks direct customer data, cannot issue refunds freely and depends on store review for product changes. Price points are tied to store price tiers, and currency conversion follows store schedules.

  • Testing is complex: sandbox accounts, license testers and StoreKit configuration files behave differently from production.
  • Cross-platform entitlements need a backend: a purchase made on iOS is not visible to the Android store.
  • Aggressive designs carry risk: loot boxes and manipulative offers attract regulatory scrutiny in several countries.
  • Family sharing and refunds can revoke entitlements that the app must respect.

Related distribution topics such as app review, app rollout and alternative app marketplaces influence IAP directly, since a rejected product or a regional marketplace with its own billing rules changes how revenue reaches the developer.

Understanding it simply

An in-app purchase is buying something extra from inside an app, like coins in a game or a premium plan in a note-taking app. You do not leave the app or type your card details again. The app store already knows how you pay, so it asks for a quick confirmation and charges you.

In exchange for handling the payment, the store keeps a share of the price. The app maker receives the rest and unlocks what you bought. If you get a new phone, purchases that last, such as a premium unlock, can usually be restored without paying again.

Applied in practice

A small studio publishes a meditation app on iOS and Android, free to download with a premium subscription at a monthly price and a discounted annual option with a seven-day free trial. Both plans are defined as auto-renewable subscriptions in the two store consoles with matching product identifiers.

The app sends each purchase token to the studio backend, which verifies it with the store APIs and records the entitlement against the user account. The backend subscribes to server notifications, so when a user requests a refund through the store, premium access is removed within minutes. Because the entitlement lives on the server, a subscriber who switches from an iPhone to an Android tablet signs in and keeps premium access.

As the studio earns well under one million dollars a year, it qualifies for the reduced 15% commission. After six months, trial conversion is stable and the support team receives almost no complaints about missing purchases, which the founders attribute to server-side validation from the first release.