Hardware and mobile

Keep your time clocks,
add the smartphone.

The client keeps its terminals and badges. We connect through one of four routes, only replace what is at end of life, and sixteen clocking modes coexist in the same platform.

Reuse what exists

Four routes to connect your hardware.

Replay a scenario
Four routes to connect existing hardware, without replacing itClient’s existing hardwareInstalled by LuxappsNetworked terminalany documented brandRoute 1: SDK or push to the APICurrent time softwareAPI, web services, exportsRoute 2: read what existsAccess controlcontroller, door readersRoute 3: Wiegand or OSDPClosed or broken terminalbadges are read againRoute 4: USB reader, NFC tabletSite gatewayoffline bufferencryptionnormalisationPlatformrules, AI,workflows

A client often combines several routes: recent terminals directly, the old software during transition, equipped doors through access control.
Badges already issued
TechnologyFrequencyReadable by a smartphoneWhat we do with it
EM4100, HID Prox125 kHzNoKept via the existing terminal or a 125 kHz reader
MIFARE Classic13.56 MHzIdentifier yes; sectors depending on the phoneKept by identifier, migration advised
MIFARE DESFire EV1 to EV313.56 MHzYes (ISO 14443), key-protected dataKept, basis for the secure badge
HID iCLASS, Seos13.56 MHzSeos via the HID mobile ecosystemKept
LEGIC prime, advant13.56 MHzDepending on readersKept via the existing terminal
PIN code, QR codeN/AQR yesFallback options

A 125 kHz or MIFARE Classic badge is easy to copy: we keep it for time recording, not for sensitive areas, and plan its migration.

Migration without disruption

  1. Inventory: terminals, firmware, badges, software, exports and current rules.
  2. Connector: route chosen per site, gateway installed.
  3. Parallel run: old and new calculate side by side over one or two payroll cycles, every gap is explained.
  4. Cut-over: the old software becomes read-only, history is migrated.
  5. Gradual renewal: only end-of-life terminals are replaced, by a compatible brand or a tablet.
Every clocking mode

Sixteen modes, a proof level for each.

An employee can badge at the office, clock in on the phone on assignment and declare training in the same month. Each event keeps its source and proof level, which the AI uses to target its checks.

ModeHow it worksFor whomProof level
Badge terminalBadge shown at the wall terminalFixed sitesStrong
Biometric terminal (option)Badge plus fingerprint checked on the cardHigh-fraud-risk sites, after a DPIAVery strong
Door readerEntries and exits derived from door eventsEquipped buildingsStrong
Kiosk tabletNFC badge, QR code or PINShops, small sites, construction sitesStrong
Mobile app with zoneZone, Wi-Fi or beacon checked at that momentMobile staff, sites, teleworkMedium
Phone on NFC tagThe phone taps a tag fixed at the workplaceHome care, cleaning, securityStrong
Phone as badgeThe phone emulates the badge on a compatible readerHeadquarters, upgraded sitesStrong
Team leaderThe leader clocks in the team by reading badges on a phoneConstruction, temp staffMedium
Web portalButton in the portal, SSO sessionOffices, teleworkMedium
Work sessionStart and end suggested at login, confirmed by the employeeOffices, teleworkMedium
Teams or assistant“I’m in”, “break”, “I’m off”Connected staffMedium
Voice serverCall a number with a personal codeSites without data networkLow
TimesheetEntry of hours, projects or clientsExecutives, consultantsLow
Exception-basedThe schedule applies, only gaps are enteredStable fixed hoursLow
Tachograph dataImport of driving and rest timesRoad transportStrong
Production timeStart and end per production order or taskIndustry, workshopsStrong

Exception-based clocking is only used in Luxembourg after validation: the Article L.211-29 register requires the start, end and length of work each day.

Mobile focus

The smartphone as a time clock, the NFC tag as proof.

The smartphone replaces or complements the time clock in four ways, and its NFC chip provides proof of presence without GPS: the phone taps a tag fixed at the workplace, and the tag signs each read.

Four ways to clock in with a smartphone, including NFC tags without GPSEmployee actionProof of presenceServer check1. App and zoneiPhone and AndroidTaps Clock inin the appZone, Wi-Fi or beaconread at that momentIn the zone?position not kept2. Phone on tagNFC read, no GPSTaps the phoneon the NFC tagUnique signed messagefrom the tag (AES)Signature and countervalid?3. Phone as badgedepending on the phoneShows the phoneto the readerVirtual badgeHCE or walletCompatible readerbadge recognised?4. Kiosk tabletreads current badgesShows a badge,a QR or a codeFixed tabletat the site entranceTrusted deviceand known badge?
The four uses combine: the same employee can badge at the depot, tap a tag at the client and clock in from the app while teleworking.

NFC clocking, step by step

  1. A secure NFC tag is fixed where work starts: site entrance, vehicle, plant room, a beneficiary’s home with their consent.
  2. The employee taps the phone: the app reads the tag message (identifier, counter, AES signature).
  3. The server checks signature and counter: a replayed message or counterfeit tag is refused.
  4. The punch is recorded with the place linked to the tag, with no location tracking.
  5. Against removal, a tamper-evident variant reports any opening.

Anti-fraud without surveillance

RiskCountermeasure
Fake location (GPS spoofing)Spoofed location detection, Wi-Fi or beacon as a complement
Modified phone, cloned appDevice attestation (Play Integrity, App Attest)
Clocking for a colleagueAccount bound to a device, MFA at enrolment, alert if two employees clock in from the same phone
Copied or replayed tagUnique signed message at each read
Phone time changedServer time, gap detected when the network returns
Photo of a QR codeDynamic QR code renewed every few seconds
Offline

Offline or not, the same checks.

Replay a scenario
Offline or not, every mobile punch passes the same checks1. PunchNFC tag read orzone checkedNetwork?3. Encrypted sendto the serveryes2. Local queuesigned timestamp,sent on returnnonetwork back4. Checksdevice attestedlocation not spoofedtag signaturetag counterconsistent timeno duplicateAll valid?5. Recordedday recalculatedyes6. To be confirmedemployee explains,manager decidesnoif accepted

In a basement or a dead zone, the punch is timestamped and signed on the phone, then sent when the network returns; the server corrects the time and flags any gap.

Privacy by design

LuxApps Pointage

Your time clocks, your rules, your payroll.

Show us your hardware and your agreements: we show you the path to payroll, compliance included.

Book a demo