Hi @BlackPeral have a look this thread

Hello @a_el_amraoui , @ygx consumptionStatus Some examples of consumption status include the following scenarios: Scenario 1: A user purchases a “bag of 100 coins” in your app and spends all 100 coins. The in-app purchase is considered fully consumed. Scenario 2: If your app has an exchange platform that has bartering, or if your app transferred an in-app purchase from one account to another user’s account, the in-app purchase is considered fully consumed. It’s a numerical value (usually in minutes or hours). playTime It helps Apple understand how much of the app or in-app purchase was consumed. For example: If playTime = 5, it means the user used the app (or specific purchased feature/content) for 5 minutes (or hours, depending on your unit) before refunding. If playTime = 0, it means the customer never used the app or content. Thanks

Hello @crauss77 , Apple’s CONSUMPTION_REQUEST server notification does not include any indication of user consent (customerConsented). That’s by design Apple expects your app, not your server, to collect and confirm the user’s consent before sending consumption data to Apple. Here’s how it’s meant to work 👇 App receives refund request sheet prompt When the user initiates a refund through Apple (for example, via the “Report a Problem” link or refund sheet), Apple sends a CONSUMPTION_REQUEST notification to your server. This is Apple saying: “Please send us details about how this user consumed their purchase.” Your app is responsible for obtaining consent Before your server calls the Consumption API, you must collect the user’s consent within the app. Apple requires that customerConsented = true be included in your API call; otherwise, Apple rejects the request. There is no fallback or assumption Apple will not process a consumption update without explicit consent.