AppStore Server Notification sent a different type from the real one

Question

Created Apr ’23

Replies 2

Boosts 0

Participants 2

Recently I got CS. The customer paid for a subscription renewal but he didn't get a benefit from the subscription. I looked up for server notification logs and saw the latest server notification type was did_fail_to_renew. Also, i requested a transaction history from AppStore Server API(GET https://api.storekit.itunes.apple.com/inApps/v1/history/{originalTransactionId}). The auto_renewable_subscription_purchase was successfully purchased. I don't know why AppStore sent the wrong notification type. Can you answer the question? Thanks

Boost

Answer 1

App Store Commerce Engineer OP

Apple

Apr ’23

Based on similar scenarios, the most likely case is that the user had a failure to renew but then subsequently recovered, with type DID_RENEW subtype BILLING_RECOVERY sent. You can check the notification history endpoint to see a full history of V2 notifications in case there was a communication failure to your server. If you are still unable to resolve what occurred, you may file a ticket in Feedback Assistant.

2

Answer 2

silleruss OP

Apr ’23

Thank you for answering this question. I saw the history of that subscription using 'GET https://api.storekit.itunes.apple.com/inApps/v1/notifications/history' endpoint. But i didn't find out any type of DID_RENEW and subtype BILLING_RECOVERY. Should i have to check for purchase history when i got a DID_FAIL_TO_RENEW notification?

0