> 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.md). # Registering the device Use this page when a device should create its own record on first contact. Auto-registration creates the device record in **Verifone Central - Device Management** when the device connects to the server for the first time. During that contact, the device completes a key exchange and sends the details needed to create the record. If registration succeeds, the device status becomes **Active**. ### Use auto-registration when Use auto-registration when: * the device should create its record during first contact * no device record exists yet for that device * the correct root hierarchy can be determined from the device IP address If the device record must exist before first contact, use [Onboard a Device](/verifone-central-device-management/verifone-central/devices/onboard-a-device.md) instead. ### When not to use this flow Do not use auto-registration when: * the device was already added manually or imported * the placement must be decided before the device connects * the hierarchy IP address range is missing or incorrect ### Before you start Confirm that: * the hierarchy includes the correct IP address range * the device is not pre-boarded * the device can contact the Device Management server * you know which root hierarchy should receive the device Prepare these details when available: * the device serial number * the expected device network or IP range * the root hierarchy that should receive the device {% hint style="info" %} Auto-registration uses the device IP address to determine the root node for placement. {% endhint %} {% hint style="warning" %} Do not pre-board a device that should auto-register. The record must not exist before first contact. {% endhint %} ### What happens during registration During auto-registration, the device sends: * serial number * customer ID * model * IP address The server uses the IP address to match the correct root hierarchy, then creates the device record. After creation, the device is placed under that root node by default. Successful registration gives you two immediate signals: * the device record appears in the device list * the device status becomes **Active** ### Auto-registration flow Use this flow when the device registers on first contact. {% stepper %} {% step %} ### 1. Configure the hierarchy Define the IP address range for the target hierarchy. If the range is wrong, the device may register under the wrong root node or fail placement. {% endstep %} {% step %} ### 2. Confirm the device is not pre-boarded Auto-registration requires the device record to be absent before first contact. {% endstep %} {% step %} ### 3. Let the device connect When the device contacts the server, it performs a key exchange. During this exchange, the server receives the device identity and network details. {% endstep %} {% step %} ### 4. The server places the device The server uses the reported IP address to determine the root node. The device is then placed at that root node by default. {% endstep %} {% step %} ### 5. Verify the result Confirm that: * the device record now exists * the device appears under the expected root hierarchy * the device status is **Active** {% endstep %} {% endstepper %} ### How to verify success After first contact, confirm these checks in order: 1. The device appears in the device list. 2. The device is placed under the expected root hierarchy. 3. The device status is **Active**. If one of these checks fails, review the troubleshooting steps below. ### Troubleshooting Check these first: * the hierarchy IP range matches the device network * the device was not added manually before first contact * the device can reach the Device Management server Then review these related pages: * [Hierarchies](/verifone-central-device-management/verifone-central/devices/manage-hierarchies-and-groups/hierarchies.md) * [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) * [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md) #### Common outcomes Use these checks to narrow the issue: * **No device record appears** — confirm first-contact connectivity and make sure the device was not pre-boarded. * **The device appears under the wrong root node** — correct the hierarchy IP address range. * **The record exists but is not Active** — review ongoing connectivity and heartbeat behavior. ### Result The device is registered, placed under the matching root node, and ready for monitoring and lifecycle management. ### Next steps * [View devices](/verifone-central-device-management/verifone-central/devices/view-devices.md) — confirm the new device record * [Device heartbeats](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-heartbeats.md) — check ongoing connectivity * [Device life cycle](/verifone-central-device-management/verifone-central/devices/registering-the-device/device-life-cycle.md) — understand later status changes --- # 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, and the optional `goal` query parameter: ``` GET https://docs.verifone.com/verifone-central-device-management/verifone-central/devices/registering-the-device.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.