flutter_billing
A plugin for Flutter that enables communication with billing API in iOS and Android.
This plugin implements in app purchases rather than Android Pay or Apple Pay. Both Apple and Google collect fees upon each successful transaction made using this plugin.
Warning: This plugin is still under development, some billing features are not available yet and testing has been limited. Feedback and Pull Requests are welcome.
Using
Add flutter_billing
as a dependency in
pubspec.yaml
.
Create an instance of the plugin:
final Billing billing = new Billing(onError: (e) {
// optionally handle exception
});
Request available products for purchase:
final List<BillingProduct> products = await billing.getProducts(<String>[
'my.product.id',
'my.other.product.id',
]);
or
final BillingProduct product = await billing.getProduct('my.product.id');
if (product != null) {
// success
} else {
// something went wrong
}
Request purchased products (each purchase is a product identifier):
final Set<String> purchases = await billing.getPurchases();
Check if a product is already purchased:
final bool purchased = purchases.contains('my.product.id');
or
final bool purchases = await billing.isPurchased('my.product.id');
Purchase a product:
final bool purchased = await billing.purchase(productId);
Limitations
This is just an initial version of the plugin. There are still some limitations:
One time purchase products are not supportedConsumable products are not supportedAndroid subscription are not supportediOS receipt request is not supported- iOS subscriptions are not supported
Libraries
Dart
- dart:ffi
- Foreign Function Interface for interoperability with the C programming language. [...]
- dart:html
- HTML elements and other resources for web-based applications that need to interact with the browser and the DOM (Document Object Model). [...]
- dart:js
- Low-level support for interoperating with JavaScript. [...]
- dart:js_util
- Utility methods to efficiently manipulate typed JSInterop objects in cases where the name to call is not known at runtime. You should only use these methods when the same effect cannot be achieved with @JS annotations. These methods would be extension methods on JSObject if Dart supported extension methods.