Hi there, I had a couple of question about the nature of the `cancelDate` field coming back in the RVS response.
The docs read
cancelDate - Long Integer - The date the purchase was cancelled, or the subscription expired. The field is null if the purchase was not cancelled.
My understanding is that the cancelDate will always be in the past but I want to make sure I'm not making a false assumption.
My questions are:
1. When present and not-null in the API response is cancelDate always going to be in the past.
2. If the cancelDate is in the future is that the date at which the subscription _will lose_ their entitlements? Or should we rely on renewalDate (or the larger of the two values) for that?
3. If the cancelDate is present in the API response and the value is in the past but renewalDate is in the future should we give the user their entitlements for the maximum of the two values or should we revoke access right away?
4. Unrelated to cancelDate but still within the context of subscription management, are there any plans for supporting webhook notifications for subscription lifecycle events? Like cancelation, payment made, free trial start, etc? Such things would help out from a reporting perspective quite a bit.
Thanks for all the help!