Microtransactions: What They Are and How Games Use Them

Microtransactions are small purchases made inside a game or app after it has been installed. The player pays for content, currency, time savings or a chance-based item, usually through the platform's built-in payment system. The amount per purchase is small, but the model earns because a small share of players buys repeatedly.

This guide covers how microtransactions in games are structured, how studios decide what to sell, what each model does to retention and revenue, and where the model goes wrong. It is written for indie developers and small studios who need to pick a system and defend it.

What counts as a microtransaction

A microtransaction is a purchase tied to a single game or app account, delivered digitally, and priced low enough that the buyer does not need to plan for it. That separates it from a full game purchase, a subscription, or a one-off expansion.

The purchase can be a direct item (a skin, a level pack, a character), a soft or hard currency bundle, a time-saver (extra lives, faster building), or a randomized reward. It can also be a removal fee, such as paying to drop ads. What all of these share is that the player already has the game and is paying to change how it plays.

Three properties define the category in practice:

• Delivered in-app. The purchase runs through the store's billing, not a separate checkout.
• Repeatable. The player can buy again, often many times, which is what makes the model a revenue stream rather than a sale.
• Consumable or durable. Consumables are used up (currency, energy, boosters). Durables stay (skins, unlocks, battle pass tiers). The mix decides how predictable your revenue is.

How microtransactions in games actually earn

Most games with microtransactions earn from a minority of players. The standard way to see this is the payer conversion rate: payers divided by active players. In most free-to-play games this figure is in the low single-digit percentages. A useful rule of thumb for planning is that conversion, average revenue per paying user, and retention multiply together, so improving any one of them lifts revenue without needing more installs.

Two numbers drive the model more than any other:

• ARPPU (average revenue per paying user): total revenue divided by the number of paying users in the period. It tells you how much each buyer spends.
• ARPU (average revenue per user): total revenue divided by all active users. It tells you what each install is worth, and it is the number you compare against your cost per install.

ARPU is the one that decides whether paid acquisition works. If ARPU over the player's lifetime is below the cost of acquiring that player, growth spends money faster than it earns it. Conversion sits between the two: a game can have a high ARPPU and still fail if almost nobody buys.

Revenue also depends on when the player is asked to pay. A first purchase during the first session tends to be the hardest. Many studios design a cheap, clearly valuable first offer (often a starter bundle) to convert a non-payer into a payer, because a player who has bought once is far more likely to buy again than one who never has.

The main microtransaction models and what each one asks of the player

Every model below is a different answer to the same question: what is the player paying for, and why now?

The battle pass deserves separate attention because it changes the shape of revenue. Instead of depending on impulse buys, it sells a season in advance and then pays out over weeks of play. That makes revenue more predictable and gives players a reason to return, but it also commits you to shipping enough content to make each season worth buying.

Loot boxes are the model with the most legal exposure. Several jurisdictions treat paid random rewards as gambling or restrict them, and rules differ by country and by platform. The details vary and change, so check the current rules for each market you ship in on the official regulator or platform policy page before you design the feature.

Designing a store players trust

The pricing page is where most goodwill is won or lost. A store that feels fair converts better over time than one that squeezes a single session.

Start with the value ladder. Decide what a player gets at each price point and make the steps small and clear. A player should be able to understand a bundle's contents in a few seconds without a spreadsheet. Avoid currency packs that leave a balance just short of the item the player actually wants; that pattern reads as manipulation and drives refunds and bad reviews.

Then set your price points against the store's tiers. Mobile app stores and console platforms define price bands and take a commission on each transaction, which reduces what you keep per sale. The commission and tax treatment vary by platform and country, so confirm the current rates in the platform's developer documentation rather than assuming. Price after commission, not before.

Give the player a non-paying path. Games that let dedicated players earn premium items through play keep their free audience engaged, and that audience is what makes the game worth paying into for everyone else. A common split is cosmetics earnable slowly and time savers sold directly.

Finally, show the odds and the contents. Where random rewards are allowed, disclosing drop rates is required in some markets and expected in most. Clear disclosure reduces disputes and is cheaper than handling them later.

A short worked example

These numbers are illustrative, not benchmarks. Take a small mobile puzzle game with 100,000 monthly active players. If 2% convert, that is 2,000 payers. If each payer spends an average of $8 that month, revenue is $16,000. ARPU is $0.16.

Now suppose the studio adds a $4.99 battle pass with a season of rewards. Conversion rises to 3% and average spend per payer to $10. Revenue becomes $30,000 from the same audience, and ARPU nearly doubles to $0.30. No new installs were needed. That is the arithmetic that makes model choice matter more than marketing spend at small scale.

The same math works in reverse. If a studio had raised prices instead of adding a battle pass, it might have lifted ARPPU but lost payers, and the net could be negative. Model changes tend to move conversion; price changes tend to move spend per payer. Test them separately.

Common mistakes

The failures repeat across studios, and most of them are avoidable before launch.

• Selling power in a competitive game. If paying players beat non-payers, the free audience leaves and the pool of future payers shrinks with it.
• Interrupting play to sell. Offer screens placed mid-action cost more in retention than they earn in conversion.
• Pricing without checking the platform cut. A price that looks healthy can leave too little after commission and tax.
• Shipping randomized rewards without checking regional rules. What is allowed in one market may be restricted in another, and retrofitting is expensive.
• Ignoring refunds and chargebacks. Confusing purchases or accidental buys generate disputes that cost fees and can affect your store standing.

Practical takeaway

Pick your model by asking what your players already value: expression in competitive games, progress in strategy games, convenience in casual games. Then check three things before you build the store: the price after platform commission, the conversion you need for the model to earn, and the rules for random rewards in every market you ship to. Measure conversion and ARPPU separately so you know which lever moved. Keep at least one path for non-paying players, disclose what buyers get, and revisit the design each season as your retention data changes.

This article is general information, not financial, legal or tax advice.