You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>In-app products are the digital goods that you offer for sale from inside your
90
-
application to users. Examples of digital goods includes in-game currency,
91
-
application feature upgrades that enhance the user experience, and new content
89
+
<p>In-app products are the digital goods that you offer for sale from inside your
90
+
application to users. Examples of digital goods includes in-game currency,
91
+
application feature upgrades that enhance the user experience, and new content
92
92
for your application.</p>
93
-
<p>You can use In-app Billing to sell only digital content.
94
-
You cannot use In-app Billing to sell physical goods, personal services, or
95
-
anything that requires physical delivery. Unlike with priced applications, once
93
+
<p>You can use In-app Billing to sell only digital content.
94
+
You cannot use In-app Billing to sell physical goods, personal services, or
95
+
anything that requires physical delivery. Unlike with priced applications, once
96
96
the user has purchased an in-app product there is no refund window.</p>
97
-
<p>Google Play does not provide any form of content delivery. You are
98
-
responsible for delivering the digital content that you sell in your
99
-
applications. In-app products are always explicitly associated with one and
100
-
only one app. That is, one application cannot purchase an in-app product
97
+
<p>Google Play does not provide any form of content delivery. You are
98
+
responsible for delivering the digital content that you sell in your
99
+
applications. In-app products are always explicitly associated with one and
100
+
only one app. That is, one application cannot purchase an in-app product
101
101
published for another app, even if they are from the same developer.</p>
102
102
103
103
<h3 id="prodtypes">Product types</h3>
104
-
<p>In-app Billing supports different product types to give you flexibility in
105
-
how you monetize your application. In all cases, you define your products using
104
+
<p>In-app Billing supports different product types to give you flexibility in
105
+
how you monetize your application. In all cases, you define your products using
106
106
the Google Play Developer Console.</p>
107
-
<p>You can specify these types of products for your In-app Billing application
108
-
— <em>managed in-app products</em> and <em>subscriptions</em>. Google Play
109
-
handles and tracks ownership for in-app products and subscriptions on your
107
+
<p>You can specify these types of products for your In-app Billing application
108
+
— <em>managed in-app products</em> and <em>subscriptions</em>. Google Play
109
+
handles and tracks ownership for in-app products and subscriptions on your
110
110
application on a per user account basis. <a href="{@docRoot}google/play/billing/api.html#producttypes">Learn more about the product types supported by In-app Billing Version 3</a>.</p>
111
111
112
112
<h2 id="console">Google Play Developer Console</h2>
113
-
<p>The Developer Console is where you can publish your
114
-
In-app Billing application, and manage the various in-app products that are
113
+
<p>The Developer Console is where you can publish your
114
+
In-app Billing application, and manage the various in-app products that are
115
115
available for purchase from your application.</p>
116
-
<p>You can create a product list of
117
-
digital goods that are associated with your application, including items for
118
-
one-time purchase and recurring subscriptions. For each item, you can define
119
-
information such as the item’s unique product ID (also called its SKU), product
120
-
type, pricing, description, and how Google Play should handle and track
116
+
<p>You can create a product list of
117
+
digital goods that are associated with your application, including items for
118
+
one-time purchase and recurring subscriptions. For each item, you can define
119
+
information such as the item’s unique product ID (also called its SKU), product
120
+
type, pricing, description, and how Google Play should handle and track
121
121
purchases for that product.</p>
122
-
<p>You can also create test accounts to authorize
122
+
<p>You can also create test accounts to authorize
123
123
access for testing applications that are unpublished.</p>
124
-
<p>To learn how to use the Developer Console to configure your in-app
<p>Google Play uses the same checkout backend service as is used for application
130
+
<p>Google Play uses the same checkout backend service as is used for application
131
131
purchases, so your users experience a consistent and familiar purchase flow.</p>
132
132
<p class="note"><strong>Important:</strong> You must have a Google Wallet
133
133
merchant account to use the In-app Billing service on Google Play.</p>
134
-
<p>To initiate a purchase, your application sends a billing request for a
135
-
specific in-app product. Google Play then handles all of the checkout details for
136
-
the transaction, including requesting and validating the form of payment and
137
-
processing the financial transaction.</p>
138
-
<p>When the checkout process is complete,
139
-
Google Play sends your application the purchase details, such as the order
140
-
number, the order date and time, and the price paid. At no point does your
141
-
application have to handle any financial transactions; that role is provided by
134
+
<p>To initiate a purchase, your application sends a billing request for a
135
+
specific in-app product. Google Play then handles all of the checkout details for
136
+
the transaction, including requesting and validating the form of payment and
137
+
processing the financial transaction.</p>
138
+
<p>When the checkout process is complete,
139
+
Google Play sends your application the purchase details, such as the order
140
+
number, the order date and time, and the price paid. At no point does your
141
+
application have to handle any financial transactions; that role is provided by
142
142
Google Play.</p>
143
143
144
144
<h2 id="samples">Sample Application</h2>
145
-
<p>To help you integrate In-app Billing into your application, the Android SDK
146
-
provides a sample application that demonstrates how to sell in-app products and subscriptions
145
+
<p>To help you integrate In-app Billing into your application, the Android SDK
146
+
provides a sample application that demonstrates how to sell in-app products and subscriptions
147
147
from inside an app.</p>
148
148
149
-
<p>The <a href="{@docRoot}training/in-app-billing/preparing-iab-app.html#GetSample">TrivialDrive sample for the Version 3 API</a> sample shows how to use the In-app Billing Version 3 API
150
-
to implement in-app product and subscription purchases for a driving game. The
151
-
application demonstrates how to send In-app Billing requests, and handle
152
-
synchronous responses from Google Play. The application also shows how to record
153
-
item consumption with the API. The Version 3 sample includes convenience classes
154
-
for processing In-app Billing operations as well as perform automatic signature
149
+
<p>The <a href="{@docRoot}training/in-app-billing/preparing-iab-app.html#GetSample">TrivialDrive sample for the Version 3 API</a> sample shows how to use the In-app Billing Version 3 API
150
+
to implement in-app product and subscription purchases for a driving game. The
151
+
application demonstrates how to send In-app Billing requests, and handle
152
+
synchronous responses from Google Play. The application also shows how to record
153
+
item consumption with the API. The Version 3 sample includes convenience classes
154
+
for processing In-app Billing operations as well as perform automatic signature
155
155
verification.</p>
156
156
157
-
<p class="caution"><strong>Recommendation</strong>: Make sure to obfuscate the
157
+
<p class="caution"><strong>Recommendation</strong>: Make sure to obfuscate the
158
158
code in your application before you publish it. For more information, see
<p>If you have an existing In-app Billing implementation that uses Version 2 or
164
-
earlier, it is strongly recommended that you migrate to <a href="{@docRoot}google/play/billing/api.html">In-app Billing Version 3</a> at your earliest convenience.</p>
163
+
<p>The In-app Billing Version 2 API is deprecated and will be discontinued in January 2015.
164
+
If you have an existing In-app Billing implementation that uses API Version 2 or
165
+
earlier, you must migrate to <a href="{@docRoot}google/play/billing/api.html">In-app Billing Version
166
+
3</a>.</p>
165
167
166
168
<p>If you have published apps selling in-app products, note that:</p>
167
169
<ul>
168
-
<li>Managed items and subscriptions that you have previously defined in the Developer Console will
170
+
<li>Managed items and subscriptions that you have previously defined in the Developer Console will
169
171
work with Version 3 as before.</li>
170
-
<li>Unmanaged items that you have defined for existing applications will be
171
-
treated as managed products if you make a purchase request for these items using
172
-
the Version 3 API. You do not need to create a new product entry in Developer
173
-
Console for these items, and you can use the same product IDs to purchase these
174
-
items. They will still continue to be treated as unmanaged items if you make a
175
-
purchase request for them using the Version 2 or earlier API.
172
+
<li>Unmanaged items that you have defined for existing applications will be
173
+
treated as managed products if you make a purchase request for these items using
174
+
the Version 3 API. You do not need to create a new product entry in Developer
175
+
Console for these items, and you can use the same product IDs to purchase these
176
+
items. They will still continue to be treated as unmanaged items if you make a
177
+
purchase request for them using the Version 2 or earlier API.
0 commit comments