Purchase Acknowledgement

Definition

Purchase acknowledgement is the required signal that tells Google Play a non-consumable product or subscription purchase has been processed. For an initial purchase, the developer verifies the purchase, grants the correct benefit, and then acknowledges it once. If acknowledgement does not happen within three days, Play automatically refunds and revokes the purchase. Subscription renewals do not require another acknowledgement.

The deadline begins when a purchase becomes PURCHASED, not while it remains PENDING. That distinction is important for cash-based or delayed payment methods. A backend must never grant or acknowledge merely because it received a token; it first queries authoritative purchase state and validates product, package, user binding, and replay rules. Obsolete inference from a legacy payment field is not a substitute for the current API resource.

Reliable processing order

A secure sequence receives the token, performs server-side verification, commits the entitlement idempotently, and calls the Play Developer API acknowledgement endpoint. Google recommends backend processing where possible because it handles purchases from other devices, promotion redemption, and app network loss. If the same request or RTDN is delivered twice, the handler should recognize the existing purchase and avoid duplicating benefits while treating an already acknowledged result as success.

Consumable one-time products are consumed rather than acknowledged, because consumption also makes the item purchasable again. Testing should cover pending-to-purchased transitions, crashes between persistence and acknowledgement, retryable API errors, duplicates, automatic refund, and a purchase already processed elsewhere. Apple uses transaction finishing in StoreKit as a related client responsibility, but it is not the same Play acknowledgement API or three-day rule. Keep platform terminology precise when designing a cross-store state machine.