Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 683db303 authored by Kevin Hufnagle's avatar Kevin Hufnagle
Browse files

docs: Noted that orderId is blank for all test purchases. 

All test purchases associated with Google Play apps---both one-time
and subscription---now contain a blank "orderId" field. Updated the
documentation accordingly. Also removed the explanation about
canceling test purchases using the merchant center; a lack of an
"orderId" value prevents this workflow from being possible anymore.

Bug: 29068371
Change-Id: I748989c404549769eefd44afa3a7cc125f2e7073
parent 3c8b96ad

docs/html/google/play/billing/billing_admin.jd

+9 −0
Original line number Original line Diff line number Diff line
@@ -747,6 +747,15 @@ you at the conclusion of the purchase flow, as the value of the 
<code>orderId</code> field of the <code>PURCHASE_STATE_CHANGED</code>

<code>orderId</code> field of the <code>PURCHASE_STATE_CHANGED</code>

intent.</p>

intent.</p>





<p class="note">

  <strong>Note:</strong> When a user completes a test purchase, the

  <code>orderId</code> field remains blank. To track test transactions, use

  the <code>purchaseToken</code> field instead. For more information about

  working with test purchases, see <a

  href="{@docRoot}google/play/billing/billing_testing.html">Testing In-app

  Billing</a>.

</p>



<p>In your app, you can use the order number as a general-purpose identifier for

<p>In your app, you can use the order number as a general-purpose identifier for

the in-app purchase transaction. After the purchase, you can use the order

the in-app purchase transaction. After the purchase, you can use the order

number as a means of tracking the transaction in reconciliation reports and for

number as a means of tracking the transaction in reconciliation reports and for

docs/html/google/play/billing/billing_testing.jd

+15 −29
Original line number Original line Diff line number Diff line
@@ -79,14 +79,11 @@ launch. They let authorized user accounts make purchases of your in-app products 
through Google Play without incurring any actual charges to the user

through Google Play without incurring any actual charges to the user

accounts.</p>

accounts.</p>





<p>Once authorized for testing access, those users can make purchases without

<p>

being charged.

  Once authorized for testing access, those users can make purchases without

Test purchases are real orders and Google Play processes them in the same way as

  being charged. The <code>orderId</code> field for test purchases remains

other orders. However, the <code>orderId</code> field for test purchases is

  blank, ensuring that there are no actual charges to user accounts.

blank.

</p>

When purchases are complete, Google Play prevents the orders from

going to financial processing, ensuring that there are no actual charges to user

accounts, and automatically canceling the completed orders after 14 days.</p>





<p class="note">

<p class="note">

  <strong>Note:</strong> Test subscription purchases recur daily, regardless of

  <strong>Note:</strong> Test subscription purchases recur daily, regardless of
@@ -130,8 +127,8 @@ account. Users can confirm the account that is making a purchase by expanding th 
purchase dialog.</p>

purchase dialog.</p>





<p class="note">

<p class="note">

  <strong>Note:</strong> For test subscription purchases, leave the {@code orderId}

  <strong>Note:</strong> For test purchases, leave the {@code orderId} field

  field blank. You can use the {@code purchaseToken} field to identify test purchases.

  blank. You can use the {@code purchaseToken} field to identify test purchases.

</p>

</p>
@@ -150,33 +147,22 @@ with a notice across the center of the purchase dialog, for easy identification. 




<h4 id="cancelling">Canceling completed test purchases</h4>

<h4 id="cancelling">Canceling completed test purchases</h4>

<p>Google Play accumulates completed test purchases for each user but does not

<p>Google Play accumulates completed test purchases for each user but does not

pass them on  to financial processing. Over time, it automatically clears out

pass them on to financial processing.</p>

the purchases by canceling them. </p>





<p>In some cases, you might want to manually cancel a test purchase to continue

<p>In some cases, you might want to manually cancel a test purchase to continue

testing. For canceling purchases, you have these options:</p>

testing. To do so, open the app page in the Play Store. If the test purchase



that you want to cancel is a subscription, you can also use the

<ul>

<li>Wait for the transactions to expire&mdash;Google Play clears completed test

purchases 14 days after their purchase date. </li>

<li>Cancel purchases manually&mdash;you can go to the Google payments merchant

center, look up the transaction, and then cancel it. You can find transactions

by looking up their order numbers.</li>

</ul>



<p>

  You can cancel test subscriptions purchases from the app page in the Play Store,

  or use the 

<a href="https://developers.google.com/android-publisher/api-ref/purchases/subscriptions/cancel">

<a href="https://developers.google.com/android-publisher/api-ref/purchases/subscriptions/cancel">

  {@code cancel}</a> method.

{@code cancel()}</a> method of the Purchases.subscriptions API.

</p>

</ul>





<p class="caution">

<p class="caution">

  <strong>Important:</strong> The

  <strong>Important:</strong> The

  <a href="https://developers.google.com/android-publisher/api-ref/purchases/subscriptions/refund">

  <a href="https://developers.google.com/android-publisher/api-ref/purchases/subscriptions/refund">

  {@code refund}</a> and

  {@code refund()}</a> and

  <a href="https://developers.google.com/android-publisher/api-ref/purchases/subscriptions/revoke">

  <a href="https://developers.google.com/android-publisher/api-ref/purchases/subscriptions/revoke">

  {@code revoke}</a> methods do not support test purchases.

  {@code revoke()}</a> methods of the Purchases.subscriptions API don't support

  test purchases.

</p>

</p>