Forget this... It was my mistake...

This is the answer I've got today (20210621) from Feedback Assistant: Apple - Jun 21, 2021 at 2:23 PM Engineering has provided the following information regarding this issue: In sandbox, such issues can happen if the purchase was made on or before 2018 as transactions created in or before 2018 were deleted. So, the original transaction data was not available and we use the date of the restored transaction as a fallback. This shouldn't happen in production. Kind regards, Oscar

I suggest you open an issue in Feedback Assistant: https://feedbackassistant.apple.com/ It seems that the response code returned by your server is not interpreting it correctly. Are you returning any Content-Type headers that do not match the content of the response?

I think is is something that will be available in the version 2 of notifications in some later moment during this year. You can see the conference Manage in-app purchases on your server by Tori Shurman in WWDC21

I suggest you open an issue in Feedback Assistant: https://feedbackassistant.apple.com/ It seems to be a bug. Does it happen in Sandbox or in Production?

Hello, @crauss77. Have you been able to find any users whose subscriptions are being affected by this problem? Because it could serve as an additional piece of information for Apple to use when investigating the problem. And if you have stored the "latest_receipt" of any of their purchases, you could call the verifyReceipt URL to see if, at least, the purchase information that does not arrive as a notification is correctly registered with Apple.