Full Online
Full Online binds the licence to the first machine that successfully checks in and requires continued confirmation on the schedule signed into the licence.
Activation flow
Section titled “Activation flow”- Issue the licence without collecting a fingerprint.
- The customer starts your application on the intended machine.
- The SDK sends the licence and that machine’s hashed fingerprint to DYCRYPT.
- The first successful check claims the licence.
- A later check with a different machine fingerprint is refused.
Signed timing rules
Section titled “Signed timing rules”The product defines:
- Check every: how often your application should attempt a check.
- Allowed offline for: the maximum time since its last successful check.
Both values are signed into the licence. SDK configuration may check more often or allow less offline time, but cannot weaken these limits.
If the maximum passes, the SDK returns STALE with valid: false. Show a reconnect message rather than calling the licence corrupt.
Application integration
Section titled “Application integration”Call check() on startup and again on the interval your application owns. The SDK starts no background scheduler for you. A successful result records the check so subsequent local judgments can enforce the signed maximum window.
When a customer replaces hardware, use Release machine in the licence detail. The existing installation stops matching and the next successful check claims the licence. DYCRYPT keeps the move count visible.
Choose Full Online when revocation, current installation visibility, and strict one-machine enforcement outweigh the network dependency.