SecureAccess

Attendance that cannot be handed to a colleague.

What you just saw

A palm at the turnstile, and the gate opens.

A palm held at the turnstile and the gate opens on a sub-1 s match: no badge tap, no queue for a card reader.

sub-1s

gate verification

40+/min

throughput per lane

±25°

rotation tolerance

0

cards issued

The credential problem

Every credential you can issue, someone can pass on.

Access control on an industrial site is not really a hardware problem. It is that the thing being checked at the gate is separable from the person it belongs to.

01

The badge that gets lent

A card proves possession, not presence. One worker carrying two cards through a turnstile is the single largest source of attendance fraud on a shift-based site, and no card reader can detect it.

02

The badge that gets lost

Every lost card is a replacement, a re-issue queue at the security desk and a window in which someone else can walk in on it. A palm cannot be left at home, handed over at the gate or found in a car park.

03

The register that gets signed later

Manual attendance is retrospective and unverifiable. Palm verification writes the record at the moment of entry, with the terminal, the timestamp and the match result attached to it.

Gujarat pilot, Track A: six months, three terminals

250-400

workers enrolled

95%+

reduction in buddy-punching

sub-1s

unlock at the turnstile

92%

worker satisfaction with the gesture

Environment and throughput

Rated for shift change on a dusty floor.

A gate reader is judged at 7:55am, when three hundred people arrive at once with dust on their hands. Because the read is sub-dermal, the conditions that defeat fingerprint sensors on an industrial site do not apply here.

Palm attendance terminal in use at a workplace gate
SecureAccess gate and enclosure specification
Gate verificationSub-0.7-1.0 sMatching runs on the reader, so the turnstile does not wait on a network round trip to head office.
Throughput40+ people per minute, per laneSized for shift change, when an entire line arrives inside a ten-minute window.
Capture envelope5-15 cm, +/-25 degContactless, with no cradle or guide. A worker walking at pace does not have to stop and align a hand.
Surface toleranceUnaffected by grime, wear or moistureThe vessel map is sub-dermal, so worn fingerprints, dust, oil and callused hands are not a failure mode.
EnclosureIndustrial shop-floor ratedDust, wash-down adjacency and continuous shift use, on a pedestal or a door frame.
FeedbackPerimeter LED halo, piezo chimeVisual and audible confirmation that stays legible in a noisy plant and under mixed lighting.
Gate interfaceSDK plus relay outputDrops into the turnstile or door controller already installed. The gate opens on the signal it accepts today.

Enrolment and cutover

Nobody has to trust it on day one.

Cards stay live through the parallel run, so the decision to retire them is made against your own reconciled attendance data rather than a vendor claim.

  1. 01Roster importEmployee identifiers come from your HRMS. No biometric data is involved in this step and none leaves the site.
  2. 02Supervised captureOne session per person at a desk-mounted reader, witnessed by HR or security. Each palm resolves to an irreversible record that cannot be turned back into an image, and the captured frame is destroyed on the device as soon as that record exists.
  3. 03Parallel runCards stay live while both records are written. The two attendance logs are reconciled side by side, which is where the buddy-punching gap becomes visible in your own data rather than in ours.
  4. 04Retire the cardThe badge stock, the re-issue desk and the replacement budget go with it. Supervisor override remains as the exception path.

Attendance and audit integration

Attendance integration and data handling
Attendance recordPer-person entry and exit eventsEach event carries the terminal identifier, the timestamp, the match result and the measured latency.
HRMS syncEvent webhook or scheduled exportAttendance lands in the payroll system you already run. PalmPay is not a system of record for employment data.
ExceptionsSupervisor override, recordedLogged against the shift and the supervisor, never against the template. An override is an audit row, not a gap.
Replay protectionA captured gate request cannot be replayed against the controller or the attendance endpoint.
RetentionTemplates onlyThere is no raw biometric image in the datastore to disclose, subpoena or leak. DPDP Act alignment starts here.