I am currently implementing In-App purchases for our iOS app. In particular, I am currently working on subscriptions. We offer several conditions for non-renewal of a subscription (1 month, 3 months, 6 months) and a subscription to automatic renewal, which lasts 1 month at a time. I installed a system that will check all night if the auto-renewal subscription is still valid and has not yet been returned by Apple's check verification servers. To automatically renew my subscription, I can limit this to purchases made last month, because after that I must either have a new transaction for this user or the subscription has expired.
However, my question is that it is also necessary to regularly check non-renewable subscriptions, especially for updates in the field cancellation_date. In the Check Validation Guide , the cancelation_date field does not mean that it is intended only for automatic renewal of a subscription. However, several other documents and answers (sorry for the lack of links here) have suggested that this is what you only need to check for updates in automatic renewal of your subscription.
I think the only reason non-renewable subscriptions always return to transaction receipts is because applications that do not store this information on their server can restore a subscription. However, if the transaction is also updated, if there are any changes in the payment, I would very much like to follow this information.
Since we have a large number of users, and we need to check either only payments for the last month, or all payments for the last 6 months are of great importance, I would like to hear your opinion (and, I hope, experience) in this regard.
source
share