Biometric attendance devices with KIDUART
Most schools already own an attendance machine at the gate or the staff room. KIDUART accepts punches from those devices through a device endpoint secured with its own API key, so the punch lands in the same attendance record your registers, reports and payroll already read from instead of a monthly export nobody reconciles.
What you get
- Gate and staff-room punches land in the attendance record directly
- Staff attendance feeds leave and payroll instead of a separate sheet
- Devices authenticate with their own key, not a staff login
- RFID card numbers can be stored against the student record
- Manual correction still possible, with the change recorded
Connected with our team. Built and working, but switched on with us during onboarding because it needs your credentials, admin consent or hardware. Bring the account details to the demo and we will scope the setup call there and then.
The connection, hop by hop
How Biometric attendance devices actually works here
No hand-waving about being 'seamlessly integrated'. This is the path a single event takes, end to end.
Device is registered
Each machine is registered for your school and issued its own device key, so a device is not a user account.
Punch is captured
A fingerprint or card punch is read at the gate, the staff room or the hostel entry point.
Sent to KIDUART
The device or its connector posts the punch to the attendance endpoint using the device key.
Written to attendance
The punch is matched to the student or staff record and becomes attendance, visible in registers and reports.
Keys, data and the bill
Who holds the credentials
The device key belongs to your school and can be rotated or revoked without touching staff logins.
Where the data sits
KIDUART stores the punch time and the matched person. Fingerprint templates stay on your device.
Who gets billed
The hardware is yours. There is no per-punch charge from us.
Where it lands in the product
The modules this integration writes into
An integration is only useful if it writes into the module your staff already work in. These are the exact modules involved.
Setup, step by step
Connecting Biometric attendance devices
Tell us which attendance machines you already own
We confirm how your model can post or push punches
The device is registered and issued its own key
Map device users to staff and student records
Run a parallel week against your existing register before switching over
What you need on your side
- Attendance hardware at the gate or staff room
- Network access from the device to the internet, or a local connector
- Staff and student records already created in KIDUART
Questions schools ask
Biometric attendance devices, answered plainly
Do we have to buy new machines?
Usually not. Tell us the make and model you already run and we will confirm what it can push before you spend anything.
Where are fingerprints stored?
On your device, as they are today. KIDUART receives the punch event and the person it maps to, not the biometric template.
Why is this guided setup?
Because device models differ. Registration and mapping are done with our team once, and after that punches flow on their own.
Also in campus devices and tracking
Related integrations
See Biometric attendance devices in a live demo
We will run the connection on screen with your own scenario your fee book, your parent groups, your school accounts.
30-minute walkthrough
Booked around your school hours
Run on your own data
Your fee heads, classes and staff roles
No card, no lock-in
Nothing is charged to see the product