We encountered a bug receiving a duplicated DID_RENEW notification for the same transactionId with different notificationUUID and signedDate after decoding it. We received them in a 98ms time lapse, so it seems there is a bug on Apple side. So far it is happening in the Sandbox environment, but maybe the Production environment is affected (we cannot confirm it because we already don't change to V2 in Production). There is an example of decoded notifications to illustrate the error: Notification extract #1 { "decodedTransaction": { "signedDate": 1695733544660, // Notice it is different "transactionId": "2000000422429312", // Notice it is the same "environment": "Sandbox", "expiresDate": 1695737117000, "purchaseDate": 1695733517000, "transactionReason": "RENEWAL", "originalPurchaseDate": 1695729871000, ... }, "notificationType": "DID_RENEW", "notificationUUID": "693c67fd-f507-49cd-b0cb-c244e94fe874" // Notice it is different } Notification extract #2 { "decodedTransaction": { "signedDate": 1695733544758, // Notice it is different "transactionId": "2000000422429312", // Notice it is the same "environment": "Sandbox", "expiresDate": 1695737117000, "purchaseDate": 1695733517000, "transactionReason": "RENEWAL", "originalPurchaseDate": 1695729871000, }, "notificationType": "DID_RENEW", "notificationUUID": "7e69c544-5ba0-42a0-88f4-ddae211563b5" // Notice it is different }