Handling RevenueCat Refunds and Subscription Access CorrectlyHandling RevenueCat Refunds and Subscription Access Correctly
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A refund does not reach your webhook handler as an expiry. RevenueCat reports a refund from store support as a CANCELLATION event with cancel_reason set to CUSTOMER_SUPPORT, and its event types reference warns that auto-renewal may still be active afterwards.
That makes CANCELLATION the wrong event to revoke on. It also fires when someone simply turns off auto-renew, and that user has paid through to the end of the period. EXPIRATION is the event that means access ended. Revoking on the first BILLING_ISSUE has the same problem, because a store grace period keeps access in place while the payment may still succeed.
What happens after a refund is your product's decision rather than the store's. Write that policy down and let your server apply it to its own access record, instead of assuming the store already removed access. https://www.duskolicanin.com/blog/flutter-subscription-refund-expiry-access
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started