NG-Key
NG-Key
Secure mobile enrollment and access control
Support

Get help with NG-Key, mobile access, readers, and rollout questions.

Use this page for operational questions, onboarding help, reader rollout topics, and support requests around mobile credentials, smart readers, and access workflows.

FAQ

How does the mobile key flow work at the door?

A user presents the phone via NFC, confirms locally with Face ID or device biometrics, the device signs the access challenge using a bound credential, and the reader can approve the request to open the door.

What do FIDO2 and WebAuthn mean here?

WebAuthn is the web standard used by apps and browsers to create and use public-key credentials. FIDO2 combines WebAuthn with authenticator protocols, enabling phishing-resistant authentication where private keys stay protected on the user device.

Why is this stronger than conventional RFID?

Conventional RFID cards often rely on static identifiers or secrets that can be copied if the medium is weak or poorly managed. NG-Key uses device-bound credentials, local user verification, and signed challenges, which significantly raises the barrier against cloning, replay, and credential sharing.

Which reader technologies are supported?

The readers support Legic and are based on a Legic 6300 chip. A MIFARE variant is also available. The hardware is Apple certified for supported mobile access scenarios.

App help
Mobile onboarding

Guide users from invitation to enrolled phone, bound credential, and production-ready access state.

Reader rollout

Get help with QR claim setup, NFC mobile key rollout, reader grouping, and operational provisioning.

Authentication troubleshooting

Support can help with biometrics, passkeys, discoverable credentials, and reader-side mobile authentication behavior.

Operational support

Use the contact form for rollout planning, technical assistance, product questions, and access-control deployment topics.