Quick answer: Because Apple always makes the final decision, your consumption data and refund preference are inputs, not a veto. Even a strong, on-time response with a "prefer decline" preference can result in a granted refund if Apple's decisioning system weighs the customer's history, the refund reason, or other factors differently. It doesn't mean you did anything wrong, and it doesn't mean responding is pointless. It means you influence the odds, not the outcome of any single case.
This is one of the most frustrating moments in the whole refund process: you caught the CONSUMPTION_REQUEST in time, you sent accurate consumption data, you set your preference to decline, and Apple granted the refund anyway.
Here's the truth, stated plainly: you never had the power to deny the refund. Apple makes the final decision. Everything you send is evidence submitted to the decision-maker, not a control over it.
That's the relationship you have with Apple's refund system, and understanding it upfront saves a lot of misplaced frustration.
An apple granted refund despite consumption data does not automatically mean your response failed. It means Apple considered the available information and reached a refund decision that differed from your preference.
What your response actually does
Your consumption response is one input into Apple's refund decision process, alongside factors you don't see or control:
The customer's stated refund reason.
The customer's purchase and refund history.
Apple's applicable policies and requirements.
The specifics of the transaction.
Your consumption data and refund preference.
Apple's documentation allows developers to provide consumption information such as consumption status, delivery status, account tenure, lifetime purchase and refund amounts, and other transaction-related information. Apple uses the submitted information to help inform its refund decision.
You're adding relevant evidence to Apple's decision process. Adding evidence matters, but it doesn't mean Apple must reach the outcome you requested.
Reasons a well-formed response still loses
If you responded correctly and still lost, several factors can explain why apple refunds even when your evidence appears strong:
The customer's side was simply stronger. A credible dissatisfaction reason, especially early in a subscription with low usage, can support a refund.
Regional consumer law. Applicable consumer protections can affect how refund requests are handled. Developer-submitted evidence doesn't override a legal entitlement.
Customer history in their favor. A customer with little prior refund activity can present a different context from someone with repeated refunds.
The reason category. The customer's stated refund reason is part of the information Apple can consider.
Your data didn't say what you thought. High consumption may support your position in some cases, but if the actual data shows low usage, a delivery problem, or another issue, accurate evidence may support the customer's refund instead.
Notice that most of these aren't necessarily failures on your part. Apple's refund process is designed so that your response contributes evidence, while Apple retains the final decision.
Why this isn't a reason to stop responding
It's tempting to conclude that if Apple can approve a refund despite your response, responding is pointless. That's the wrong lesson.
The purpose of responding is not to guarantee every refund is denied. The purpose is to make sure Apple receives the relevant evidence available to you for every eligible request.
If a refund preference ignored situation occurs, that does not mean the preference was a binding instruction. Your preference communicates what outcome you recommend; Apple remains the decision-maker.
You also can't know how Apple would have evaluated a request if you had provided no consumption information at all. Consistent responses ensure that your available evidence is actually submitted instead of leaving Apple's process without your input.
Where your effort really pays off
If any single case is out of your hands, put your energy where it compounds:
Respond to every eligible request, every time. The biggest operational problem isn't simply an approved refund after a response; it's an eligible request that receives no response because the window was missed. Making sure your response coverage stays high is the part fully within your control. (See The 12-Hour Window.)
Send accurate, complete data. A response with real consumption, delivery, tenure, and relevant transaction data gives Apple more context than a bare preference. Apple documents several consumption fields that can be submitted as part of the consumption-information workflow.
Watch the aggregate, not the anecdote. Track approved-refund rates over time and by reason. A single contested refund apple case cannot tell you whether your overall refund-response process is working.
This is the practical case for automation. Responding to eligible requests with complete data inside the required window is difficult to sustain manually at scale.
Apple refund automation software can help teams monitor incoming requests, prepare the relevant consumption information, submit responses consistently, and track outcomes over time.
RefundSensor answers eligible Apple CONSUMPTION_REQUEST events and Google Play chargeback reviews automatically, with the available consumption data attached, and tracks outcomes over time. The goal isn't to guarantee that Apple will deny every request. It's to make sure you don't lose the opportunity to provide your evidence simply because nobody was available to respond.
Further reading
Stop judging refunds one case at a time. RefundSensor responds to eligible Apple and Google Play refund requests with available data inside the applicable response window and tracks your outcomes over time, so you can optimize the process you actually control. Start free
Frequently asked questions
Because Apple makes the final decision and your response is only one input. The customer's reason, history, and regional refund rights can outweigh your consumption data and preference in any given case.
No. It's one factor Apple considers, not an override. Where your evidence supports it, it can help; it can't force the outcome.
Usually not. A single granted refund often just reflects a stronger customer case or a legal refund right, not a mistake in your response.
Yes. Influence shows up across many requests, not in one. Consistently responding with accurate data lowers your overall approved-refund rate even though individual cases can still go against you.
By your approved-refund rate over time, not by individual outcomes. The trend reflects the strategy; a single case doesn't.
