Deploying a resource used to charge your card first and provision second. If the provisioning then failed, you were left looking at an error message on screen and a real invoice in your billing history for something that had never been created — sometimes followed by a refund, sometimes not.
That order is now reversed. Your card is charged as the very last step, once the resource genuinely exists. If a deployment fails at any point before that, nothing is invoiced and nothing is charged, so there is nothing to refund and nothing confusing left behind in your billing history.
Two related changes come with it:
- Payment problems are caught up front. If there's no usable card on the project, or the account has an unpaid balance, the deploy is refused before anything is created rather than partway through.
- Cancelling your last resource now refunds the unused time. Removing a resource has always left a credit on your account that we apply to your next invoice. That doesn't help when it's the only thing you were paying for and there is no next invoice — so in that case the unused remainder of the period goes back to your card instead. Card processing fees are non-refundable and are deducted, as described in our payment policy.
Nothing changes about what you pay for a resource that deploys successfully.