Hi RevenueCat team,
We’re using Virtual Currencies (beta) for an AI product, and we’ve hit an important gap that I think affects many AI businesses.
For most AI subscription products, usage credits are modeled as a monthly allowance, even when the customer is on an annual plan.
Today, RevenueCat grants currency on purchase/renewal (billing cycle), which means annual subscribers get all credits up front.
That creates two major problems:
- We can’t natively do a monthly drip grant for annual plans (e.g., +X credits each month).
- We can’t natively do monthly expiration/reset of that monthly allowance within an annual subscription.
Because of this, we had to build and maintain external scripts/webhooks to:
- Grant monthly credits to annual subscribers
- Remove/expire prior month’s credits (non-rollover policy)
This is fragile and defeats the purpose of centralizing entitlement + billing logic in RevenueCat.
Feature request
Please add support for sub-cycle virtual currency schedules, such as:
- “For annual product, grant X credits every month”
- Optional rollover behavior:
- no rollover (expire previous month credits)
- limited rollover (N months)
- full rollover
- Optional proration behavior for mid-cycle start/cancel
- Webhook events for scheduled grant/expiry actions
Why this matters
This pattern is standard for AI apps (monthly credit budgets with annual billing discounts), and native support would remove a lot of custom backend complexity and operational risk.
If useful, we’re happy to share our current workaround architecture and edge cases.
Thanks!
