Did Fail to Renew

Learn about the DID_FAIL_TO_RENEW App Store Server Notification V2. Fired when a subscription renewal fails due to a billing issue.

App Store Server Notifications V2Subscriptions
DID_FAIL_TO_RENEW

The DID_FAIL_TO_RENEW notification fires when Apple fails to charge a customer for their subscription renewal. This is typically due to an expired or declined payment method.


When does it fire?


This notification triggers when the billing attempt at the end of a subscription period fails. It may include a subtype indicating whether a grace period is active:


  • Grace period active — the customer still has access while Apple retries billing
  • No grace period — access may be revoked if billing isn't resolved

Apple will retry billing multiple times over the following days before eventually expiring the subscription.


Payload highlights


The signed transaction info shows the last successful transaction, while the signed renewal info indicates the grace period status and the next retry date. This helps you understand the customer's current access state.


How Yeethook helps


Billing failures are involuntary churn — the customer didn't intend to cancel. Yeethook alerts your team immediately so you can take action, such as sending a payment update reminder or adjusting access gracefully.


Common use cases


  • Detect involuntary churn before it becomes permanent
  • Send payment update reminders to affected subscribers
  • Monitor billing failure rates across regions and payment methods
  • Track grace period resolution rates

Enrichment with p8 key

With a p8 key, Yeethook can enrich billing failure events with the subscriber's payment history and previous billing retry outcomes.

Related Events

Get this event in Slack

Connect Yeethook to receive Did Fail to Renew notifications in your Slack channels.

Get Started Free