billing.account_locked
Account hits 60-day lockdown.
project_id is always null for billing events.When this fires
The creator's account hits the 60-day past-due lockdown. New signups on my.memberpass.net/{handle} are blocked and the dashboard surfaces a lockdown banner.
Required ability
billing:read — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "billing.account_locked",
"created_at": "2026-05-18T00:00:00Z",
"api_version": "2026-05-01",
"project_id": null,
"data": {
"creator_id": "cre_01HX...",
"past_due_since": "2026-03-19T00:00:00Z",
"locked_at": "2026-05-18T00:00:00Z"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always billing.account_locked for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | null | Always null — account-level event. |
data.creator_id | string ULID | Creator that was locked. |
data.past_due_since | ISO 8601 timestamp | When the past-due state began. |
data.locked_at | ISO 8601 timestamp | When the lockdown took effect. |
Caveats
- Lockdown is reversible: a successful payment fires
billing.invoice_paidand the lockdown is cleared automatically. There is no dedicated "account_unlocked" event. - Existing subscribers retain access to project resources during lockdown; only new signups are blocked.
Related events
billing.grace_period_warning— 7-day notice predecessor.billing.invoice_paid— automatic unlock signal.- Billing events overview — back to family overview.
How is this guide?