Excessive refund requests can cost you more than the refunds, because both app stores treat them as a quality signal

Excessive refund requests are on Apple's list of reasons to doubt your app. Guideline 5.6.4 of the App Review Guidelines says so in one sentence, and Google's Developer Distribution Agreement has a matching clause that lets it pull a new developer's app on refund rates. Most developers read refunds as a revenue problem. The stores also read them as a quality signal, and a quality signal can end in a removal notice.

Here's what each store actually wrote, how far the wording reaches, what it costs when an app comes down, and how to keep your refund volume from becoming evidence against you. No store publishes a threshold, so this is about reading the contracts carefully and controlling what you can.

What Apple's Guideline 5.6.4 says about excessive refund requests

Guideline 5.6.4, titled App Quality, sits inside section 5.6, the Developer Code of Conduct. Its middle sentence is the one that matters: indications that the quality expectation isn't being met include excessive customer reports about concerns with your app, such as negative customer reviews, and excessive refund requests. The last sentence connects it to enforcement. An inability to maintain high quality may be a factor in deciding whether a developer is abiding by the Developer Code of Conduct.

That link is where the weight comes from. The Code of Conduct's own introduction says your Developer Program account will be terminated if you engage in activities that aren't in accordance with it. The same section lists the behavior Apple is looking for: apps that trick users into unwanted purchases, raise prices in a tricky manner, or charge for features or content that aren't delivered. Each of those produces refund requests, which is why Apple counts them.

What a 5.6.4 notice looks like in practice

Apple doesn't publish its enforcement letters, so the best evidence is what developers report. In one Apple Developer Forums thread, a developer wrote that Apple cited Guideline 5.6.4 and warned that the app would be removed from sale, with the developer account possibly suspended, if the app wasn't changed within 14 days. That developer's proposed fixes were a free trial, an in-app rating screen, more testing and design tweaks. Other developers in the thread pointed out that none of it addressed why customers were asking for their money back.

Can Apple remove an app for excessive refund requests?

Yes. Schedule 2 of the Apple Developer Program License Agreement, section 7.3, lets Apple stop marketing and allowing downloads of an app at any time, with or without cause. It also lists specific grounds, including a violation of the agreement or of other documentation such as the App Review Guidelines. Guideline 5.6.4 is part of those guidelines. And the same section adds that Apple's decision to stop distribution doesn't relieve you of your obligations under Schedule 2.

What Google Play's agreement says about refund rates

Google's wording is shorter and more direct. Section 4.11 of the Google Play Developer Distribution Agreement, in the version effective September 15, 2025, says that for new developers without product history, Google may use or publish performance measurements such as uninstall and refund rates to identify or remove products that aren't meeting acceptable standards, as determined by Google.

Two details deserve attention. The clause names refund rates by name, not as an example of something broader. And it's scoped to new developers without product history, which is exactly the account that can least afford a removal. An established account isn't immune, though. Section 10.3 lets Google terminate the agreement if you or your product pose a potential risk for economic, reputational or security-related harm to Google, users or partners.

How a Google Play removal turns into a terminated account

Google's Play Console help on account terminations describes the ladder. Multiple removals or warnings may result in an app suspension. App suspensions count as strikes against the good standing of your developer account. Multiple suspensions, or suspensions for egregious violations, may lead to termination. When an account is terminated, every app in the catalog is removed from Google Play, and the users, statistics and ratings attached to those apps are forfeited.

What removal costs in money

A removal notice doesn't erase the refunds you already owe. It stops the revenue that would have paid for them. On Apple, Schedule 2, section 6.3 makes you reimburse Apple for refunds it grants, including refunds a payment provider reports, which is how a chargeback reaches you. Section 7.1 keeps that reimbursement alive before and after termination and lets Apple withhold all payments for a period it considers reasonable to offset end-user refunds. Section 8.1 of Google's agreement does the same for products sold before removal, and section 3.8 lets Google deduct refunds from your payouts.

Then count what keeps running. Customers who already installed the app still open it. Your servers, GPU compute, paid third-party API calls, storage and payment-processor fees keep billing you for those users while new revenue drops to zero. If the app pays out to creators or affiliates, those payouts were calculated on sales that may now come back as refunds against a frozen balance.

How often stores actually terminate accounts

The public numbers put the risk in proportion. Apple's 2024 App Store Transparency Report counts 146,747 terminated developer accounts. Of those, 146,583 were terminated for fraud under DPLA section 3.2(f), and Apple notes the most common reason is a connection to other terminated developer accounts. Only 99 apps were removed under Guideline 5.6.0, the Developer Code of Conduct, and 69 under Guideline 3.1.2, Subscriptions. Of 8,132 appeals of account terminations, 225 accounts were restored.

Read that two ways. A refund-driven termination of an honest app is rare, and the report doesn't break out 5.6.4 on its own. But once an account is terminated, getting it back is unlikely. Apple's Code of Conduct does offer one route: a written statement detailing the improvements you plan to make, and if Apple approves the plan and confirms the changes, the account may be restored.

How to keep refund volume from becoming evidence

You can't stop people asking for refunds. You can stop giving them reasons, and you can make sure the stores hear your side in the two flows where they ask.

Remove the causes the Code of Conduct names

• Show the price, the billing period and the renewal terms on the paywall before the purchase button, so nobody discovers a weekly charge on a bank statement.
• Deliver what you sold the moment it's paid for. A purchase that doesn't unlock is a refund request and a support ticket at once.
• Make cancellation easy to find in your settings screen. A subscriber who can't find the exit asks the store for their money back instead.
• Watch refunds by product, country and app version, not just in total. A spike after one release or in one market tells you what to fix.

Answer the two flows that let you submit evidence

Only two refund flows let you put evidence in front of the store before it decides. Apple sends a CONSUMPTION_REQUEST and asks you to respond within 12 hours with consumption data through Send Consumption Information. Google Play sends a pending refund review for a chargeback, and you respond within 24 hours by calling orders.reviewrefund. Everything else, including Google Play's 48-hour self-service refunds, support refunds and auto-refunds of unacknowledged purchases, is decided without you. A request you answer with accurate data is a request the store can decline when the content was delivered and used.

Can you be punished for refunds you didn't cause?

Neither store says it separates abusive refund requests from fair ones in its quality review, so assume the raw volume is what's visible. That's the case for keeping your own record: which refunds came from the same few accounts, which followed a delivery failure on your side, and which came after heavy use. If a 5.6.4 notice ever arrives, that record is what turns a vague promise into the specific improvement plan Apple's Code of Conduct asks for.

RefundHalt answers every CONSUMPTION_REQUEST and Google Play chargeback review inside its window with your real usage data, and tracks refund rates by product, country and version, so you see a quality problem in your numbers before a store sees it in theirs.