Resuming a paused VPN subscription: freeze intervals and payment records
Discuss a VPN subscription pause only when the merchant already offers and publishes that rule. Pausing is not a refund or an automatic extension. This guide covers time entitlements and accounting for lawful, authorized services, not connection methods or a claim that 稳付pay supplies a VPN pause feature.
Continue by topic
Start with the purchased product’s pause rules
Distinguish a customer-requested pause from compensation for a service outage. State eligible plans, maximum freeze duration, early-resume rules and whether traffic or add-on packs can expire during the pause. Do not retroactively promise free extensions for a product without a pause rule.
Record request time, approval time, actual suspension time and the agreed starting point. These may differ. A first support message is not automatically the approved start. The original payment remains paid according to its evidence; pausing service does not turn it into an unpaid order.
Preserve intervals, expiry values and timezone
Give each approved pause a unique operation reference linked to the original order and account. Store rule version, start and end, pre-pause expiry and the calculation used at resumption. Use an explicit timezone and consistent boundaries, such as inclusive start and exclusive end. Count overlapping intervals only once.
Illustrative rule only: a product extends expiry by actual approved frozen duration. Original expiry is November 20 at 00:00+07:00; a freeze from November 3 at 00:00 to November 6 at 00:00 is 72 hours, producing November 23 at 00:00+07:00. Calendar-day or non-extension products must follow their own original rules instead.
Separate resumption, renewal and compensation entries
Resumption references the pause. A new renewal references its own verified payment order. Outage compensation references an approval and reason, never a fabricated payment. If renewal during a pause is allowed, define its starting point beforehand and retain each source so resumption cannot overwrite a completed renewal.
Use uniqueness constraints for pause and resume operations and a local transaction for local state changes. An unknown remote authorization result stays pending: query the same operation before adding another 72 hours. Repeated payment notifications for the original order must not resume or extend it again.
Trace time calculations back to their evidence
Show purchased time, approved freezes, actual usage, separate compensation and current expiry. Every resume needs one valid pause; each renewal needs verified payment. Extensions without payment need genuine approval. Refunds follow a separate agreed process; pausing does not automatically return money.
Test repeated requests, overlapping intervals, early resumption, requests after expiry, renewal while paused, timezone displays and remote timeouts with owned data. Support needs a redacted order and timeline, not passwords. A temporary connection problem is not itself an approved freeze and should not silently change the subscription ledger.
Frequently asked questions
Does not using the service automatically extend the subscription?
No. Inactivity is not an approved pause. Apply the conditions published before purchase and the actual authorized freeze record.
Should a customer pay again if expiry is wrong after resuming?
First reconcile intervals, rule versions, concurrent renewals and authorization results. Trace paid renewals to their original orders instead of using another payment to repair the time ledger.