Replace Keycards With Smartphones Across Your Texas Facilities.

Mobile credentials are digital identifiers stored on a smartphone that authenticate at a door reader the same way a proximity card would, but without the physical card. They transmit via Bluetooth Low Energy or NFC. The credential lives in the phone's secure enclave or a wallet app, so it cannot be cloned the way a standard Wiegand card can. Platforms like HID Mobile Access, Allegion ENGAGE, and Brivo mobile credentials all use encrypted cryptographic keys that rotate automatically, making mobile credentials more secure than static card data.

Yes, on compatible platforms. HID Mobile Access supports Apple Wallet and Google Wallet for facilities that have deployed HID readers with firmware supporting that protocol. Allegion ENGAGE and Dormakaba readers also support wallet-based credentials on select hardware. Not every reader on every platform supports wallet integration yet: the access control panel and reader firmware must both be current. We verify hardware compatibility during the design phase and advise when a reader upgrade is required to enable wallet-based credentials.

Yes. Most mobile credential implementations support Express Mode, where the credential broadcasts passively over Bluetooth without requiring the user to open an app or unlock the phone. The reader picks up the credential as the user approaches. Some deployments require a tap, gesture, or app open for higher-security areas. We configure the authentication mode per door based on your security policy: express mode at general entry points, tap-to-open at restricted areas.

Issuing a mobile credential typically takes under two minutes from your access control dashboard. You enter the person's name and email address, select their access groups and schedule, and trigger a credential invite. The recipient receives an email or SMS with a link to install the credential to their phone. For contractors, you can set the credential to expire automatically on a specific date, eliminating the step of manually revoking access after the job ends.

Revoking a mobile credential takes under 30 seconds from the management dashboard. Unlike a lost card, which can be used until someone notices and deactivates it, a mobile credential on a lost phone can be revoked immediately and remotely. If the phone is recovered, the credential can be reissued in minutes. For phones without screen locks, most platforms allow you to push a remote wipe of the access credential without wiping the entire device.

No. The authentication happens locally between the phone and the reader. The reader stores the current valid credential list and validates against it without contacting the cloud at every access event. Credential updates, revocations, and new issuances sync from the cloud to the reader at regular intervals, typically every few seconds to a few minutes depending on the platform. If the internet connection at the site drops, access continues using the cached credential list.

Yes. Most cloud platforms support mixed-credential environments where some users carry cards and others use mobile credentials on the same system. This is common during transitions: legacy employees retain cards while new hires receive mobile credentials. Readers that support HID Seos or OSDP can read both card and mobile credentials without hardware replacement. We scope the coexistence configuration and identify any readers that need firmware or hardware updates to support dual-mode operation.

In most configurations, yes. Standard 125 kHz proximity cards transmit a static ID that can be cloned with inexpensive hardware available online. Mobile credentials use encrypted, rotating keys stored in the phone's secure enclave that cannot be copied. NFC and Bluetooth transmissions are encrypted end to end. The phone itself adds another layer: most mobile OS security frameworks require biometric or PIN authentication before the credential can transmit. The practical security level depends on reader firmware version, credential protocol, and how users configure their phone lock screens.