Mobile
Device credential, platform attestation, and per-transaction user approval when required.
Access and Attendance can involve the same user, gateway, and moment, yet they are not the same decision. MesaiGo produces the evidence once, and each product evaluates it under its own policy.
The mobile device signs identity and transaction context. The gateway witnesses only the local interaction it observed. The server evaluates assignment, freshness, proximity, and policy.
Device credential, platform attestation, and per-transaction user approval when required.
Correct entry-point discovery, fresh challenge, BLE/UWB evidence, and field witness.
Replay consumption, policy, assurance, duplicate-request control, and final decision.
Evidence used, policy version, decision, and product outcome.
An access approval may unlock a door; whether attendance starts is determined by shift and attendance policy. This separation preserves correction, audit, and legal boundaries.
Authorization, actuation, physical passage observation, and security alarm.
Attendance event, shift calculation, exception, approval, and payroll output.
See every step, the evidence it uses, and the decision authority.