Can I run RefundHalt and RevenueCat at the same time?

Yes. Keep RevenueCat as the primary App Store Server Notifications receiver and add your RefundHalt webhook URL in RevenueCat's Apple Server Notification Forwarding field. Turn RevenueCat's own refund handling off so only one system answers.

Does RevenueCat send Apple a consumption percentage?

Per their public documentation, the payload they send covers consent, delivery status, sample content, and your refund preference. A usage-based consumption percentage is not part of it.

Does RevenueCat handle Google Play chargeback reviews?

Their refund handling documentation covers Apple's consumption requests. Google's orders.reviewrefund evidence window, which decides who pays for a chargeback from August 2026, is not part of that feature.

Do I need to remove the RevenueCat SDK to use RefundHalt?

No. RefundHalt needs no SDK at all; it works entirely server-side against the stores' official APIs. Your app code does not change.

All comparisons

COMPAREFacts checked July 11, 2026

RefundHalt vs RevenueCat for refund handling

RevenueCat is subscription infrastructure with a refund-response option. RefundHalt is a dedicated refund defense engine. They solve different problems, and they work well together.

The quick answer

If you already run RevenueCat and just want Apple refund requests acknowledged instead of ignored, turning on their refund handling is a fine first step. It sends Apple a fixed set of values with the preference you pick in a dropdown.

If you want each case decided on its own facts, you need more than a fixed preference. RefundHalt matches every request to the buyer, pulls real usage numbers from your server, applies your rules (grant the cheap goodwill cases, contest the heavy users), and also covers Google Play chargeback reviews, which RevenueCat's refund feature does not touch.

At a glance

Feature	RefundHalt	RevenueCat
Apple CONSUMPTION_REQUEST responses	Yes, automatic	Yes, automatic
Google Play chargeback reviews (orders.reviewrefund)	Yes, with evidence	No
Consumption percentage from real usage	Yes, from your endpoint or ingest API	No, not part of the payload they send
Refund preference	Per case, decided by your policy rules	One global dropdown, per-customer override via an attribute your code sets
Decline as a standing policy	Yes	Partial, only via the per-customer attribute, not the global setting
Per-case rules (price, usage, prior refunds)	Yes	No
Voided purchase tracking	Yes	Yes
Subscription infrastructure (paywalls, entitlements)	No, by design	Yes, that is the core product
Works without an SDK	Yes	No, the platform is SDK-based
Refund outcome analytics	Yes, cross-store ledger	Yes, refund requests chart

Where RevenueCat is stronger

You already use RevenueCat: enabling refund handling is one dropdown, zero new vendors.
It is free: RevenueCat charges nothing extra for refund request handling.
You want one platform for entitlements, paywalls, and analytics; refund responses are a bonus, not the mission.

Where RefundHalt is stronger

You sell on Google Play too: the 2026 chargeback rules make unanswered disputes cost real money, and RevenueCat's refund feature is Apple-only.
You want evidence, not just a preference: RefundHalt sends a consumption percentage computed from the buyer's actual usage.
You want per-case decisions without writing code: rules like 'grant under $5 with zero usage, contest heavy users' run automatically.
You want declines by default where justified: RevenueCat's global setting only offers grant or let-Apple-decide.

Use both: keep RevenueCat primary, let RefundHalt answer

You do not have to choose. Keep RevenueCat as your subscription backbone and set its Apple Server Notification Forwarding URL to your RefundHalt webhook. RevenueCat keeps receiving everything exactly as before, and RefundHalt receives the raw signed events it needs to fight your refund cases.

Set RevenueCat's refund handling to 'Do not handle' so the two systems never race to answer the same request.

Pricing

RevenueCat's refund handling costs nothing on top of the platform, which is priced on tracked revenue. RefundHalt is a flat, standalone price: $14.99 a month or $99.99 a year, everything included, with a 7-day free trial.

Frequently asked questions

Can I run RefundHalt and RevenueCat at the same time?: Yes. Keep RevenueCat as the primary App Store Server Notifications receiver and add your RefundHalt webhook URL in RevenueCat's Apple Server Notification Forwarding field. Turn RevenueCat's own refund handling off so only one system answers.
Does RevenueCat send Apple a consumption percentage?: Per their public documentation, the payload they send covers consent, delivery status, sample content, and your refund preference. A usage-based consumption percentage is not part of it.
Does RevenueCat handle Google Play chargeback reviews?: Their refund handling documentation covers Apple's consumption requests. Google's orders.reviewrefund evidence window, which decides who pays for a chargeback from August 2026, is not part of that feature.
Do I need to remove the RevenueCat SDK to use RefundHalt?: No. RefundHalt needs no SDK at all; it works entirely server-side against the stores' official APIs. Your app code does not change.

Sources

Competitor information comes from public documentation and websites, verified on the date shown. Spot something outdated? Email hello@refundhalt.com and we will correct it.