Skip to main content

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

The subscription enters 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

This resumes billing at the gateway, clears paused_at and paused_until, and fires SubscriptionResumed.

Checking pause status

Gating feature access during a pause

A paused subscription is intentionally left in the Paused status rather than Canceled so your application can distinguish between the two and handle them differently. Gate access as appropriate for your product:
Or use Laravel’s Gate/Policy:

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

The subscription-manager Livewire component includes pause and resume actions in its management UI:
See Livewire Components for the full component reference.

Next steps