Subscription events fire when a recurring billing subscription changes on your Storefront: when a customer subscribes, renews, misses a payment, is suspended or refunded, or has auto-renew changed.
See Using Webhooks for the full payload structure, which is shared across every event type.
| Event type | Display name | Description |
|---|---|---|
subscribe | Subscribe | A customer subscribed to a product |
renew_subscription | Renew subscription | A subscription was renewed |
enable_subscription_autorenew | Enable subscription auto-renew | Auto-renew was enabled for a subscription |
disable_subscription_autorenew | Disable subscription auto-renew | Auto-renew was disabled for a subscription |
refund_subscription | Refund subscription | A subscription was refunded |
suspend_subscription | Suspend subscription | A subscription was suspended |
reactivate_subscription | Reactivate subscription | A suspended subscription was reactivated |
expire_subscription | Expire subscription | A subscription expired |
subscription_payment_failed | Subscription payment failed | A payment failed for a subscription |
Suspension and reactivation
A subscription can be suspended automatically, when auto-renew is off, the term ends, and no payment is made, or manually by a reseller. Both fire suspend_subscription.
Reactivating a subscription fires reactivate_subscription. If the subscription is reactivated after its billing period has ended, a new charge is made, so you may also receive a payment event for the same subscription.
Events can arrive close togetherA single action can produce more than one event, for example a reactivation followed by a charge. Use
created_dateto put events in order, andevent_idto detect duplicates.