In-App Purchases: What They Are and How They Work

In-app purchases are the transactions that happen inside a mobile game after it's already been downloaded — the economic engine beneath free-to-play gaming's surface. They range from a $0.99 coin pack to a $99.99 battle pass bundle, and they account for a substantial portion of mobile gaming revenue globally. The Apple App Store and Google Play both operate distinct purchase frameworks that shape how these transactions are structured, disclosed, and sometimes disputed.

Definition and scope

An in-app purchase (IAP) is any paid transaction initiated from within a mobile application rather than at the point of download. On both iOS and Android platforms, IAPs are processed through the platform's native payment infrastructure — Apple's StoreKit framework or Google Play Billing — rather than through external payment processors. This matters because Apple and Google each take a commission of up to 30% on qualifying transactions (Apple App Store Review Guidelines, §3.1.1; Google Play Billing Policy).

IAPs fall into three structural categories:

  1. Consumables — items that are used up and can be purchased again, such as gems, gold, energy, or ammunition packs.
  2. Non-consumables — permanent unlocks purchased once, such as removing ads or unlocking a character permanently.
  3. Subscriptions — recurring charges (weekly, monthly, or annual) that grant ongoing access to content or benefits.

The scope of the IAP market is significant. Mobile gaming represented approximately 50% of global gaming revenue in 2023, with IAPs driving the majority of that figure (Newzoo Global Games Market Report 2023).

How it works

When a player taps a purchase button inside a game, the game's code passes the transaction request to the platform's billing SDK. The platform authenticates the buyer's stored payment method, processes the charge, and returns a receipt to the game's server. The game server validates that receipt before granting the purchased item — a step that prevents fraudulent or spoofed purchases.

The flow looks like this in practice:

This architecture means the developer never directly handles payment card data. The platform acts as the merchant of record, which is why refund requests for IAPs go through Apple's Report a Problem portal or Google Play's refund interface rather than directly to the game developer. For anyone navigating a disputed charge, mobile game refund policies explains platform-specific timelines and eligibility rules in detail.

Common scenarios

The most familiar IAP scenario in mobile games is the virtual currency layer — a game sells a fictional currency (gems, V-Bucks, coins) at fixed price points, and players spend that currency on items. This two-step conversion obscures the real-money cost of individual items, a practice the FTC has flagged in consumer protection contexts (FTC, Children's Online Privacy).

Gacha mechanics introduce a randomized element, where a purchase delivers a random item from a probabilistic pool rather than a specified item. These are closely related to loot boxes and occupy a contested regulatory space; Japan's Consumer Affairs Agency established guidelines on complete gacha (complete-set gacha) in 2012, classifying it as a form of gambling under certain conditions. For a focused treatment of this category, mobile game loot boxes covers the regulatory landscape and probability disclosure requirements.

Battle passes represent a hybrid model — a seasonal subscription that bundles cosmetic rewards unlocked through gameplay progression. They have largely displaced pure loot boxes in titles aimed at younger audiences because rewards are deterministic rather than random.

Subscriptions differ from the above in one structural way: they renew automatically unless actively cancelled. Both Apple and Google require clear disclosure of renewal terms before purchase, and both platforms provide subscription management interfaces where recurring charges can be reviewed. This connects directly to mobile game subscriptions, which covers cancellation mechanics and billing cycle edge cases.

Decision boundaries

The distinction that matters most for most players is consumable vs. non-consumable. A consumable purchase, by definition, disappears — spending 500 gems on a summon means the gems are gone regardless of the outcome. A non-consumable purchase persists in the account and is typically restorable if the game is reinstalled (Apple's restore purchases mechanism; Google Play's entitlements API).

The second boundary worth understanding is platform vs. developer pricing. Developers set the price tier, but platforms enforce regional pricing conversions. A $4.99 pack in the US might not cost the exact equivalent in Canadian dollars or Euros — platforms maintain localized price sheets that don't always track exchange rates precisely.

The third boundary is age and authorization. Both Apple and Google offer parental controls that require authentication before any IAP is processed — a safeguard directly relevant to the concerns covered in mobile gaming for kids and safety. The FTC has pursued enforcement actions against developers who made IAPs too easy for minors to trigger without parental consent, resulting in settlements that included refund programs for affected families (FTC v. Apple Inc., 2014).

For a broader picture of how IAPs fit alongside other revenue models — ads, premium pricing, subscriptions — mobile game monetization models maps the full ecosystem. The Mobile Game Authority home is the reference point for navigating all of it.


References