diff options
Diffstat (limited to 'docs/html/google/play/billing/api.jd')
| -rw-r--r-- | docs/html/google/play/billing/api.jd | 49 |
1 files changed, 35 insertions, 14 deletions
diff --git a/docs/html/google/play/billing/api.jd b/docs/html/google/play/billing/api.jd index 9091f51..3d46715 100644 --- a/docs/html/google/play/billing/api.jd +++ b/docs/html/google/play/billing/api.jd @@ -11,12 +11,13 @@ parent.link=index.html <li><a href="#producttypes">Product Types</a> <ol> <li><a href="#managed">Managed In-app Products</a><li> + <li><a href="#subs">Subscriptions</a><li> </ol> </li> <li><a href="#purchase">Purchasing Items</a></li> - <li><a href="#consume">Consuming Items</a> + <li><a href="#consume">Consuming In-app Products</a> <ol> - <li><a href="#consumetypes">Non-consumable and Consumable Items</a><li> + <li><a href="#consumetypes">Non-consumable and Consumable In-app Products</a><li> <li><a href="#managingconsumables">Managing Consumable Purchases</a><li> </ol> </li> @@ -40,11 +41,22 @@ parent.link=index.html <h2 id="producttypes">Product Types</h2> <p>You define your products using the Google Play Developer Console, including product type, SKU, price, description, and so on. For more information, see <a -href="{@docRoot}google/play/billing/billing_admin.html">Administering In-app Billing</a>. The Version 3 API only supports the managed in-app product type.</p> +href="{@docRoot}google/play/billing/billing_admin.html">Administering In-app Billing</a>. The Version 3 API supports managed in-app products and subscriptions.</p> <h3 id="managed">Managed In-app Products</h3> <p>Managed in-app products are items that have their ownership information tracked and managed by Google Play. When a user purchases a managed in-app item, Google Play stores the purchase information for each item on a per-user basis. This enables you to later query Google Play at any time to restore the state of the items a specific user has purchased. This information is persistent on the Google Play servers even if the user uninstalls the application or if they change devices.</p> <p>If you are using the Version 3 API, you can also consume managed items within your application. You would typically implement consumption for items that can be purchased multiple times (such as in-game currency, fuel, or magic spells). Once purchased, a managed item cannot be purchased again until you consume the item, by sending a consumption request to Google Play. To learn more about in-app product consumption, see <a href="#consume">Consuming Items</a></p> +<h3 id="subs">Subscriptions</h3> +<p>A subscription is a product type offered in In-app Billing that lets you sell +content, services, or features to users from inside your app with recurring +monthly or annual billing. You can sell subscriptions to almost any type of +digital content, from any type of app or game. To understand how +subscriptions work, see <a href="{@docRoot}google/play/billing/billing_subscriptions.html">In-app Billing Subscriptions</a>.</p> +<p>With the Version 3 API, you can use the same purchase flow for buying +subscriptions and retrieving subscription purchase information as with in-app +products. For a code example, see <a href="{@docRoot}google/play/billing/billing_integrate.html#Subs">Implementing Subscriptions</a>.</p> +<p class="caution"><strong>Important</strong>: Unlike in-app products, +subscriptions cannot be consumed.</p> <h2 id="purchase">Purchasing Items</h2> @@ -72,29 +84,38 @@ href="{@docRoot}google/play/billing/billing_admin.html">Administering In-app Bil </p> <p>To learn more about the Version 3 API calls and server responses, see <a href="{@docRoot}google/play/billing/billing_reference.html">In-app Billing Reference</a>.</p> -<h2 id="consume">Consuming Items</h2> -<p>You can use the consumption mechanism to track the user's ownership of in-app products.</p> -<p>In Version 3, all in-app products are managed. This means that the user's ownership of all in-app item purchases is maintained by Google Play, and your application can query the user's purchase information when needed. When the user successfully purchases an item, that purchase is recorded in Google Play. Once an item is purchased, it is considered to be "owned". Items in the "owned" state cannot be purchased from Google Play. You must send a consumption request for the "owned" item before Google Play makes it available for purchase again. Consuming the item reverts it to the "unowned" state, and discards the previous purchase data.</p> +<h2 id="consume">Consuming In-app Products</h2> +<p>You can use the consumption mechanism to track the user's ownership of in-app +products.</p> +<p>In Version 3, all in-app products are managed. This means that the user's +ownership of all in-app item purchases is maintained by Google Play, and your +application can query the user's purchase information when needed. When the user +successfully purchases an in-app product, that purchase is recorded in Google +Play. Once an in-app product is purchased, it is considered to be "owned". +In-app products in the "owned" state cannot be purchased from Google Play. You +must send a consumption request for the "owned" in-app product before Google +Play makes it available for purchase again. Consuming the in-app product reverts +it to the "unowned" state, and discards the previous purchase data.</p> <div class="figure" style="width:420px"> <img src="{@docRoot}images/in-app-billing/v3/iab_v3_consumption_flow.png" id="figure2" height="300"/> <p class="img-caption"> <strong>Figure 2.</strong> The basic sequence for a consumption request. </p> </div> -<p>To retrieve the list of product's owned by the user, your application sends a {@code getPurchases} call to Google Play. Your application can make a consumption request by sending a {@code consumePurchase} call. In the request argument, you must specify the item's unique {@code purchaseToken} String that you obtained from Google Play when it was purchased. Google Play returns a status code indicating if the consumption was recorded successfully.</p> +<p>To retrieve the list of product's owned by the user, your application sends a {@code getPurchases} call to Google Play. Your application can make a consumption request by sending a {@code consumePurchase} call. In the request argument, you must specify the in-app product's unique {@code purchaseToken} String that you obtained from Google Play when it was purchased. Google Play returns a status code indicating if the consumption was recorded successfully.</p> -<h3 id="consumetypes">Non-consumable and Consumable Items</h3> +<h3 id="consumetypes">Non-consumable and Consumable In-app Products</h3> <p>It's up to you to decide if you want to handle your in-app products as non-consumable or consumable items.</p> <dl> <dt>Non-consumable Items</dt> -<dd>Typically, you would not implement consumption for items that can only be purchased once in your application and provide a permanent benefit. Once purchased, these items will be permanently associated to the user's Google account. An example of a non-consumable item is a premium upgrade or a level pack.</dd> +<dd>Typically, you would not implement consumption for in-app products that can only be purchased once in your application and provide a permanent benefit. Once purchased, these items will be permanently associated to the user's Google account. An example of a non-consumable in-app product is a premium upgrade or a level pack.</dd> <dt>Consumable items</dt> <dd>In contrast, you can implement consumption for items that can be made available for purchase multiple times. Typically, these items provide certain temporary effects. For example, the user's in-game character might gain life points or gain extra gold coins in their inventory. Dispensing the benefits or effects of the purchased item in your application is called <em>provisioning</em> the in-app product. You are responsible for controlling and tracking how in-app products are provisioned to the users. -<p class="note"><strong>Important:</strong> Before provisioning the consumable item in your application, you must send a consumption request to Google Play and receive a successful response indicating that the consumption was recorded.</p> +<p class="note"><strong>Important:</strong> Before provisioning the consumable in-app product in your application, you must send a consumption request to Google Play and receive a successful response indicating that the consumption was recorded.</p> </dd> </dl> <h3 id="managingconsumables">Managing consumable purchases in your application</h3> -<p>Here is the basic flow for purchasing a consumable item:</p> +<p>Here is the basic flow for purchasing a consumable in-app product:</p> <ol> <li>Launch a purchase flow with a {@code getBuyIntent} call</li> <li>Get a response {@code Bundle}from Google Play indicating if the purchase completed successfully.</li> @@ -102,10 +123,10 @@ href="{@docRoot}google/play/billing/billing_admin.html">Administering In-app Bil <li>Get a response code from Google Play indicating if the consumption completed successfully.</li> <li>If the consumption was successful, provision the product in your application.</li> </ol> -<p>Subsequently, when the user starts up or logs in to your application, you should check if the user owns any outstanding consumable items; if so, make sure to consume and provision those items. Here's the recommended application startup flow if you implement consumable items in your application:</p> +<p>Subsequently, when the user starts up or logs in to your application, you should check if the user owns any outstanding consumable in-app products; if so, make sure to consume and provision those items. Here's the recommended application startup flow if you implement consumable in-app products in your application:</p> <ol> -<li>Send a {@code getPurchases} request to query the owned items for the user.</li> -<li>If there are any consumable items, consume the items by calling {@code consumePurchase}. This step is necessary because the application might have completed the purchase order for the consumable item, but stopped or got disconnected before the application had the chance to send a consumption request.</li> +<li>Send a {@code getPurchases} request to query the owned in-app products for the user.</li> +<li>If there are any consumable in-app products, consume the items by calling {@code consumePurchase}. This step is necessary because the application might have completed the purchase order for the consumable item, but stopped or got disconnected before the application had the chance to send a consumption request.</li> <li>Get a response code from Google Play indicating if the consumption completed successfully.</li> <li>If the consumption was successful, provision the product in your application.</li> </ol> |