Android in-app purchases

Purchases require a separate store integration. Android export and a plugin API do not mean a billing plugin ships with Reckfell. Do not use an invented singleton name or package inherited from an old guide.

Before implementation

Choose a store, compatible plugin or your own SDK bridge. Record its version, methods, signals, Gradle requirements, minimum SDK and release signing requirements. Configure test products and test users through that store.

Handle a purchase

1. Connect to billing and fetch current product details. Display the store-provided price rather than a hard-coded string.
2. Start the flow and handle success, cancellation, failure and pending status. PENDING does not grant entitlement.
3. Send the purchase token to your backend. Verify through the store API and prevent duplicate entitlement for the same token.
4. Grant entitlement once and perform the store-required acknowledgement/consumption. Purchase restoration must not credit a consumable again.
5. Reconcile entitlements when the app resumes; handle refunds and subscription expiry.

For Google Play use the official purchase-verification guidance. Keep server credentials out of the APK. No billing-plugin API, transaction, sandbox or publication was tested for this page; this is an integration procedure, not a supplied payment module.