> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lead.bank/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Account Statuses

> Lifecycle of a core account, who changes it, and how to observe a change.

Lead manages every core account status. You never call an endpoint to change one, and the status you read is whatever Lead has set. This page tells you what each status means and what to expect when one changes.

## Lifecycle

```mermaid theme={null}
flowchart LR
    subgraph live [ ]
        direction TB
        active <--> inactive
    end
    active --> closed
    inactive --> closed
    style live fill:none,stroke:none
```

## Statuses

| **Status** | **Description** | **Notes** |
| - | - | - |
| `active` | The account is operating normally. | Its core balance can move, and account numbers on that balance can transact. |
| `inactive` | Lead has paused the account. Funds stay on the ledger. | Account numbers on the balance cannot send or receive while the account is inactive. |
| `closed` | Lead has closed the account on the core. Terminal. | The account stays readable so historical core transactions still resolve. |

## Transitions

`active` and `inactive` move between each other. Either can move to `closed`. Nothing moves out of `closed`.

Your Lead team will tell you before an account you depend on is deactivated or closed. Status changes are rare.

## Relationship to the core balance

A core account and its core balance normally change status together. If you see them disagree, treat the balance as authoritative for whether money can move, and contact your Technical Account Manager.

Account numbers keep their own status, so an account number can show `active` and still not transact while its account is inactive. If payments fail unexpectedly, check the core account and core balance status first.

## Webhooks

Core accounts do not emit events today. Status changes are Lead-initiated and rare, so poll `GET /v2/core_accounts/{id}` at the cadence your use case needs. A daily refresh is enough for most programs.

## Related

[The Core Account Object](/products/core-account/core-account-object) · [Core Balance Statuses](/products/core-balance/statuses) · [Account Number Statuses](/products/account-number/statuses) · [Webhooks & Events](/api-reference/using-the-api/webhooks)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.