In-App Purchases Overview

The in-app purchase service sells your products for real money through the platform’s own store: Google Play on Android and the App Store on iOS. The SDK starts the store, keeps the list of products on sale up to date, reports every purchase to analytics, and keeps track of every purchase the player paid for until your game delivers it.

How it works

1. You list your products in the Live Ops Dashboard under the IAPConfig module of the Configuration section of your game.
2. When configurations are initialized, the SDK reads that list and starts the store with it. If the list is empty, the store is not started.
3. Every time a newer configuration is applied, the SDK compares the products in it with the ones on sale and updates the store when they differ.
4. Your game reads the products with their store prices and calls Purchase() when the player buys one.
5. You deliver what the player bought and call FinishTransaction(). Until you do, the purchase stays owed to the player, across app restarts.

You never hand the SDK a product list yourself. The products on sale are always the ones in the configuration.

Accessing the service

using PlayOps.InAppPurchases;
using TactileModules.InAppPurchase;

PlayOpsInAppPurchases inAppPurchases = playOpsSDK.InAppPurchases();

The product, transaction and result types live in the TactileModules.InAppPurchase namespace.

Configuration has to be initialized

The store starts when configurations are initialized, not when the SDK is. Make sure your game calls Initialize() on the configuration service at startup:

var configurations = playOpsSDK.Configurations();
configurations.Initialize();

Until then the store has nothing to sell, and every purchase answers StoreUnavailable.

Caution

Subscribe to the in-app purchase events before you call configurations.Initialize(). Initializing configurations is what starts the store, and a purchase the store hands back while it starts is announced only once. See Recovered and Unfinished Purchases.

Which products are sold

Only consumable products are sold. A product in IAPConfig with any other product type, or without an identifier, is skipped and a warning is logged.

Configuring products on the dashboard

1. Go to the Live Ops Dashboard under your game.
2. Open the Configurations service.
3. Search for the IAPConfig module.
4. Configure the products. Each entry in InAppProducts is one product.
5. Publish the configuration. The SDK only receives published configuration, on the game’s next sync. Until you publish, players keep the products they had.

The product identifier

Identifier is only the last part of the product’s store identifier. The SDK builds the rest from your app’s bundle identifier.

Example: tier1 in the game com.company.mygame

The store identifier is your bundle identifier, then .iap., then Identifier.

Where	Correct	Wrong
Identifier on the dashboard	tier1	com.company.mygame.iap.tier1
Product id in Google Play Console and App Store Connect	com.company.mygame.iap.tier1	tier1
GetProduct() in your code	com.company.mygame.iap.tier1	tier1

Bundle identifiers that end with the store name

If your bundle identifier ends with the name of the store the app was installed from (apple on iOS, google or amazon on Android), that last part is left out. A game with the bundle identifier com.company.mygame.amazon, installed from the Amazon Appstore, sells tier1 as com.company.mygame.iap.tier1.

Fields

Field	What the SDK does with it
Identifier	The last part of the store identifier. See The product identifier.
Title	Shown as the product’s Title until the store sends its own.
Description	Only used by the development store, which the SDK uses in the editor and in development builds.
Price	Reported in the purchase analytics events, in cents: 0.99 is reported as 99. The development store also reports it as the store price.
CurrencyCode	Only used by the development store.
FormattedPrice	Shown as the product’s FormattedPrice until the store sends its own price.
Amount	Not read by the SDK.
ProductType	Must be Consumable. Products of any other type are skipped.
OnSale	Not read by the SDK.

What’s next

• Making a Purchase — show products and buy one
• Recovered and Unfinished Purchases — deliver purchases no purchase call is waiting for
• Store State — know whether the store can sell right now
• Purchase Analytics — the events the service reports for you