Apple’s signed server-to-server messages for subscription and in-app purchase lifecycle changes.
App Store Server Notifications deliver asynchronous events from Apple to a developer-controlled HTTPS endpoint. Version 2 wraps notification data in a signed JWS, allowing the receiver to verify Apple’s certificate chain and decode transaction and renewal information. Events cover renewals, billing failures, grace periods, refunds, revocations, offer changes, expirations, and test handshakes. They are Apple’s functional counterpart to Google Play RTDN, although names, payloads, retry behavior, and state models differ.
The notification is evidence to process, not a reason to trust arbitrary JSON. A backend verifies the JWS, binds bundle ID and environment, checks signed dates and identifiers, and handles notificationType plus subtype. Production and sandbox must be distinguished. Duplicate delivery is normal, and events can arrive out of order, so notificationUUID and store timestamps support idempotency and ordering guards. Current transaction state may also be reconciled with Apple’s server APIs.
In App Store Connect, the developer supplies production and sandbox notification URLs. Tierux’s Apple setup guidance uses the same app-specific endpoint for both environments, but entering the URL remains one manual App Store Connect step. A TEST notification confirms routing and signature verification; it does not prove every renewal or refund branch. The handler should return a retryable status for transient failures and a successful response only after durable processing rules are satisfied.
For a renewal, signed transaction data extends the entitlement. A billing issue may retain access only when Apple indicates Billing Grace Period. A REFUND or revocation can remove access according to the verified product and transaction lineage. Tests should include valid signatures, wrong bundle, sandbox separation, duplicate UUIDs, stale ordering, unknown future event types, and replay. Apple support is implemented with limitations compared with the more battle-tested Play path, so operational monitoring and sandbox exercises remain important.
Google Play’s distinct lifecycle-notification channel.
The Apple client framework that supplies signed transaction data.
A reversal that Apple can report through a signed notification.
Verify signatures, order events, and update entitlements idempotently.
Start free