RENEWAL event unexpected flow

Question

I have a question regarding a RENEWAL event. Specifically, for Android, when the webhook receives a type=RENEWAL, when should we process it and consider it a real resume of subscription to where entitlements should be granted?
Currently according to the documentation this RENEWAL event should only happen after a SUBSCRIPTION_PAUSED event for Android. Is this correct or can the previous event be of another type? if so, what other types should be supported.

Specific example app user ID: JNhjegTrnBTZIbsYLzZkHPmroOl1

Firstly, Customer History does not even show an event that happened today for RENEWAL:

But as you can see from my database of logs for each webhook event I got this:

Second, is this order expected? After Expiration we would get a renewal or an initial?
Should we proceed with granting entitlements?

wes_clark · Answer

Hi! Thank you for the thorough evidence. I believe that this may just be a situation of the ordering of events in the Customer History view. If you click on the Renewal event, is the event timestamp of the event December 30th? The events are ordered by the purchase date in the Customer History so while the renewal may have happened/been detected on the 30th, the store itself will have treated the purchase date to be the 23rd. I would also be happy to look further on my end to double check. Could you specify which project this is for?

RENEWAL event unexpected flow

1 reply

Most helpful members this week

Cookie policy

Cookie settings

Related topics

RENEWAL event unexpected flow after SUBSCRIPTION_EXTENDEDicon

Unexpected Resubscribe Flowicon

Initial purchase vs renewal events on Android and Iosicon

Mixpanel: Parallel Trial and regular cancellation/renewal events?icon

Webook renewal event is sent if product is already purchasedicon

Most helpful members this week

Sign up

‏‏‎ ‎

Log in to the Community

‏‏‎ ‎

Scanning file for viruses.

This file cannot be downloaded

Cookie policy

Cookie settings