https://support.google.com/googleplay/android-developer/answer/2481797?hl=en

Preparing Your In-app Billing Application

PREVIOUSNEXT

THIS LESSON TEACHES YOU TO

1. Download the Sample App
2. Add Your App to the Developer Console
3. Add the In-app Billing Library
4. Set the Billing Permission
5. Initiate a Connection with Google Play

YOU SHOULD ALSO READ

• In-app Billing Overview

Before you can start using the In-app Billing service, you'll need to add the library that contains the In-app Billing Version 3 API to your Android project. You also need to set the permissions for your application to communicate with Google Play. In addition, you'll need to establish a connection between your application and Google Play. You should also verify that the In-app Billing API version that you are using in your application is supported by Google Play.

Download the Sample Application

---

In this training class, you will use a reference implementation for the In-app Billing Version 3 API called the TrivialDrivesample application. The sample includes convenience classes to quickly set up the In-app Billing service, marshal and unmarshal data types, and handle In-app Billing requests from the main thread of your application.

To download the sample application:

1. Open the Android SDK Manager.
2. In the SDK Manager, expand the Extras section.
3. Select Google Play Billing Library.
4. Click Install packages to complete the download.

The sample files will be installed to <sdk>/extras/google/play_billing/.

Add Your Application to the Developer Console

---

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 Walletmerchant account.
2. 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.
3. In the All Applications tab, add a new application entry.
   1. Click Add new application.
   2. Enter a name for your new In-app Billing application.
   3. Click Prepare Store Listing.
4. In the Services & APIs tab, find and make a note of the public license key that Google Play generated for your application. This is a Base64 string that you will need to include in your application code later.

Your application should now appear in the list of applications in Developer Console.

Add the In-app Billing Library

---

To use the In-app Billing Version 3 features, you must add the IInAppBillingService.aidl file to your Android project. This Android Interface Definition Language (AIDL) file defines the interface to the Google Play service.

You can find the IInAppBillingService.aidl file in the provided sample app. Depending on whether you are creating a new application or modifying an existing application, follow the instructions below to add the In-app Billing Library to your project.

New Project

To add the In-app Billing Version 3 library to your new In-app Billing project:

1. Copy the TrivialDrive sample files into your Android project.
2. Modify the package name in the files you copied to use the package name for your project. In Eclipse, you can use this shortcut: right-click the package name, then select Refactor > Rename.
3. Open the AndroidManifest.xml file and update the package attribute value to use the package name for your project.
4. Fix import statements as needed so that your project compiles correctly. In Eclipse, you can use this shortcut: press Ctrl+Shift+O in each file showing errors.
5. Modify the sample to create your own application. Remember to copy the Base64 public license key for your application from the Developer Console over to your MainActivity.java.

Existing Project

To add the In-app Billing Version 3 library to your existing In-app Billing project:

1. Copy the IInAppBillingService.aidl file to your Android project.
   • In Android Studio: Create a directory named aidl under src/main, add a new packagecom.android.vending.billing in this directory, and import the IInAppBillingService.aidl file into this package.
   • In Eclipse: Import the IInAppBillingService.aidl file into your /src directory.
   • In other dev environments: Create the following directory /src/com/android/vending/billing and copy the IInAppBillingService.aidl file into this directory.
2. Build your application. You should see a generated file named IInAppBillingService.java in the /gendirectory of your project.
3. Add the helper classes from the /util directory of the TrivialDrive sample to your project. Remember to change the package name declarations in those files accordingly so that your project compiles correctly.

Your project should now contain the In-app Billing Version 3 library.

Set the Billing Permission

---

Your app needs to have permission to communicate request and response messages to the Google Play’s billing service. To give your app the necessary permission, add this line in your AndroidManifest.xml manifest file:

<uses-permission android:name="com.android.vending.BILLING" />

Initiate a Connection with Google Play

---

You must bind your Activity to Google Play’s In-app Billing service to send In-app Billing requests to Google Play from your application. The convenience classes provided in the sample handles the binding to the In-app Billing service, so you don’t have to manage the network connection directly.

To set up synchronous communication with Google Play, create an IabHelper instance in your activity'sonCreate method. In the constructor, pass in the Context for the activity, along with a string containing the public license key that was generated earlier by the Google Play Developer Console.

Security Recommendation: It is highly recommended that you do not hard-code the exact public license key string value as provided by Google Play. Instead, you can construct the whole public license key string at runtime from substrings, or retrieve it from an encrypted store, before passing it to the constructor. This approach makes it more difficult for malicious third-parties to modify the public license key string in your APK file.

IabHelper mHelper;
@Override
public void onCreate(Bundle savedInstanceState) {
   // ...
   String base64EncodedPublicKey;

   // compute your public key and store it in base64EncodedPublicKey
   mHelper = new IabHelper(this, base64EncodedPublicKey);
}

Next, perform the service binding by calling the startSetup method on the IabHelper instance that you created. Pass the method an OnIabSetupFinishedListener instance, which is called once the IabHelpercompletes the asynchronous setup operation. As part of the setup process, the IabHelper also checks if the In-app Billing Version 3 API is supported by Google Play. If the API version is not supported, or if an error occured while establishing the service binding, the listener is notified and passed an IabResult object with the error message.

mHelper.startSetup(new IabHelper.OnIabSetupFinishedListener() {
   public void onIabSetupFinished(IabResult result) {
      if (!result.isSuccess()) {
         // Oh noes, there was a problem.
         Log.d(TAG, "Problem setting up In-app Billing: " + result);
      }
         // Hooray, IAB is fully set up!
   }
});

If the setup completed successfully, you can now use the mHelper reference to communicate with the Google Play service. When your application is launched, it is a good practice to query Google Play to find out what in-app items are owned by a user. This is covered further in the Query Purchased Items section.

Important: Remember to unbind from the In-app Billing service when you are done with your activity. If you don’t unbind, the open service connection could cause your device’s performance to degrade. To unbind and free your system resources, call the IabHelper's dispose method when your Activity is destroyed.

@Override
public void onDestroy() {
   super.onDestroy();
   if (mHelper != null) mHelper.dispose();
   mHelper = null;
}