Can customer subscribe to the same subscription if they are already subscribed (opted-out but not expired yet)?

Thanks for the detailed write-up and screenshots!

So, when a customer cancels (opts out of renewal), they don't lose access immediately, they keep their subscription until the end of the paid period and if they resubscribe before that period ends, Google Play allows it and backdates the new subscription to the original renewal date.

That's seems to be why you see a new subscription start and the old one expire at almost the same minute, where Google is aligning the billing cycle.

For this flow, RevenueCat sends specific webhook events:

• CANCELLATION: the customer opted out of renewal, but still has access
• UNCANCELLATION: the customer re-enabled auto-renew before expiration (they never lost access)
• EXPIRATION: access is actually revoked
• RENEWAL: a new billing cycle started. Note that Google Play may classify a resubscription as a RENEWAL rather than an INITIAL_PURCHASE

If your backend is treating CANCELLATION as "revoke premium," that's likely where the sync issue is coming from. You'd want to keep access active on cancellation and only revoke on EXPIRATION. More here: https://www.revenuecat.com/docs/integrations/webhooks/event-types-and-fields#cancellation-and-expiration-reasons

Some extra context on this:

• Common Webhook Flows walks through cancellation, uncancellation, and resubscribe sequences
• Event Types & Fields has the full reference for each event
• Google Play subscription lifecycle on Android's docs also explains the cancel/restore behavior from Google's side

Let me know if you have any questions! Feel free to share the affected App User Ids too, to try and investigate/confirm the Events on the Customer Profile.

Best,

Thank you ​@guilherme for the reply.

I’ve looked at the webhook events and there is no `UNCANCELLATION` event triggered. Also, I only revoke premium access on `EXPIRATION`.

If you look at the second image I shared, The subscription started on `2026-03-07` but user manages to resubscribe again on `2026-03-23` and the expiration happened shortly after that. The monthly subscription cycle was not completed yet.

Where can I share the App User Ids? Is sharing here safe? Also do you need the project ID?

Thanks

Hello ​@guilherme , could you share where can I share the App User Ids with the RC team?

Thank you

Apologies for the delay here!

Feel free to do it here or via our Support Form - make sure to mention this ongoing thread and also mention me too there, so it loops the right folks internally.

Hey all, just wanted to follow up here with an update since we continued this investigation internally.

After digging into the actual events and purchase receipts, it turns out this is a specific Google Play edge case where a user re-subscribes via the in-app paywall (not the Play Store settings) while their cancelled subscription is still active. Google treats that as a brand new purchase, so a new token gets issued and the old one expires almost immediately. That's why you see an EXPIRATION and INITIAL_PURCHASE land within milliseconds of each other, with no UNCANCELLATION in between.

We are working on a fix that would handle this more gracefully and emit a single UNCANCELLATION event for this flow. In the meantime, the safest approach is to call GET /v1/subscribers/{app_user_id} before revoking access on any EXPIRATION, and only revoke if there's no active subscription on the response.

Thanks for your patience on this! Let us know if you have any follow-up questions.