1. Device enrollment
The organization registers the employee and the phone key protected by iOS or Android.
Step-by-step verification
An access or attendance transaction is verified in eight steps.
MesaiGo does not consider “the phone saw the gateway” sufficient. Every attempt checks the phone, gateway, entry point, time, required security level, and organization rules together.
8Verification steps
2Verification levels
1Final server decision
0Hidden security downgrades
One complete record for each attempt
Phone, gateway, and server data must belong to the same attempt.
Information from the phone, gateway, and server is not combined merely because it appeared at the same time. Every piece is linked to one transaction, so data from another attempt cannot be reused.
2. Entry point
The app verifies the relevant server, entry point, and gateway.
3. New single-use request
The gateway creates a request that works only once and expires shortly after it is created.
4. Local approval
When an organization rule requires it, the user approves the specific transaction on the phone.
5. Proximity
Standard BLE communication or a secure UWB distance measurement is completed between the phone and gateway.
6. Gateway verification
The gateway signs only the live interaction it observed and submits it to the server.
7. Decision
The server checks identity, whether the request expired or was already used, device assignment, and organization rules together in one operation.
8. Result record
The signed final result is written to the transaction history together with the security level used.
Choose the verification level that fits your needs.
Compare Standard and High Assurance by hardware, user approval, and the security each provides.