Lifecycle States
What happens between a missed payment and a closed account, and how long you have at each step.
DigitalKey ERP — Docs · digital-key.co/docs/billing/lifecycle
The timeline
User created
│ lifecycle_status = registered
▼ first login
Activated lifecycle_status = active
│
▼ billing day arrives
┌────────────────────────────┐
│ Balance covers the cost? │
└────────────┬───────────────┘
yes │ no
│ └──────────────► temp_suspend
▼ │
stays active ▼ after lifecycle_temp_suspend_days (5)
suspend
│
▼ after lifecycle_suspend_days (5)
deactivated
At temp_suspend or suspend: a top-up that covers the
unpaid month collects it and reactivates the account.
The five states
| Parameter | Type | Required | Description |
|---|---|---|---|
registered | state | Optional | Created but never signed in. Not yet billed for anything. |
active | state | Optional | Normal working state. Deductions are being met. |
temp_suspend | state | Optional | A deduction failed. The first grace period is running. |
suspend | state | Optional | The first grace period expired. The second is running. |
deactivated | state | Optional | Both grace periods expired, or an administrator closed the account. |
Which states can sign in
| Parameter | Type | Required | Description |
|---|---|---|---|
registered | state | Required | Yes — signing in is what activates the account. |
active | state | Required | Yes. |
temp_suspend | state | Required | Yes. Full access continues throughout the grace period. |
suspend | state | Optional | No. Sign-in is refused, and an open session is ended. |
deactivated | state | Optional | No. Sign-in is refused. |
temp_suspend is a grace period with access. The reason is shown only after the correct password, so it cannot be used to probe which accounts exist.Grace periods
| Parameter | Type | Required | Description |
|---|---|---|---|
lifecycle_temp_suspend_days | integer= 5 | Optional | Days in temp_suspend before dropping to suspend. |
lifecycle_suspend_days | integer= 5 | Optional | Days in suspend before deactivation. |
lifecycle_warning_balance | integer= 20000 | Optional | Balance in IQD below which a low-balance warning is raised. |
status_changed_at, which is the date shown on My Account.Reactivation
There is no separate reactivation step. A top-up first collects the month that failed — in full — and only then restores a temp_suspend or suspend account to active. Paying late does not make the missed month free.
registered, so billing still starts at first login.Deactivation
When the second grace period expires, the account is deactivated: the status is set to deactivated, the account is marked inactive, and its feature subscriptions are disabled.
What is recorded
Every transition is written to the lifecycle log with the state moved from, the state moved to, and the reason — insufficient_balance, auto_daily_check, manual_suspend and so on. Timestamps are also stamped on the user record:
| Parameter | Type | Required | Description |
|---|---|---|---|
activated_at | timestamp | Optional | When the account first became active. |
temp_suspended_at | timestamp | Optional | When it entered temp_suspend. |
suspended_at | timestamp | Optional | When it entered suspend. |
deactivated_at | timestamp | Optional | When it was deactivated. |
reactivated_at | timestamp | Optional | When it was last brought back. |
status_changed_at | timestamp | Optional | When the state last changed. Grace periods are counted from here. |
Demo accounts
Staying ahead of it
- Check
next_billing_atand your balance on My Account. - Act on a
billing_deduction_failednotification the day it arrives. - Keep more than one month's cost in balance so a late top-up is not urgent.
- Remember every user is billed separately — check the team, not just yourself.
Related
- How Billing Works — the monthly cycle.
- My Account — your balance and dates.
- Notifications — the warnings you get.