Connectivity Lifecycle

Deactivate and resume a subscription

Temporarily deactivate a subscription when a device is lost or stolen, then resume it later when service should be restored.

This flow is designed for operational scenarios where you want to quickly protect the customer and suspend service without permanently canceling the subscription.

Best for this flow:

  • a customer reports a lost or stolen device and you need to immediately suspend service, then reactivate it once the situation is resolved.
  • temporary deactivate subscription by request of the user/support

What you will do

Lost / stolen recovery flow

Deactivate and resume, step by step

Follow the support and lifecycle journey used to protect a subscription when a device is lost or stolen, then restore service later.

01
Deactivate subscription
POST /subscriptions/{id}/deactivate
Result
200 Subscription deactivated

Deactivate the subscription to suspend service quickly and prevent unauthorized usage while keeping the subscription resource intact.

Events
subscription.deactivated
↓
02
Subscription remains suspended
Subscription state
Result
Inactive service

While the subscription is deactivated, the SIM is detached from the network but the subscription remains available to be resumed later.

↓
03
Resume subscription
POST /subscriptions/{id}/resume
Result
200 Subscription resumed

Resume the subscription when the device is recovered, replaced, or support confirms that service should be restored.

Events
subscription.active

This recipe is built for cases such as:

  • device reported as lost
  • device reported as stolen
  • temporary deactivate requested by support
  • service restoration after device recovery or SIM replacement