Biometric compatibility depends on the verification method

1. Mobile fingerprint verification

On supported mobile devices, EkamQR can use the operating system's biometric capabilities as part of the attendance verification flow. Availability depends on the device, operating system, enrolled biometrics and security capabilities. The application should not be treated as a replacement for the operating system's biometric security.

2. Biometric attendance devices

Connected attendance devices can vary by manufacturer, protocol, firmware, verification modes and supported data formats. Device connectivity does not automatically guarantee that every biometric operation is compatible.

3. Fingerprint and face templates

Biometric templates can depend on vendor algorithms, template versions and device families. A template enrolled on one device may not be accepted by another device even when both devices support fingerprint or face verification. Compatibility should be tested rather than assumed.

Do not transfer biometric templates across device families in production until enrollment, upload, matching and deletion behavior has been validated on the exact models and firmware involved.

4. Recommended validation before rollout

1. Confirm the exact device model, firmware and communication mode.
2. Test employee creation and device-code mapping.
3. Test fingerprint/card/other supported template upload and download where required.
4. Verify punches reach EkamQR with correct employee and timestamp mapping.
5. Test night/cross-date shifts and failure/retry behavior.
6. Document any device-specific limitations before production use.

5. Re-enrollment and security changes

Mobile or trusted-device security changes can require re-enrollment. For example, a changed trusted biometric key or device security state may invalidate an earlier enrollment to prevent silent reuse of outdated trust.

6. Compatibility check