Conditional takeaway. Assume charges continue until the vendor’s documented stop-billing event occurs. Disks, snapshots, IPv4, and GPU attachments often bill after compute stops. AiXVPS does not guarantee refunds.
Working distinctions
| Action (buyer language) | Typical intent | Still verify |
|---|---|---|
| Stop / shut down / power off | Instance not running | Does compute billing pause? Do disk/IP continue? |
| Delete / destroy instance | Remove the VM | Irreversible data loss; attached volumes orphaned? |
| Delete volume / snapshot | Remove storage objects | Separate from VM delete; priced until removed |
| Cancel service / request cancellation | End the subscription/account product | Effective date, refund window, promo clawbacks |
| Release floating IP / GPU | Drop add-ons | Whether they auto-release on VM delete |
Checklist before you pay (and before you leave)
- Find the exact doc that defines stop vs delete for your SKU; save URL + access date.
- Hourly products: minimum charge, rounding, and when the meter ends.
- Monthly/annual: cancel deadline relative to renewal; timezone.
- Intro pricing: what happens at renewal; whether cancel is allowed mid-term.
- Residual billables: disk, snapshots, backups, IPs, licenses, GPU.
- Refund policy: days, partial months, fees, exclusions.
- Data export: take backups before delete—see backups vs snapshots.
- Confirmation: email/ticket/UI state that proves cancel completed.
Community clues
“Still billed after stop” reports are prompts to re-read the current stop/delete article for that cloud—not automatic proof of fraud. Match product generation and date; label conflicts as unresolved until docs and invoices agree.
Cost tool link
Exit risk belongs next to annual cash-due-today on the total cost worksheet. If cancel terms are unknown, say so—do not model refunds as $0 recovered by default.