When invoices go overdue

We don't suspend on day one. We don't terminate quietly. Here's the exact ladder.

Day 0 — Due date passed

We retry the saved payment method once. If it succeeds, you're done — nothing else happens.

If it fails, you get an email saying the charge failed and the invoice is overdue.

Days 1–6 — Daily retries + warnings

Every day we:

1. Retry the saved payment method.
2. Email you that the invoice is still unpaid.

Each email tells you exactly when suspension hits.

Day 7 — Service suspended

Affected services suspend at the end of day 7. You get a final warning email a few hours before. After suspension:

• Web/business hosting — pages return a Suzko "suspended" notice. Files + database are intact.
• Game servers — server stops. World data + configs intact.
• VPS — VM powered off. Disk intact.
• Deploy projects — containers stopped. Code + env vars intact.
• Mailboxes — incoming mail is rejected. Existing mail intact.
• Phone numbers — calls/SMS rejected; number retained.
• Domains — not suspended via dunning. Domain expiry is a separate registrar timeline (see Domain renewals).

Days 8–13 — Suspension warnings

Daily warning emails. Services stay suspended. Pay the invoice and they restart automatically.

Day 14 — Service terminated

Services delete permanently. Files, databases, VM disks, container state, mailboxes — gone. We can't restore from backup at this point.

Domains are excluded (they have their own grace period at the registrar level).

How to get out

Pay the unpaid invoice from /dashboard/invoices.

• If you fix the card and the auto-retry succeeds, you're back in.
• If you pay manually, the service unsuspends within a minute.
• After day 14 termination, there's nothing to restore — you'll need to reprovision and restore from your own backups.

Avoiding the whole thing

• Keep a current card on file.
• Watch your billing email. If anything bounces, log in and check.
• Move to annual cycles if cash flow is the issue — one big charge beats twelve risky ones.