A store-authorized reversal of purchase money that may also revoke the digital benefit previously granted.
A refund returns all or part of an in-app purchase payment through Google Play or the App Store. It can result from a customer request, developer action, policy decision, fraud review, unacknowledged Play purchase, or other store process. Refund and cancellation are not synonyms: cancellation usually stops future renewal while preserving access through a paid period, whereas a refund reverses money already collected and may require immediate revocation.
A backend learns about reversals through store lifecycle channels and verification APIs, not from a client flag. Google Play provides RTDN and voided-purchase information alongside current purchase state. Apple App Store Server Notifications V2 can send REFUND and related signed transaction data; sandbox refund requests can generate the same notification type for testing. The server verifies app identity, product, transaction lineage, environment, and event authenticity before changing an entitlement.
The correct access result depends on product type, refunded quantity or period, store evidence, and business rules permitted by the platform. A fully refunded one-time unlock generally should no longer grant its durable benefit. A subscription reversal can affect the refunded transaction period while later valid periods or a reversed refund need separate handling. Keep an audit record rather than deleting the original purchase, and make the state transition idempotent so duplicate notifications do not revoke unrelated access.
Revenue reporting should record refunds separately from gross sales, renewals, and voluntary churn. Customer support needs transaction identifiers and reason context without exposing raw secrets. Tests should cover full and partial outcomes when supported, duplicate and out-of-order events, refund reversal, wrong app, sandbox separation, and a purchase mapped to multiple features. Never promise that an app directly approves every request; the store controls its refund workflow and payment movement. The application’s responsibility is to respond accurately to verified results.
The server-side access record that a verified reversal can change.
Apple’s signed channel for refund lifecycle events.
The Play requirement whose omission can trigger an automatic refund.
Preserve audit history while updating access from verified store evidence.
Start free