This documentation provides technical reference information for using the In-app Billing Version 3 API.
Server Response Codes
The following table lists all of the server response codes that are sent from Bazaar to your application. Bazaar sends the response code synchronously as an integer mapped to the
RESPONSE_CODE key in the response
Bundle. Your application must handle all of these response codes.
Table 1. Summary of response codes for In-app Billing Version 3 API calls.
|1||User pressed back or canceled a dialog|
|3||Billing API version is not supported for the type requested|
|4||Requested product is not available for purchase|
|5||Invalid arguments provided to the API. This error can also indicate that the application was not correctly signed or properly set up for In-app Billing in Bazaar, or does not have the necessary permissions in its manifest|
|6||Fatal error during the API action|
|7||Failure to purchase since item is already owned|
|8||Failure to consume since item is not owned|
The In-app Billing Version 3 API is defined in the
IInAppBillingService.aidl file, which is included with the Version 3 sample application.
The getSkuDetails() method
This method returns product details for a list of product IDs. In the response
Bundle sent by Bazaar, the query results are stored in a String
ArrayList mapped to the
DETAILS_LIST key. Each String in the details list contains product details for a single product in JSON format. The fields in the JSON string with the product details are summarized in table 2.
Table 2. Description of JSON fields with product item details returned from a
|The product ID for the product.|
|Value must be “inapp” for an in-app purchase type.|
|Formatted price of the item, including its currency sign. The price does not include tax.|
|Title of the product.|
|Description of the product.|
The getBuyIntent() method
This method returns a response code integer mapped to the
RESPONSE_CODE key, and a
PendingIntent to launch the puchase flow for the in-app item mapped to the
BUY_INTENT key. When it receives the
PendingIntent, Bazaar sends a response
Intent with the data for that purchase order. The data that is returned in the response
Intent is summarized in table 3.
Table 3. Response data from an In-app Billing Version 3 purchase request.
|0 if the purchase was success, error otherwise.|
|A String in JSON format that contains details about the purchase order. See table 4 for a description of the JSON fields.|
|String containing the signature of the purchase data that was signed with the private key of the developer.|
Table 4 describes the JSON fields that are returned in the response data for a purchase order.
Table 4. Descriptions of the JSON fields for
|A unique order identifier for the transaction.|
|The application package from which the purchase originated.|
|The item's product identifier. Every item has a product ID, which you must specify in the application's product list on the Bazaar publisher site.|
|The time the product was purchased, in milliseconds since the epoch (Jan 1, 1970).|
|The purchase state of the order. Possible values are 0 (purchased), 1 (canceled), or 2 (refunded).|
|A developer-specified string that contains supplemental information about an order. You can specify a value for this field when you make a |
|A token that uniquely identifies a purchase for a given item and user pair.|
The getPurchases() method
This method returns the current un-consumed products owned by the user. Table 5 lists the response data that is returned in the
Table 5. Response data from a
|0 if the request was successful, error otherwise.|
|String containing a continuation token to retrieve the next set of in-app products owned by the user. This is only set by the Bazaar service if the number of products owned by the user is very large. When a continuation token is present in the response, you must make another call to |
Was this content helpful?
Write your comment here...
If you have any comment on this content or any idea to make it better, use this form to send us your comment.
Publish Date: 1400-03-29 07:35
Latest Update: 1400-04-11 12:32