Device life cycle
Understand device status states and what each state means.
Use this page to interpret device status after onboarding, registration, or later operational changes.
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.
When to use this page
Use this page when you need to:
understand what a device status means
decide whether a device needs action
explain why a device is not yet active
Before you start
Confirm that you know:
whether the device was manually added, bulk imported, or auto-registered
whether the device already contacted the server
whether hierarchy placement is expected to be automatic or manual
Use View devices when you need to confirm the current status and related actions.
How devices move through lifecycle states
Most devices follow this pattern:
the record is created or prepared
the device contacts the server
the device is assigned to the correct hierarchy
the device remains active unless it is intentionally inactivated or deleted
If a device stops at an earlier state, the missing step usually explains the current status.
Device states
Active
The device is added to the estate, assigned to the correct node, and operating normally.
This is the expected state after successful registration and placement.
Next action:
review device details only if you need to investigate alerts, rollouts, or device health
Pending Registration
The device record exists in Device Management, but the device has not yet registered with the server.
Use this state to identify devices that were added before first contact.
Next action:
confirm the device can contact the server
confirm you did not intend to use auto-registration without a pre-created record
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.
Use this state to identify devices that still need correct placement.
Next action:
verify hierarchy rules or move the device manually if needed
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
Next action:
keep the device inactive if it may return
review the sub-status when you need to explain why it left service
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.
Next action:
restore the device only if it was deleted by mistake
leave it deleted if it should no longer be managed
How to interpret the most common states
Use these quick checks:
Pending Registration — the record exists, but the device has not completed first contact
Pending Hierarchy Assignment — the device exists, but placement still needs to be resolved
Active — registration and placement completed successfully
Inactive — the device stays in the estate, but is not currently in service
If the device state does not match the expected workflow stage, review onboarding, registration, or hierarchy setup.
Resolve a state mismatch
Use this order to avoid changing the wrong record:
Confirm the device identity and current hierarchy.
Compare the state with the expected onboarding or registration stage.
Correct connectivity or placement before changing status.
Do not delete a device to resolve a registration or hierarchy issue. Use Deleted only when the device should no longer be managed.
Common problems to check
Use these checks to narrow the issue:
A manually added device is still pending — confirm it completed first contact
An active device is in the wrong node — confirm hierarchy mapping or move it manually
An inactive device became active again — confirm whether it contacted the server after being held or repaired
A deleted device generated an alert — confirm whether the hardware should still be trying to contact the server
Result
The lifecycle status shows where a device stands operationally and the next action needed. Confirm the device identity and hierarchy before changing its state.
Common lifecycle tasks
Use these pages to act on lifecycle status:
Onboard a Device — add new devices to the estate
Registering the device — complete first-time device registration
View devices — review device status and manage device actions
Next steps
Registering the device — complete first-contact registration
Device heartbeats — understand ongoing device check-ins
View devices — review and act on current status
Last updated
Was this helpful?