Definition
Suspension is the offline state of an IoT SIM. It cannot attach until resume. The reason may be nonpayment, exhausted data, a violation, a device being taken back, or a manual hold. Payment or a renewal can clear some of those reasons. It does not clear all of them.
Why a SIM is cut off
- Nonpayment: The plan expired without renewal, or the balance is not enough, and the SIM suspends on its own. Payment usually allows an automatic or a manual resume.
- Exhausted data: The allowance is gone, overage billing is not on, or the overage cap is also used up. A new plan or a renewal is required before resume.
- Violation: The SIM was used for something prohibited, such as fraud or spam messages. The operator or the platform forces the suspension. Resume needs an appeal or a correction.
- Manual: The enterprise suspends SIMs on devices being recovered, or on a project that is ending, so the cost stops.
How operations runs it
The IoT Cloud Platform can suspend one SIM, a batch, or a filtered set. A warning can go out first, for example when data is about to run out. After the cut-off, the user pays or renews in user self-service or through the agent. A successful payment raises a payment callback and can resume the SIM automatically. Suspend and resume is the paired entry.
The command has to reach the operator
The suspend command has to arrive at the operator, or the SIM is only suspended on the screen. The log keeps who did it, when, and why. The card lifecycle updates, and card information query shows the suspended state. Nonpayment and exhausted data are usually automatic. A violation or a manual hold is started by a person. With resume, the two actions are the full suspend-and-resume control.
Paying does not clear every reason
Resume after suspension needs a payment or a renewal, and only for reasons that payment is allowed to clear. The payment callback from WeChat Pay or Alipay can then run plan provisioning and resume, which is “payment opens the SIM.” A warning before the cut-off, such as 10% of data remaining, reduces the surprise of going offline. A violation or a manual hold needs an operation log and an approval. See suspend and resume.
Where suspension sits in the lifecycle
Suspension is the move from in service to suspended on the card lifecycle. The command goes to the operator so the SIM is actually cut off. The platform can suspend by ICCID, by MSISDN, or by batch. The record is used in operator reconciliation and in audit. In B2B2C, a consumer can pay in user self-service and resume automatically when the reason allows it. An agent can suspend SIMs in their name from the agent self-service portal.
A manual suspension must not use the nonpayment auto-restore path
Suspension cuts data service, and the reason code decides whether it can open again automatically. Nonpayment and exhausted data can be lifted automatically: once the money or the new plan is in place, a resume command is allowed. A manual suspension is for taking a device back, pausing a project, or freezing for risk, and its reason code needs its own number. If the user pays for another plan, that only adds credit. It does not clear the manual reason. A violation suspension also keeps the work-order number from the operator or from risk control, and resume checks that the work order is closed. One SIM can stack reasons. If it is both unpaid and manually frozen, every reason has to be lifted before it may open. Settling the unpaid balance must not clear the manual freeze with it. When SimtoLink suspends a SIM, the operator should pick from a reason list rather than press a single “suspend” button. An automatic suspension fired by a data usage alert is written as “data exhausted,” not as “manual.”
How to check that the command reached the operator
Changing the platform status to suspended only records a local intention. A success returned by the operator is what means the network side has started refusing data. A timeout stays in “suspending,” and retries use the same request id, so two opposite commands are not created. If a query of the operator still shows usable while the local status is already suspended, the unfinished command wins. Do not let the query change the local status back to usable. The other way around, if the operator suspends the SIM first for nonpayment, the sync job should write the reason as nonpayment and stop further traffic charges, or move into the agreed suspension billing. It cannot pretend the SIM is still in normal use. A bulk suspend runs against a number-range list. SIMs in the list that are already cancelled are skipped and listed. One failure should not roll the whole batch back, and a failed SIM should not be silently treated as suspended. The suspension log used for reconciliation contains at least the identifier, the reason code, the request time, and the receipt time. Days with no receipt are not counted in an appeal that says “it was suspended, so there should have been no usage.”
Do plan days keep running while the SIM is suspended
After a suspension for exhausted data, the included amount is already used up, and the cycle may not have ended. Whether the cycle keeps running decides whether the next renewal continues on the remaining days or opens a new tier. If a manual suspension lets the cycle keep running, a project paused for a month still consumes the monthly bundle, and there is no allowance left when service returns. If the cycle freezes, the rule has to define that the freeze starts when the receipt succeeds, and how the remaining days join up after unfreeze. If the operator still rents by calendar month, a platform freeze affects only the price charged to the customer. It does not affect the cost paid to the operator. Those two books stay apart. A preinstalled SIM that was suspended by mistake in the warehouse should not count warehouse days as the user’s usage days when it is restored. If the device has already been removed and the SIM still suspends and resumes automatically every cycle, there is no final state. It should move to cancellation at expiry, rather than hang on suspension indefinitely. A long suspension that still occupies an operator-side resource needs its own cleanup job. Before cleanup, export the SIM number and the last reason, so there is an explanation later for why the SIM disappeared.