An active server debits the same USD wallet when its period ends. While it is still active, you get one email each day for the three days before that charge. The subject names the hostname and how many days are left. The body names the dollar amount the wallet will debit.
Those notes are the window to top up. They are not extra days after the due time. Turning the server off does not stop the charge. Billing still runs while the box is powered down.
Top up before the period ends. The customer floor is still $20, even when the plan itself costs less than that.
When the period ends
If the wallet covers the charge, the server stays active and the next renewal date moves forward. You get a mail that the renewal went through. If the server had been off because of a short balance and the charge then succeeds, power comes back on with that renewal.
If the balance is short, the mail says the period ended and the instance is being destroyed. Disks and the IPv4 are gone. Unused prepaid time is not refunded. A new deploy is a new disk.
If destroy does not finish
A failed destroy can leave the row suspended and powered off. That is a different state from the three reminder emails. Add funds only when the instance notice says to, then wait. If the wallet already shows a balance and the box stays off, open a ticket and name the hostname. The held-box steps are in When a VPS is suspended, add funds.
Destroying it yourself
Destroy on the instance page deletes the host the same way an unpaid period does. Disks and IPs are gone. Unused prepaid time is not credited back to the wallet. A ticket can ask the desk to cancel a box, and the same rule applies.
One wallet pays every live server. A balance that covers one plan can still be short for two. The quote lock and the coins that fund that wallet are in A crypto quote locks when the invoice is created. Billing answers that are already public sit on the FAQ.
Comments