I've been posting Consumption Information in response to CONSUMPTION_REQUEST notifications sent to my servers. For months and months the response has been 202 (ACCEPTED). Suddenly on 8/25 everything has switched to 404, which indicates the transactionId is not found. The 404 error doesn't seem to indicate any format problem (and this had been working for some time), just that the transactions aren't recognized to Apple. Has anyone else seen a change in Apple response to sending Consumption information in response to a CONSUMPTION_REQUEST?

When you create an SKMutablePayment it has a field applicationUsername which corresponds to a username within our service. How is this reflected in purchases (the info the API returns the app which presumably we send to our server) vs info sent via S2S messages which we receive directly from Apple? Is the applicationUsername visible at all in either of these messages (the one returned in the running app via the purchase API as well as the S2S message)?