+ The Google Play Developer Console provides a product list for each of your published applications. You can sell an item using Google Play's in-app billing feature only if the item is listed on an application's product list. Each application has its own product list; you cannot sell -items that are listed in another application's product list.
+items that appear on another application's product list. + +
+ You can access an application's product list by clicking the In-App Products link in applications listed in your developer account (see @@ -58,25 +71,17 @@ product description, and price. The product list stores only metadata about the you are selling in your application. It does not store any digital content. You are responsible for storing and delivering the digital content that you sell in your applications.
-
-- Figure 1. You can access an application's product list by clicking the - In-App Products link in the main Apps navigation. -
-You can create a product list for any published application, or any
application in the alpha or beta channels, that's been
uploaded and saved to the Developer Console. However, you must have a Google payments merchant
account and the application's manifest must include the com.android.vending.BILLING
permission. If an application's manifest does not include this permission, you will be able to edit
-existing items in the product list but you will not be able to add new items to the list. For more
+existing items in the product list, but you won't be able to add new items to the list. For more
information about this permission, see
Updating Your
Application's Manifest.
Note: Previously you could test an app by +
Note: Previously, you could test an app by
uploading an unpublished "draft" version. This functionality is no longer
supported; instead, you must publish it to the alpha or beta distribution
channel. For more information, see
- Note: Batch upload of product lists containing subscriptions is not yet supported. Note: Batch upload of product lists containing subscriptions is not yet supported.
+Also, you cannot perform a batch upload containing changes to in-app products that are linked to a
+pricing template.Adding items one at a time to a product list
@@ -107,39 +114,67 @@ number of in-app items.
-- Figure 2. The Add New Product page lets you add items to an - application's product list. -
+
+ You must enter the following information for each item in a product list:
+
+ 
+ You must enter the following information for each item in a product list (see + figures 2 and 3):
Product IDs are unique across an application's namespace. A product ID must start with a lowercase letter or a number, and must be composed using only lowercase letters (a-z), numbers - (0-9), underlines (_), and dots (.). The product ID "android.test" is reserved, as are all - product IDs that start with "android.test."
-In addition, you cannot modify an item's product ID after it is created, and you cannot reuse
+ (0-9), underscores (_), and dots (.). The product ID "android.test" is reserved, as are all
+ product IDs that start with "android.test".
Note: Be sure to plan your product ID namespace carefully. You + cannot modify an item's product ID after it is created, and you cannot reuse a product ID.
The product type can be Managed per user account, - Unmanaged, or Subscription. You can never +
The product type can be Managed product or Subscription. You cannot change an item's product type after you set it. For more information, see - Choosing a product type later in this - document.
+ Choosing a product type. +Note: For subscription items, note that you cannot change the + item's price once you have published it.
An item's publishing state can be Published or Unpublished . To be visible to a user during checkout, an item's publishing state must be set to - Published and the item's application must be published on Google Play.
+ Published, and the item's application must be published on Google Play.Note: This is not true for test accounts. An item is visible to a test account if the application is not published and the item is published. See Testing In-app @@ -147,12 +182,12 @@ number of in-app items.
You can provide localized titles and descriptions for your in-app - products using the Add Translations button. If you want Google Play to translate - your title and description for you, based on the title and description in the - default language, just click the languages that you want to offer. If you want - to provide custom translations in specific languages, you can also do that. By - default, an in-app product inherits its default language from the parent - application.
+ products by selecting Add Translations. If you want Google + Play to translate your title and description for you, based on the title and + description in the default language, just choose the languages that you + want to offer. If you want to provide custom translations in specific + languages, you can also do that. By default, an in-app product inherits its + default language from the parent application.The title is a short descriptor for the item. For example, "Sleeping potion." @@ -166,36 +201,19 @@ number of in-app items.
up to 80 characters in length.You must provide a default price in your home currency. You can also provide prices in other - currencies, but you can do this only if a currency's corresponding country is listed as a - target country for your application. You can specify target countries on the Edit Application - page in the Google Play developer console.
-To specify prices in other currencies, you can manually enter the price for each - currency or you can click Auto Fill and let Google Play do a one-time - conversion from your home currency to the currencies you are targeting (see figure 3).
-For subscription items, note that you can not change the item's price once you have published - it.
+Provide a price in your home currency, or link the price to an existing + pricing template (see figure 4). Based on the price you enter or the prices + from the pricing template, the system autofills country-specific prices for + different currencies. These generated prices use today's exchange rates and + locally-relevant pricing patterns.
+You can also change prices for other currencies manually, but you can do + this only if a currency is used in one of the target countries for your + application. You can specify target countries for your app on the + Pricing & Distribution page in the Google Play + Developer Console.
-- Figure 3. Specifying additional currencies for an in-app product. -
-For more information about product IDs and product lists, see -Creating In-App Product IDs. For more information about pricing, see -In-App Billing Pricing.
- -Note: Be sure to plan your product ID namespace. You cannot reuse -or modify product IDs after you save them.
-To add a batch of items to a product list using a CSV file, you first need to create your CSV @@ -203,17 +221,48 @@ file. The data values that you specify in the CSV file represent the same data v manually through the In-app Products UI (see Adding items one at a time to a product list). -
If you are importing and exporting CSV files with in-app products, please -keep tax-inclusive pricing in mind. If you use auto-fill, you can provide a -tax-exclusive default price and tax-inclusive prices will be auto-filled. If you +
If you are importing and exporting CSV files with in-app products, keep +country-specific pricing in mind. If you use auto-fill, you can provide a +tax-exclusive default price, and tax-inclusive prices will be auto-filled. If you do not use auto-fill, prices you provide must include tax.
Note: Batch upload of product lists containing -subscriptions is not yet supported.
+subscriptions is not yet supported. Also, you cannot perform a batch upload +containing changes to in-app products that are linked to a +pricing template. -The CSV file uses commas (,) and semi-colons (;) to separate data values. -Commas are used to separate primary data values, and semi-colons are used to separate subvalues. For -example, the syntax for the CSV file is as follows: + + +To import the items that are specified in your CSV file, do the following:
+ +The CSV file must be on your local computer or on a local disk that is connected to your + computer.
+This option overwrites values of existing items only if the value of the product_id + in the CSV file matches the In-app Product ID for an existing item in the product list. + Overwriting doesn't delete items that are on a product list but not present in the CSV + file.
+You can also export an existing product list to a CSV file by clicking Export to CSV + on the In-app Product List page. This is useful if you have manually added items to +a product list and you want to start managing the product list through a CSV file.
+ +The CSV file uses commas (,) and semi-colons (;) to separate data values. +Commas are used to separate primary data values, and semi-colons are used to +separate subvalues. For example, the syntax for the CSV file is as follows:
"product_id","publish_state","purchase_type","autotranslate ","locale; title; description","autofill","country; @@ -266,36 +315,39 @@ example, the syntax for the CSV file is as follows:
This is equivalent to the Title setting in the In-app Products UI. If the title contains a semicolon, it must be escaped with a backslash (for example, "\;"). A backslash - should also be escaped with a backslash (for example, "\\">.
+ should also be escaped with a backslash (for example, "\\").This is equivalent to the Description in the In-app Products UI. If the description contains a semicolon, it must be escaped with a backslash (for example, "\;"). A backslash - should also be escaped with a backslash (for example, "\\">.
+ should also be escaped with a backslash (for example, "\\").This is equivalent to clicking Auto Fill in the In-app Products UI. Can be
true or false. The syntax for specifying the country
and price varies depending on which autofill setting you use.
If autofill is set to true, you need to specify only the default
- price in your home currency and you must use this syntax:
"true","default_price_in_home_currency"
If autofill is set to false, you need to specify a country
- and a price for each currency and you must use the following syntax:
"false", "home_country; default_price_in_home_currency; country_2; country_2_price; country_3; country_3_price; ..."
+Note: If you use an autofill value of false
+ and set country prices manually, you must incorporate country-specific
+ pricing patterns, including tax rates, into the prices you provide.
The country for which you are specifying a price. You can only list countries that your application is targeting. The country codes are two-letter uppercase - ISO country codes (such as "US") as defined by + ISO country codes (such as "US"), as defined by ISO 3166-2.
This is equivalent to the Price in the In-app Products UI. The price must be specified in
micro-units. To convert a currency value to micro-units, you multiply the real value by
1,000,000.
- For example, if you want to sell an in-app item for $1.99 you specify 1990000 in the
+ For example, if you want to sell an in-app item for $1.99, you specify 1990000 in the
price field.
To import the items that are specified in your CSV file, do the following:
++ If you sell multiple apps at the same price—or multiple in-app products at + the same price across one or more apps—you can add pricing + templates. These templates make it easier to manage shared prices. +
+ ++ When creating a template, you can provide new pricing information, or you can + apply pricing information from an existing paid app or in-app product. +
+ +
+ + To add a pricing template, do the following: +
The CSV file must be on your local computer or on a local disk that is connected to your - computer.
+This option overwrites values of existing items only if the value of the product_id - in the CSV file matches the In-app Product ID for an existing item in the product list. - Overwriting does not delete items that are on a product list but not present in the CSV - file.
+ ++ If you are adding your first pricing template, the Add a Pricing + Template banner appears. Select Add template to + create a new template. The Pricing Template page + appears. +
+ ++ Otherwise, you see a list of your pricing templates. Select New + pricing template. The Pricing Template page + appears. +
++ Provide details about the template. These details include the name, the + price, and whether to include tax as part of your country-specific + prices. +
++ Based on the price and tax option you provide, the Developer Console + generates prices for international currencies using today's exchange + rates and country-specific pricing patterns. +
+You can also export an existing product list to a CSV file by clicking Export to CSV - on the In-app Product List page. This is useful if you have manually added items to -a product list and you want to start managing the product list through a CSV file.
++ You can link shared prices across paid apps or in-app products to a pricing + template. To complete the linking process, use either the template's + Linked Items tab or the Price section within a paid app or in-app + product's pricing page. +
+ ++ Note: Since a subscription within your app has a constant + price, you cannot link a subscription with a pricing template. You can, + however, import the prices from a template and apply them to a new + subscription. +
+ ++ After you create a pricing template, you can link the prices of in-app + products and paid apps to that template. After completing this linking + process, any changes you make to the pricing template are applied to the + prices of items that you've linked to the template. +
+ +
+ + To link a pricing template to an in-app product, do the following: +
+ ++ To link a pricing template to the price of a paid app, you follow a similar + process. On the pricing template's Linked Items tab, choose a paid + app in the Link Paid Apps section. +
+ ++ After you create a paid app or in-app product, you can link its pricing + information to a pricing template. +
+ +
+ + To link an in-app product to a pricing template, do the following: +
+ ++ To link the price of a paid app to a pricing template, you follow a similar + process within the app's Pricing & Distribution + sub-panel. +
+ ++ As your app evolves, you may find it useful to remove older versions of + in-app products or apps, some of which may be linked to pricing templates. To + delete an in-app product or app that is linked to a pricing template, simply + remove it by completing the following steps. You don't need to unlink the + in-app product or app from the pricing template beforehand. +
+ +
+ + To delete an in-app product that is linked to a template, do the following: +
+ +
+ + To delete a paid app that is linked to a template, do the following: +
+ ++ If you no longer need a pricing template, you can delete it by completing the + following steps: +
+ +An item's product type controls how Google Play manages the purchase of the item. There are several product types, including "managed per user account", "unmanaged," and "subscription." However, @@ -408,8 +780,7 @@ version of In-app BIlling that your app uses.
For details, refer to the documentation for In-app Billing Version -3 or In-app -Billing Version 2. +3.
The Google Play Developer Console provides a public licensing key for each -app. To get the key for an app, follow these steps:
+app. + +
+ To get the key for an app, follow these steps:
Previously, the Developer Console provided a single public key per developer account. To transition apps to the new per-app public key, the Developer Console set the app-specific key as the former developer key. This ensures compatibility for apps that depend on the (former) developer key.
-
-- Figure 4. You can find the license key for each app in the - Services & APIs panel. -
-If you have questions or encounter problems while implementing In-app Billing, contact the diff --git a/docs/html/google/play/billing/billing_overview.jd b/docs/html/google/play/billing/billing_overview.jd index cc564689b5cd5..2954a833f442a 100644 --- a/docs/html/google/play/billing/billing_overview.jd +++ b/docs/html/google/play/billing/billing_overview.jd @@ -122,7 +122,7 @@ the product types supported by In-app Billing Version 3.
The Developer Console is where you can publish your -In-app Billing application, and manage the various in-app products that are +In-app Billing application and manage the various in-app products that are available for purchase from your application.
You can create a product list of digital goods that are associated with your application, including items for @@ -130,6 +130,14 @@ one-time purchase and recurring subscriptions. For each item, you can define information such as the item’s unique product ID (also called its SKU), product type, pricing, description, and how Google Play should handle and track purchases for that product.
+If you sell several of your apps or in-app products at the same price, you +can add pricing templates to manage these price points from a +centralized location. When using pricing templates, you can include the local +tax within the prices you provide, or you can provide prices and have the system +add local taxes to these prices. You can make changes to the prices in your +templates—such as refreshing the exchange rates for certain +countries—and your changes are applied to the apps and in-app products +that you link to the template.
You can also create test accounts to authorize access for testing applications that are unpublished.
To learn how to use the Developer Console to configure your in-app diff --git a/docs/html/google/play/billing/billing_reference.jd b/docs/html/google/play/billing/billing_reference.jd index 45ec7854b59d1..95ab8e57efbc0 100644 --- a/docs/html/google/play/billing/billing_reference.jd +++ b/docs/html/google/play/billing/billing_reference.jd @@ -139,7 +139,8 @@ does not include tax.