-
Notifications
You must be signed in to change notification settings - Fork 3
module InAppBilling.API
- Source:
-
invalid product id passed
- Source:
-
invalid purchase id passed
- Source:
-
the prduct to be bought is not loaded
- Source:
-
Buy or subscribe to an item. The product should be loaded before this call. You can either load items at
initor by callingloadProductDetails.Name Type Description successbuySuccessCallback the callback for successful purchse
failerrorCallback the callback for failed purchase
productIdstring the product's ID to be bought
- Source:
-
Consume an item. The product should be of consumable type.
Name Type Description successconsumeProductSuccessCallback callback for successful consumption
failtype callback for failed consumption
productIdtype id of the already bought product (not the purchase itself)
- Source:
-
Get all the loaded products. Products should be loaded before this call. You can either load items at
initor by callingloadProductDetails.Name Type Description successgetLoadedProductsSuccessCallback callback for successful query
failerrorCallback callback for failed query
- Source:
-
This will return full data of a purchase including its verification payload. Depending on the platform verification payload means either the
purchaseTokenof one single purchase (on PlayStore) or the applicationreceipt(on iTunes).The puchase data should have been loaded before this call using
getPurchases.Name Type Description successgetPurchaseDetailsSuccessCallback failerrorCallback purchaseIdstring - Source:
-
This will return bought products in a chronological order (oldest first) that are not cunsumed or the subscriptions that are not expired. Following items will not appear on this list: - consumable products which has been consumed - products which have been cancelled (as possible in iOS) - subscriptions that are expired
Because of the differences between purchase verification on iOS and android, the verification payload may not be set here. If you need that piece of data reliably on both iOS and andoird, you may ask
getPurchaseDetailsfor full data.This is best practice to always look at this list on startup to activate products in your application.
Name Type Description successgetPurchasesSuccessCallback failerrorCallback - Source:
-
This initiates the plugin, you can optionally pass in one or multiple product IDs for their details to be loaded during initialization.
Name Type Description successinitSuccessCallback the success callback
failerrorCallback the failure callback
optionsObject options for configuring the plugin
Name Type Argument Description showLogBoolean <optional>
[true] wether to show logs or not, this is strongly recommended to be set to false for production
productIdsObject an optional list of product IDs to load after initialization was successful
- Source:
-
Get details for a list of product ids. This will also load the products' details if they are not already loaded. Will only return the product details for the valid product ids. Will also return the items which have been loaded
Name Type Description successloadProductDetailsSuccessCallback callback for successful query
failerrorCallback callback for failed query
productIdsString | Array.<String> - Source:
-
on iOS: Asks store to re-queue previously processed transactions. Use this with caution and don't call it again until you get the callback either on success or on failure.
on Android: This will do the same as
getPurchasesName Type Description successrestoreSuccessCallback failerrorCallback - Source:
Generated with wicked.
- Installation
- [Stores setup](Stores setup)
- [Purchase verification](Purchase verification)
- [Testing plugin](Automatic tests)
- [API documentation](API documentation)
- Debugging
- Roadmap
- [Compatibility issues](Compatibility issues)