diff --git a/docs/html/distribute/googleplay/about/monetizing.jd b/docs/html/distribute/googleplay/about/monetizing.jd index 8233a31c04c40..9a5c6d7a6956e 100644 --- a/docs/html/distribute/googleplay/about/monetizing.jd +++ b/docs/html/distribute/googleplay/about/monetizing.jd @@ -138,7 +138,7 @@ Google Play Developer Console.

Monthly payouts in your local currency

To sell products in Google Play, all you have to do is register for a Google -Checkout merchant account and link it to your Google Play Android Developer +Wallet merchant account and link it to your Google Play Android Developer Console account (see Get Started with Publishing for details). Once you’ve set up your account and published your @@ -159,4 +159,4 @@ transaction.

At the close of the month, you can download a complete sales report that gives you the final details of all transactions that closed in the month, including the payout amounts and other data. Additional financial reports are -available in your Google Checkout merchant account.

+available in your Google Wallet merchant account.

diff --git a/docs/html/distribute/googleplay/publish/console.jd b/docs/html/distribute/googleplay/publish/console.jd index 0bf5e78c95c21..3831e51353f8e 100644 --- a/docs/html/distribute/googleplay/publish/console.jd +++ b/docs/html/distribute/googleplay/publish/console.jd @@ -64,8 +64,8 @@ create the store listing page for a specific app.

Linking your Merchant Account

If you want to sell apps or in-app products, you can link your Google -Checkout Merchant account to your developer profile. Google Play uses the linked -Checkout account for financial and tax identification and monthly payouts of +Wallet merchant account to your developer profile. Google Play uses the linked +merchant account for financial and tax identification and monthly payouts of sales.

Your store listing details

diff --git a/docs/html/distribute/googleplay/publish/preparing.jd b/docs/html/distribute/googleplay/publish/preparing.jd index 416f02e0fc244..b4b8c2267b2e7 100644 --- a/docs/html/distribute/googleplay/publish/preparing.jd +++ b/docs/html/distribute/googleplay/publish/preparing.jd @@ -278,7 +278,7 @@ priced). You can also sell in-app products and subscriptions.

If your app is be priced, or if you'll be selling in-app products, -you need set up a Checkout Merchant Account before you can publish.

+you need set up a Google Wallet merchant account before you can publish.

@@ -560,7 +560,7 @@ final checks.

Make sure that:

@@ -119,8 +119,8 @@ In-app Billing.

Google Play Purchase Flow

Google Play uses the same checkout backend service as is used for application purchases, so your users experience a consistent and familiar purchase flow.

-

Important: You must have a Google Checkout -Merchant account to use the In-app Billing service on Google Play.

+

Important: You must have a Google Wallet +merchant account to use the In-app Billing service on Google Play.

To initiate a purchase, your application sends a billing request for a specific in-app product. Google Play then handles all of the checkout details for the transaction, including requesting and validating the form of payment and diff --git a/docs/html/google/play/billing/billing_subscriptions.jd b/docs/html/google/play/billing/billing_subscriptions.jd index 2840dbc60119b..92725cf3c47b7 100644 --- a/docs/html/google/play/billing/billing_subscriptions.jd +++ b/docs/html/google/play/billing/billing_subscriptions.jd @@ -53,7 +53,7 @@ publish. For more information about using the Developer Console, see

When users purchase subscriptions in your apps, Google Play handles all checkout details so your apps never have to directly process any financial transactions. Google Play processes all payments for subscriptions through -Google Checkout, just as it does for standard in-app products and app purchases. +Google Wallet, just as it does for standard in-app products and app purchases. This ensures a consistent and familiar purchase flow for your users.

@@ -137,10 +137,10 @@ original price, but new users will be charged at the new price.

automated recurring billing at either of two intervals:

@@ -154,7 +154,7 @@ cycles will always match subscription cycles, based on the purchase date.

or by Direct Carrier Billing) that was originally used to purchase the subscription.

-

When the subscription payment is approved by Google Checkout, Google Play +

When the subscription payment is approved by Google Wallet, Google Play provides a purchase token back to the purchasing app through the In-app Billing API. Your apps can store the token locally or pass it to your backend servers, which can then use it to validate or cancel the subscription remotely using the

Payment Processing and Policies

In general, the terms of Google Play allow you to sell in-app subscriptions -only through the standard payment processor, Google Checkout. For purchases of +only through the standard payment processor, Google Wallet. For purchases of any subscription products, the transaction fee is the same as the transaction fee for application purchases (30%).

@@ -306,7 +306,7 @@ document.

Subscription order numbers

To help you track transactions relating to a given subscription, Google -Checkout provides a base Merchant Order Number for all recurrences of the +Wallet provides a base Merchant Order Number for all recurrences of the subscription and denotes each recurring transaction by appending an integer as follows:

diff --git a/docs/html/google/play/billing/billing_testing.jd b/docs/html/google/play/billing/billing_testing.jd index 8dcaa86e8aa76..241d45ed96db8 100644 --- a/docs/html/google/play/billing/billing_testing.jd +++ b/docs/html/google/play/billing/billing_testing.jd @@ -77,8 +77,8 @@ reserved product IDs.

When you make an In-app Billing request with this product ID, Google Play responds as though the purchase was refunded. Refunds cannot be initiated through Google Play's in-app billing service. Refunds must be initiated by you (the merchant). After you process a refund - request through your Google Checkout account, a refund message is sent to your application by - Google Play. This occurs only when Google Play gets notification from Google Checkout that + request through your Google Wallet merchant account, a refund message is sent to your application by + Google Play. This occurs only when Google Play gets notification from Google Wallet that a refund has been made. For more information about refunds, see Handling IN_APP_NOTIFY messages and In-app Billing Pricing.

@@ -200,7 +200,7 @@ testing.

To test your In-app Billing implementation with actual in-app purchases, you will need to register at least one test account on the Google Play Developer Console. You cannot use your -developer account to test the complete in-app purchase process because Google Checkout does not let +developer account to test the complete in-app purchase process because Google Wallet does not let you buy items from yourself. If you have not set up test accounts before, see Setting up test accounts.

@@ -208,8 +208,8 @@ accounts.

Also, a test account can purchase an item in your product list only if the item is published. The application does not need to be published, but the item does need to be published.

-

When you use a test account to purchase items, the test account is billed through Google Checkout -and your Google Checkout Merchant account receives a payout for the purchase. Therefore, you may +

When you use a test account to purchase items, the test account is billed through Google Wallet +and your Google Wallet merchant account receives a payout for the purchase. Therefore, you may want to refund purchases that are made with test accounts, otherwise the purchases will show up as actual payouts to your merchant account.

diff --git a/docs/html/google/play/billing/index.jd b/docs/html/google/play/billing/index.jd index 44aa00191e269..1969154f5ea3b 100644 --- a/docs/html/google/play/billing/index.jd +++ b/docs/html/google/play/billing/index.jd @@ -31,7 +31,7 @@ familiar purchase flow.

Any application that you publish through Google Play can implement In-app Billing. No special account or registration is required other than a Google Play Developer Console account and a Google -Checkout merchant account.

+Wallet merchant account.

To help you integrate in-app billing into your application, the Android SDK provides a sample application that demonstrates how to sell standard in-app diff --git a/docs/html/google/play/billing/v2/billing_integrate.jd b/docs/html/google/play/billing/v2/billing_integrate.jd index 15813155446d7..ca41e0b7f471d 100644 --- a/docs/html/google/play/billing/v2/billing_integrate.jd +++ b/docs/html/google/play/billing/v2/billing_integrate.jd @@ -226,7 +226,7 @@ how to do this.

List.

Note: You must publish the items in your product list (sword_001 and potion_001) even though you are not publishing the - sample application. Also, you must have a Google Checkout Merchant account to add items to the + sample application. Also, you must have a Google Wallet merchant account to add items to the sample application's product list.

@@ -239,7 +239,7 @@ onto a device to run it. To run the sample application, do the following:

  1. Make sure you have at least one test account registered under your Google Play publisher account. -

    You cannot purchase items from yourself (Google Checkout prohibits this), so you need to +

    You cannot purchase items from yourself (Google Wallet prohibits this), so you need to create at least one test account that you can use to purchase items in the sample application. To learn how to set up a test account, see Setting up Test @@ -278,7 +278,7 @@ onto a device to run it. To run the sample application, do the following:

  2. Run the application and purchase the sword or the potion.

    When you use a test account to purchase items, the test account is billed through Google - Wallet and your Google Checkout Merchant account receives a payout for the purchase. + Wallet and your Google Wallet merchant account receives a payout for the purchase. Therefore, you may want to refund purchases that are made with test accounts, otherwise the purchases will show up as actual payouts to your merchant account.

diff --git a/docs/html/google/play/billing/v2/billing_subscriptions.jd b/docs/html/google/play/billing/v2/billing_subscriptions.jd index 3bcf212d8a4b3..db18a53f88632 100644 --- a/docs/html/google/play/billing/v2/billing_subscriptions.jd +++ b/docs/html/google/play/billing/v2/billing_subscriptions.jd @@ -65,7 +65,7 @@ responses. Inside the requests and responses are two new fields described below. token, a string value that uniquely identifies (and associates) a user ID and a subscription ID. Google Play generates the purchase token when the user completes the purchase of a subscription product (and payment is approved by -Google Checkout) and then sends it to the purchasing app on the device through the +Google Wallet) and then sends it to the purchasing app on the device through the In-app Billing API.

At the conclusion of a PURCHASE_REQUEST message flow, your app diff --git a/docs/html/tools/workflow/publishing/publishing.jd b/docs/html/tools/workflow/publishing/publishing.jd index 649e80dbace35..ab6321c27c335 100644 --- a/docs/html/tools/workflow/publishing/publishing.jd +++ b/docs/html/tools/workflow/publishing/publishing.jd @@ -83,7 +83,7 @@ to the . After you register you can access the Developer Console, where you can upload applications, configure publishing options, and monitor publishing data. If you want to sell your applications or use the in-app billing feature, you will also need -to set up a Google Checkout merchant account. For more information about the registration process, +to set up a Google Wallet merchant account. For more information about the registration process, see Developer Registration.

@@ -271,7 +271,7 @@ in-app purchases is the same as the transaction fee for application purchases (3

Any application that you publish through Google Play can implement in-app billing. No special account or registration is required other than a Google Play publisher account and a Google -Checkout Merchant account. Also, because the service uses no dedicated framework APIs, you can add +Wallet merchant account. Also, because the service uses no dedicated framework APIs, you can add in-app billing to any application that uses a minimum API level of 4 or higher.

To help you integrate in-app billing into your application, the Android SDK provides a The Google Play Developer Console is where you publish your In-app Billing application and manage the various digital goods that are available for purchase from your application. When you create a new application entry in the Developer Console, it automatically generates a public license key for your application. You will need this key to establish a trusted connection from your application to the Google Play servers. You only need to generate this key once per application, and don’t need to repeat these steps when you update the APK file for your application.

To add your application to the Developer Console:

    -
  1. Go to the Google Play Developer Console site and log in. You will need to register for a new developer account, if you have not registered previously. To sell in-app items, you also need to have a Google Checkout Merchant account.
    2. +
  2. Go to the Google Play Developer Console site and log in. You will need to register for a new developer account, if you have not registered previously. To sell in-app items, you also need to have a Google Wallet merchant account.
  3. Click on Try the new design to access the preview version of the Developer Console, if you are not already logged on to that version.
  4. In the All Applications tab, add a new application entry.