Registering the device
Let a device create its record automatically on first contact.
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 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
Do not pre-board a device that should auto-register. The record must not exist before first contact.
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.
How to verify success
After first contact, confirm these checks in order:
The device appears in the device list.
The device is placed under the expected root hierarchy.
The device status is Active.
If one of these checks fails, review the troubleshooting steps below.
Troubleshooting
Check these in order:
Confirm the device can reach the Device Management server.
Confirm that no device record existed before first contact.
Confirm the hierarchy IP range matches the device network.
Correct the failed condition before waiting for the next contact. Do not manually add the device while it is expected to auto-register.
Then use:
Common outcomes
Use these checks to narrow the issue:
No device record appears — check connectivity, then confirm the record was not pre-created.
The device appears under the wrong root node — correct the hierarchy IP range before further placement work.
The record exists but is not Active — review the current lifecycle state and heartbeat behavior.
Result
The device is registered, placed under the matching root node, and ready for monitoring and lifecycle management. Confirm all three checks before rollout work.
Next steps
View devices — confirm the new device record
Device heartbeats — check ongoing connectivity
Device life cycle — understand later status changes
Last updated
Was this helpful?