On iOS, Apple sends a CONSUMPTION_REQUEST notification and waits up to 12 hours for consumption evidence before deciding. On Android, Google sends a chargeback review request with a 24-hour window. RefundHalt receives these, matches the buyer, computes consumption from real usage (or time-based estimates), applies your policy, and submits the response — usually within seconds.

No. RefundHalt works entirely server-side against the stores' official APIs. Setup is pasting a webhook URL (iOS) or a topic name and a service-account email (Android) into the consoles you already use. Optionally, you can stream usage events for evidence-grade responses.

Apple and Google make the final call — nobody can promise a specific outcome. What RefundHalt guarantees is that your side of the case is always presented: with consent, delivery status, usage evidence and your preference, inside the deadline. Developers who respond consistently report the majority of contested refunds being declined.

For orders placed after August 3, 2026, Google shifts the cost of lost chargebacks to developers — you lose the purchase price plus fees. Google also introduced a review API where you get 24 hours to submit evidence. RefundHalt automates exactly that.

Instead of deciding automatically, RefundHalt sends your server a signed webhook with the full case file. Your system replies with grant, decline, or no preference through the API. If you don't answer in time, your configured fallback fires before the deadline — you can never lose by silence.

Credentials are encrypted at rest with AES-256-GCM envelope encryption under a rotatable key ring, bound to their owning record. Apple notifications are verified against Apple's root certificates; Google deliveries are OIDC-verified. We never ask for your developer account password.