> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/registering-the-device/device-life-cycle.md).

# Device life cycle

Device lifecycle shows the current operational state of a device in **Verifone Central - Device Management**.

The device status changes as the device is added, registered, assigned, inactivated, or deleted.

### Device states

#### Active

The device is added to the estate, assigned to the correct node, and operating normally.

#### Pending Registration

The device record exists in Device Management, but the device has not yet registered with the server.

#### Pending Hierarchy Assignment

The device is added to the estate, but hierarchy assignment is still pending.

Assignment can happen either:

* manually
* automatically through IP address range mapping

By default, these devices are placed at the root hierarchy level until assignment is resolved.

#### Inactive

The device remains part of the estate, but it is not currently active.

This state is typically used when the device is out for repair or held in a spare pool, but may return later.

If the device contacts the server again, its status automatically changes to either **Active** or **Pending Hierarchy Assignment**.

If automatic device movement is enabled, the device also moves to the correct hierarchy node.

**Inactive sub-statuses**

The system can mark an inactive device with these sub-statuses:

* **Device Swapped** — the device has been replaced
* **Device Missing** — the device has not contacted the server for a defined period

#### Deleted

The device is removed from the estate, but its record is retained for audit purposes.

Deleted device details remain available through **Deleted Devices** in the UI.

If a deleted device sends a heartbeat:

* the server ignores the heartbeat
* the system generates a **Deleted Device Contacting** alert

The device is not expected to reconnect in normal operation.

Its application parameters are retained, and the device can be restored from **Deleted Devices** if it was deleted by mistake.

{% hint style="info" %}
Use **Inactive** when the device may return to service. Use **Deleted** when the device should no longer be managed in the estate.
{% endhint %}

### Result

The lifecycle status shows where a device stands operationally and what action, if any, is needed next.

### Common lifecycle tasks

Use these pages to act on lifecycle status:

* [Onboard a Device](/verifone-central-device-management/verifone-central/devices/onboard-a-device.md) — add new devices to the estate
* [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) — complete first-time device registration
* [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) — review device status and manage device actions

### Next steps

* [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md)
* [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md)
* [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/registering-the-device/device-life-cycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.