Bound Totem
The terminal can be tied to the authorized company device.
Double QR · verification at the Totem
Double-QR clock-in creates a reciprocal exchange between the employee’s phone and the site Totem. Codes change, expire quickly and the punch exists only after the Totem’s final confirmation.
Security by workflow
The terminal can be tied to the authorized company device.
The company can allow one or more public IPs for that Totem.
Coordinates and a configurable radius can block generation away from the site.
The employee phone reads the short-lived QR generated by the Totem.
The phone creates a new QR that the same Totem must read.
The punch keeps its double-QR origin, site, Totem and available evidence.
Before showing a QR it verifies device, IP and location according to configuration.
The authenticated phone reads a short-lived challenge linked to that site.
It reads the second QR and only then does the server record clock-in or clock-out.
Distributed attendance
A shop, construction site, reception or branch can use a normal tablet or PC. Every Totem keeps its own device, network and geographic rules, independent of head-office distance.
The first links the phone to a Totem challenge; the second requires the authorized Totem to confirm that phone before recording.
The code is short-lived and the flow also requires the phone response QR to be read by the authorized Totem.
The company configures them. When enabled, the Totem cannot generate a challenge unless the checks pass.
No. Modern browsers and cameras are enough; a tablet, phone or PC can become the Totem.
Create a Totem, choose the required checks and enable the double-QR employee flow.
Keep working
Move to the next free tool and keep your workflow together.