We're also having this issue in the in the sandbox since May 25th. The signedRenewalInfo (JWSRenewalInfo) field of responseBodyV2DecodedPayload contains a null payload. It contains valid x5c entries, just missing the payload. We have not experienced this in production up until this point. It has been causing some concern in development.

Seems like things are back in order! The issue was resolved for me a few hours after my previous post. Lasted about 6 days in total. Thanks for fixing the issue!