Bind a terminal to a device fingerprint | HelloBooks POS Each till is registered with a device fingerprint; transactions on a non-whitelisted device are refused. Stops cloned tills, lost tablets used for sales, and offline mode abuse.
Bind a terminal to a device fingerprint
Each till is registered with a device fingerprint; transactions on a non-whitelisted device are refused. Stops cloned tills, lost tablets used for sales, and offline mode abuse.
Part of HelloBooks POS · Multi-store / chain ops
A POS without device whitelisting is a POS where any phone with the app can settle a bill. HelloBooks binds tills to a stable device fingerprint and refuses transactions on mismatched devices — protecting against insider fraud, lost-tablet abuse, and rogue cloning.
Every detail, dialled in
Built for the till, validated against the canonical accounting engine — so every POS sale closes the books cleanly.
Stable device fingerprint
On first login, the till generates a device fingerprint from hardware identifiers and a secure-enclave key. Fingerprint is registered to the outlet; subsequent logins must match.
- Hardware-backed fingerprint
- Per-outlet whitelist
- Mismatch refused at login
- Manager-approved re-registration
Transaction-time refusal
Even after login, every transaction carries the fingerprint. A spoofed login does not survive: a transaction from a non-whitelisted device is rejected, audited, and alerted.
- Per-transaction check
- Spoofed-login refused
- Audit trail per refusal
- Real-time alert to HQ
Re-registration with audit
Phones break, tablets get replaced. A manager can approve a re-registration; the new fingerprint is whitelisted; the old is retired. Every change is audited.
- Manager-approved re-registration
- Old fingerprint retired
- New fingerprint logged
- HQ visibility
Why teams move off legacy tills
- Any device with creds can sell
- Lost tablet = open till
- Cloning impossible to detect
- No HQ visibility
- Whitelisted device only
- Lost tablet refused
- Cloning blocked
- HQ alerts on attempts
Questions, answered
What if a tablet breaks?
The manager logs in on a new device; first login flags as un-whitelisted; manager passcode approves; new fingerprint registered. Two-minute recovery.
Does this work offline?
Yes — the fingerprint is verified locally with a server-issued cert; offline transactions remain valid until reconnect.
Can HQ remotely retire a device?
Yes — single-click in the device list. Useful when a tablet is lost or stolen.
What about staff phones for delivery / runner workflows?
Same flow — staff phone is whitelisted to a delivery role, not a till role. Different scope, same mechanism.
Related POS features
Ready to automate your books?
Join 2,000+ businesses saving 20+ hours per month. Get started free — no credit card required.