Service Stopping and Deletion when Invoice not Paid #365

Open
opened 2026-01-22 13:57:42 +00:00 by tobru · 0 comments
Owner

Stories

As a platform owner, I want to make sure no unpaid instances are wasting compute resources

Implementation Notes

Sometimes it can happen that invoices don't get paid. We could, of course, manually check and react, but after a certain growth, this isn't feasible anymore.

We need an automated process that takes action when an invoice isn't paid.

Invoices are per organization, so actions involve all instances running in an organization.

  • Regularly (once per day) check the invoice state and compare it with the payment target date.
  • When overdue, send reminder emails
  • After a few days of non-payment, pause (scale to 0) all instances and lock the account from manual editing, so that the user cannot just log in and unpause all instances again
  • If the invoice still isn't paid after a few more days, initiate the decommissioning process. We might separate this into a manual action at this time.
## Stories _As a platform owner, I want to make sure no unpaid instances are wasting compute resources_ ## Implementation Notes Sometimes it can happen that invoices don't get paid. We could, of course, manually check and react, but after a certain growth, this isn't feasible anymore. We need an automated process that takes action when an invoice isn't paid. Invoices are per organization, so actions involve all instances running in an organization. - Regularly (once per day) check the invoice state and compare it with the payment target date. - When overdue, send reminder emails - After a few days of non-payment, pause (scale to 0) all instances and lock the account from manual editing, so that the user cannot just log in and unpause all instances again - If the invoice still isn't paid after a few more days, initiate the decommissioning process. We might separate this into a manual action at this time.
tobru added this to the Roadmap project 2026-01-22 13:57:45 +00:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
servala/servala-portal#365
No description provided.