Skip to content
AppDues
Log in
Contact salesSign up

Why the "Always decline" refund preference was removed

If you went looking for the "Always decline" refund option in the dashboard and found it missing, that change is intentional. This guide explains what was removed, why a single blanket decline stops working over time, and how to express refund preferences per audience instead.

What changed

The dashboard no longer offers "Always decline" as a global refund preference. The remaining global options are:

  • Let Apple decide — a neutral stance with no preference expressed.
  • Grant in full — you prefer the refund be approved.
  • Grant prorated — you prefer a partial refund based on how much of the subscription was consumed.

If your account already had "Always decline" enabled, nothing was flipped behind your back: that setting stays active. The one-way catch is that once you switch it off, you cannot turn it back on — the dashboard shows a confirmation prompt before you commit. Whether to keep it on is your decision, though the case for keeping it is getting weaker.

A newer option, Refund Control, lets you set refund preferences across different customer segments rather than relying on one global choice, so Apple and Google receive a recommendation that fits each request.

Why "Always decline" was removed

Three mechanics explain the removal.

Refund preferences are signals, not instructions. When you send a preference to Apple through the App Store Server API, you are not issuing a binding decision. Apple weighs your input alongside many other factors when it evaluates a refund request. The refundPreference field inside a ConsumptionRequest is advisory by design.

Blanket declines erode their own weight. A preference that is always set to decline — whether the user barely opened the app or hit a genuine bug that made it unusable — stops reflecting the specifics of a transaction. Over time Apple's systems discount a signal that never varies. The signal turns into noise.

Rejecting valid refunds can backfire. When a legitimate refund is declined, some users skip the store and go straight to their bank to file a chargeback. A high chargeback rate puts your Apple developer account at risk of suspension. A blanket decline policy can therefore push users toward the outcome that hurts you most.

Declined refund vs. chargeback: keep the two apart

These are different events with different owners and different risk.

  • Store-declined refund — the store evaluates your advisory preference and makes the final call. You expressed a view; you did not decide.
  • Chargeback — the user disputes the charge with their bank, bypassing the store's refund flow. This is the outcome a blanket decline can provoke, and a high chargeback rate risks your developer account.

Keeping that line clear matters: a preference you send is a recommendation, while a chargeback is a dispute you did not control.

What to do right now

If you want finer control over refund recommendations, use Refund Control in the dashboard. It lets you build multiple policies keyed to customer audiences — platform, country, first purchase date, or any custom audience you define. Each policy can express one of three preferred outcomes:

  • Decline
  • Grant
  • Neutral (no preference)

The matching preference then travels to the right store: Apple gets it via the Consumption Request API, Google via the Refund Review API. On both platforms the preference is only a recommendation — the store retains final authority over whether a refund is issued.

Audience-based policies are the practical replacement for a single blanket rule. Instead of giving every request the same answer, you can tailor the recommendation to each group's situation. Decline becomes a deliberate choice saved for requests that truly warrant it, and that restraint is what keeps the signal meaningful as time goes on.

Decision checklist

Use this to decide what to do with your current setting.

  1. Check whether "Always decline" is still active on your account. If it is, it remains in force until you change it.
  2. Ask whether one rule fits every refund request. If your users span platforms, countries, or very different usage patterns, a single global decline likely does not.
  3. Decide whether to switch off the legacy setting. Remember it cannot be re-enabled once turned off, and the dashboard will confirm before you commit.
  4. Move to segmented policies where you need nuance. Use Refund Control to set decline, grant, or neutral per audience.
  5. Reserve decline recommendations for cases that warrant them. A signal that varies with context carries more weight than one that never does.

Worked example: two users, one blanket rule

Imagine two refund requests arriving the same day under an "Always decline" policy.

  • User A installed the app, barely used it, and asked for a refund the next morning.
  • User B hit a genuine bug that made the app unusable and asked for a refund after a week of trying.

A blanket decline treats both identically. Under a segmented policy, you could decline User A's request and grant User B's, so the decline recommendation reflects real context. Over time that makes your decline signal more meaningful to the store — and it reduces the chance that a legitimately aggrieved user escalates to a chargeback.

The bottom line

"Always decline" was a blunt instrument, and it was losing effectiveness. A setting that does not do what you assume it does is not worth the risk. Segmented refund policies let you express a preference that actually reflects each request, while the store keeps the final say.

Frequently asked questions

Is my existing "Always decline" setting still active?

Yes. Settings that were already set to "Always decline" were left in place and remain active. The change only removes the option from the dashboard for new selections.

Can I turn "Always decline" back on after switching it off?

No. Once you switch the setting off, it cannot be re-enabled. The dashboard shows a confirmation prompt before you commit, so you can decide with that in mind.

Does a refund preference force Apple or Google to approve or reject a refund?

No. The preference is advisory. Apple evaluates it as one factor among many, and Google receives it through the Refund Review API. The store always makes the final refund decision.

Why is a blanket decline risky for my developer account?

Declining legitimate refund requests can push users to file chargebacks with their bank instead. A high chargeback rate puts your Apple developer account at risk of suspension.

What audiences can Refund Control target?

Policies can be based on platform, country, first purchase date, or any custom audience you define. Each policy can express decline, grant, or neutral as the preferred outcome.