One Time Products with RevenueCat
Sell one time products on Android without writing BillingClient glue. The RevenueCat SDK fetches products, launches the purchase, verifies the receipt, and acknowledges or consumes the token for you.
Phase 1: Scope
Answer these before touching code.
Do not call BillingClient.queryProductDetailsAsync, acknowledgePurchase, or consumeAsync yourself once RevenueCat is integrated. The SDK owns the BillingClient instance.
Phase 2: Prepare
- Configure the product in Google Play Console as a one time product.
- In the RevenueCat dashboard, attach the product to an offering and package, and flag it as consumable if it should be consumed on purchase.
- Confirm
Purchases.configureruns once on app start with your Android API key and the current App User ID.
Phase 3: Execute
Fetch offerings, launch the purchase, then read the result off CustomerInfo.
Launch the purchase with awaitPurchase. It suspends until the RevenueCat backend verifies the token.
Read access through entitlements, or fall back to the non subscription transactions list.
The SDK acknowledges non consumables and consumes consumables automatically once the backend verifies the purchase. You do not call acknowledgePurchase or consumeAsync.
Phase 4: Handle Edge Cases
Wrap awaitPurchase to separate cancellation, pending payments, and real errors.
Phase 5: Verify
- Trust
result.customerInfofromawaitPurchase. Do not grant access from optimistic local state. - Pending purchases do not grant entitlements. Register an
UpdatedCustomerInfoListenerso you react when the payment completes. - For server side provisioning, subscribe to the RevenueCat
INITIAL_PURCHASEwebhook. Do not reimplement Google Play Developer API verification.


