The CONSUMPTION_REQUEST notification fires when Apple is processing a customer's refund request and needs consumption data from your server to make a decision. Providing accurate consumption data can help Apple decline refund requests for content that has been fully consumed.
When does it fire?
This notification triggers when a customer requests a refund for an in-app purchase and Apple wants to know how much of the content the customer has used. You have 12 hours to respond with consumption data via the App Store Server API.
Payload highlights
The signed transaction info includes the transaction ID of the purchase being contested. You need to look up usage data for this transaction and send it back to Apple using the Send Consumption Information endpoint.
How Yeethook helps
Consumption requests have a strict 12-hour deadline. Yeethook alerts your team in Slack immediately so you can ensure the consumption data is submitted on time. Missing this window means Apple makes the refund decision without your input.
Common use cases
- Get immediate alerts when Apple requests consumption data
- Track consumption request volume and response rates
- Ensure your team responds within the 12-hour deadline
- Monitor the correlation between consumption responses and refund outcomes