Mobile
A phone key that cannot be copied, operating-system checks that the app and key are genuine, and user approval when required.
MesaiGo Platform
Use the same phone and gateway checks for access and attendance.
MesaiGo verifies that an enrolled phone interacts with the correct gateway in real time. Access approval and attendance recording evaluate that shared verification under separate rules.
01Enrolled phone key
02Phone-to-gateway connection
03Security rules
04Recorded transaction result
What each component verifies
The phone, gateway, and admin panel cannot grant access by themselves.
The mobile app signs the device and transaction. The gateway verifies only the live interaction it observed. The server checks device assignment, request freshness, proximity, and organization rules.
Gateway
Finds the correct entry point, creates a single-use request, and verifies the BLE/UWB interaction.
Server decision
Rejects old or repeated attempts and checks device assignment, access rules, and the required verification level.
Transaction history
The checks performed, rules used, server decision, and outcome are recorded.
Separate decision rules
Access and Attendance use the same verification but make separate decisions.
An access approval may unlock a door; shift and attendance rules separately determine whether attendance starts. This prevents access and attendance records from being mixed and keeps every correction visible.
Access outcome
Access approval, relay command, sensor result, and security alarm.
Attendance outcome
Attendance record, shift calculation, missing or incorrect record, approval, and payroll output.
See how the system works step by step.
Follow how the phone, gateway, and server verify an access or attendance transaction.