Pausing Subscriptions
Pausing lets a subscriber stop billing temporarily while preserving their account and subscription record. It’s a powerful retention tool — users who might otherwise cancel can take a break and return later.Pause a subscription
Paused status. Billing stops immediately. paused_at is set to now and paused_until is null (manual resume required).
Pause with an auto-resume date
paused_until is stored on the subscription. Run subscribd:expire-subscriptions on a schedule to auto-resume when the date passes.
Resume a paused subscription
paused_at and paused_until, and fires SubscriptionResumed.
Checking pause status
Gating feature access during a pause
A paused subscription is intentionally left in thePaused status rather than Canceled so your application can distinguish between the two and handle them differently. Gate access as appropriate for your product:
Listening to pause events
Gateway support
For gateways without native pause support, Subscribd updates the local subscription status only. Billing will not stop at the gateway level — use
CancelSubscription with a grace period instead if hard billing stop is required.
Pause vs. cancel
The SubscriptionManager component
Thesubscription-manager Livewire component includes pause and resume actions in its management UI:
Next steps
- Canceling — Permanently end a subscription
- Subscription Status — Full status reference
- Hooks and Events — All billing events