How device binding works
HWID binding helps restrict a license to the device that first authenticates successfully.
First successful authentication
If the license has no stored HWID and has never been activated, the server records the supplied device identifier, marks the activation time and starts any configured timed expiry from that moment.
Later authentication
The same license continues to work when the same device HWID is supplied. A different HWID returns HWID_MISMATCH.
Authorized reset
When a legitimate hardware change or PC replacement is required, an authorized dashboard action can clear the stored HWID. The next successful authentication binds the license again.
Choose a stable identifier
A device identifier should be stable enough for your licensing policy but should not collect more device data than your application actually needs.