Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
revenuecat avatar

Rc One Time Products

  • 187 installs
  • 55 repo stars
  • Updated August 3, 2026
  • revenuecat/ai-toolkit

Helps with ai & agent building tasks.

About

rc-one-time-products is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • rc-one-time-products
  • AI & Agent Building
  • AI-coding skill

Rc One Time Products by the numbers

  • 187 all-time installs (skills.sh)
  • +28 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #2,995 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-one-time-products

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs187
repo stars55
Last updatedAugust 3, 2026
Repositoryrevenuecat/ai-toolkit

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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.

QuestionDecision
Is the product consumable or non consumable?Mark consumables in the RevenueCat dashboard so the SDK calls consumeAsync for you.
Do you read access through entitlements or transactions?Prefer entitlements so access logic stays decoupled from product IDs.
Do you need server notification of the purchase?Use RevenueCat webhooks. The INITIAL_PURCHASE event fires for every new non subscription purchase.

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.configure runs 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.

val offerings = Purchases.sharedInstance.awaitOfferings()
val pkg = offerings.current?.availablePackages?.first() ?: return

Launch the purchase with awaitPurchase. It suspends until the RevenueCat backend verifies the token.

val result = Purchases.sharedInstance.awaitPurchase(
    PurchaseParams.Builder(activity, pkg).build()
)
val info = result.customerInfo

Read access through entitlements, or fall back to the non subscription transactions list.

val hasAccess = info.entitlements["lifetime_access"]?.isActive == true
val owned = info.nonSubscriptionTransactions
    .any { it.productIdentifier == "lifetime_product_id" }

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.

try { /* awaitPurchase */ } catch (e: PurchasesTransactionException) {
    when {
        e.error.code == PurchasesErrorCode.PaymentPendingError -> showPending()
        e.userCancelled -> Unit
        else -> showError(e.error.message)
    }
}
OutcomeSDK signalAction
SuccessawaitPurchase returns with updated CustomerInfoGrant access from entitlements or nonSubscriptionTransactions.
User cancelPurchasesTransactionException, userCancelled == trueSwallow silently.
Pending paymentPurchasesTransactionException, PaymentPendingErrorShow a pending message. The SDK updates the entitlement later through UpdatedCustomerInfoListener.
Other errorPurchasesTransactionException, other codesSurface e.error.message to you.

Phase 5: Verify

  • Trust result.customerInfo from awaitPurchase. Do not grant access from optimistic local state.
  • Pending purchases do not grant entitlements. Register an UpdatedCustomerInfoListener so you react when the payment completes.
  • For server side provisioning, subscribe to the RevenueCat INITIAL_PURCHASE webhook. Do not reimplement Google Play Developer API verification.

References

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.