PRICING

Two plans. Everything automatic.

Pick a plan, connect your apps, and every refund request is answered for you.

Save up to 40%

Pro

For indie developers with up to 5 apps.

$49.99$29.99/mo

Billed yearly at $359.88Save 40%

  • Protect up to 5 iOS and Android apps
  • Unlimited refund requests answered
  • Helped decline about 76% of refund requests
  • Automatic policy engine and custom rules
  • AI-assisted dispute statements
  • Usage data integration
  • Webhooks and notification forwarding
  • Unlimited analytics history
  • Priority processing

Cancel anytime

Most popular

Enterprise

For studios and growing app portfolios.

$69.99$49.99/mo

Billed yearly at $599.88Save 29%

  • Protect unlimited iOS and Android apps
  • Unlimited refund requests answered
  • Helped decline about 76% of refund requests
  • Automatic policy engine and custom rules
  • AI-assisted dispute statements
  • Usage data integration
  • Webhooks and notification forwarding
  • Unlimited analytics history
  • Priority processing

Cancel anytime

Every plan includes both platforms, encrypted credential storage, and the deadline-safety fallback. 14-day free trial on each. Prices exclude VAT.

QUESTIONS

Frequently asked questions

RefundHalt is an automatic refund protection service for iOS and Android apps. You connect your app once, with no SDK and no code changes. From that moment, every refund request and every chargeback review that Apple or Google opens for your app is answered for you, with real transaction and usage information, before the store's deadline. The result is simple: fewer unfair refunds are approved, more of the revenue you already earned stays with you, and no one on your team spends time on refund paperwork.
The store decides with only the customer's information. In practice, an unanswered request is usually approved. Responding costs nothing and puts your side into the decision. RefundHalt makes sure a response is always sent on time, including nights and weekends.
Through the official APIs. When a customer requests a refund, the store's notification identifies the order. RefundHalt then retrieves the full transaction and purchase history through the App Store Server API and the Google Play Developer API. If you connect a usage endpoint, your own usage records become part of the evidence as well. RefundHalt also uses AI to read your app's public store listing and describe what each purchase costs you to deliver, which makes your case easier for a reviewer to understand.
We present your case in every single one. Apple and Google make the final decision, and RefundHalt provides them with complete, truthful information that assists that decision. In practice, across the cases we handle, RefundHalt has helped decline about 76% of customer refund requests and chargebacks.
Perfect tracking does not exist. Many apps cannot measure exact usage time, and an app without an account system cannot always tell who used what. Apple knows this, which is why the consumption payload accepts an "unknown" value for many fields and does not require complete accuracy. Google takes the same position: only your recommendation is required, and every consumption field beside it is optional. RefundHalt sends the data that is available and marks the rest as unknown. It never invents a number. In refund decisions, genuine information performs better than exaggerated information, and it keeps your developer account in good standing.
Yes. Both stores built these systems and ask developers to use them. Apple's engineers publicly recommend calling the Send Consumption Information endpoint when a refund request arrives, because the data you provide is considered in the decision. Google introduced the Review Refund API so developers can share transaction information on chargebacks. RefundHalt only sends real data through these official APIs.
developer.apple.com/forums

App Store Commerce Engineer

Jun ’24

Apple

To respond to CONSUMPTION_REQUEST notifications, you should call the Send Consumption Information endpoint: https://developer.apple.com/documentation/appstoreserverapi/send_consumption_information/

Whether you call the endpoint and provide consumption information or not, the refund may be granted or denied. However any data you provide via the endpoint will be considered in the refund decisioning process, so it’s generally recommended you call the endpoint to provide data if possible.

3 comments 0
An Apple App Store Commerce engineer on the developer forums, June 2024. Apple recommends providing consumption data.Source: developer.apple.com
For orders placed after August 3, 2026, developers pay for lost chargebacks: the purchase price, less Play's service fee, plus the chargeback fees from the bank. Google also added a 24-hour review window so developers can submit evidence before a chargeback is decided. RefundHalt answers these reviews automatically.
support.google.com/googleplay/android-developer

Updates to refund protection and chargeback cost responsibility

Google Play is committed to continuously strengthening the protection of the platform. In 2025, Google Play successfully prevented US$3.4B of fraud and abuse. In 2026, we are implementing additional enhanced guardrails and fraud detections to reduce potential refund abuse, further protecting users and developers on Google Play.

Additionally, to align with industry standards, Google Play and developers will begin sharing chargeback costs for orders placed after August 3, 2026. Chargebacks are disputes initiated by users directly with their financial institutions. When a chargeback occurs, the costs is split as follows:

  • Developer responsibility: The purchase price (less Play’s service fee) and the associated chargeback fees from the financial institution.
  • Google Play’s responsibility: We will continue to cover the service fee cost for that transaction.

To help you take an active role in managing chargebacks ahead of these changes taking effect, a new optional Review Refund API is now available. This lets you to share key transaction information with Google Play, such as order delivery state and item consumption status. With this information, Google Play can better identify and contest illegitimate chargebacks on your behalf.

Google's announcement in Play Console Help: chargeback costs are shared with developers for orders placed after August 3, 2026.Source: support.google.com
You can check in two minutes. On iOS, open App Store Connect, go to Trends, select Proceeds, and filter Transaction Type by Refund. On Android, open Play Console and review the Financial reports section. Many developers see the full number there for the first time.
No. RefundHalt works entirely server-side through the stores' official APIs. Setup means pasting two values into App Store Connect or Play Console. Most developers finish in about two minutes.
On iOS, Apple requests consumption information for consumable purchases and auto-renewing subscriptions, and RefundHalt tracks refunds across all purchase types. On Android, RefundHalt answers chargeback reviews and tracks refunds through the Voided Purchases API.
Apple requires customer consent before consumption data is shared. You do not need a popup. Most developers add a short line to their privacy policy or terms of service. Ask your legal advisor for the exact wording.
Yes. We only request the minimum access needed to answer refund requests and submit your evidence, never a permission that could transfer your app or change your account. Credentials are encrypted at rest with AES-256-GCM envelope encryption under a rotatable key ring. Apple notifications are verified against Apple's root certificates, and Google deliveries are verified with OIDC. We never ask for your developer account password.
Yes. You would build webhook receivers for both stores, verify Apple's signed notifications, set up Play RTDN, match buyers to purchases, assemble evidence, and respond within the deadline at any hour. That is several weeks of engineering plus ongoing maintenance. RefundHalt already does all of it for one subscription.
Cool, contact us by email at support@refundhalt.com.

The next refund request is already on its way.

Set up RefundHalt in the time it takes to read another support email about a refund you didn't get to contest.