Skip to content
Mobile Access Credentials
Mobile Access Control Integration
The business case for mobile credentials is rarely the technology. It is that roughly one in ten cards goes missing every year, that every replacement costs administrative time, and that a lost card sits unreported for days while a lost phone gets reported in minutes.
Evolution deploys mobile access credentials as part of an integrated access control estate. That means credential lifecycle, reader capability, network design and fallback all planned together.
Our Mobile Access Credential Solutions
Assessment of whether your existing readers and controllers can support mobile credentials, including OSDP capability and BLE/NFC hardware, and what needs replacing if not
Credential platform selection, including vendor lock-in and licensing cost analysis over the system’s life
Deployment across Apple Wallet and Google Wallet employee badge, and vendor platforms including HID Mobile Access
Enrolment and revocation process design, integrated with HR onboarding and offboarding
Phased migration from physical credentials, running both in parallel during transition
Fallback design for lost, flat and unenrolled devices
Reader upgrade programmes to BLE and NFC capable hardware
Integration with visitor management for temporary mobile credentials
Choosing Mobile Access Credentials in the Aliro Era
Until recently, choosing mobile credentials meant choosing a vendor’s cloud and staying there. Readers, credentials and management platform came as a bundle, and moving later meant replacing all three.
In February 2026, the Connectivity Standards Alliance released Aliro 1.0, an open credential standard developed with founder members including Apple, Google, Samsung, HID, ASSA ABLOY, Allegion and dormakaba. It uses NFC or Bluetooth Low Energy with ultra-wideband, and is built on public key infrastructure with mutual authentication between reader and device, supporting offline credential sharing and revocation.
The practical consequence for anyone specifying now: the industry is moving toward credentials that are portable between vendors. If you are about to commit to a reader estate with a ten-year life, that materially affects what you should buy this year.
Aliro does not make your current platform obsolete. It changes the calculation on what you buy next. We will map your existing estate against the standard’s trajectory and tell you plainly which of your planned purchases are safe and which are worth delaying six months.
Security Controls for Mobile Credentials
Mobile credentials are, correctly implemented, more secure than the cards they replace. The credential is stored in the device’s secure element, protected by the device’s own biometric or passcode authentication, transmitted over an encrypted channel, and revocable centrally in seconds.
That is conditional on implementation. The questions that matter:
- Where is the credential stored, and is it bound to the device?
- What happens when the device is lost, wiped or replaced?
- Does revocation propagate to offline readers, and how quickly?
- Is enrolment tied to a verified identity, or to an email address anyone could receive?
- What is the fallback when someone’s battery is flat, and does that fallback undermine the control?
We work through each of these before deployment rather than after the first incident.
Mobile Access Control Technology We Integrate
Mobile credential deployment depends on what your access control platform supports and what your reader estate can read.
We work with HID for mobile credentials and mobile-enabled readers, Suprema for biometric and mobile-capable readers, and Gallagher, LenelS2 and Software House C•CURE 9000 at platform level. For workplace and tenant experience layers where mobile access sits alongside booking, wayfinding and visitor flow, we work with Sharry, SwiftConnect and smartspaces. Where a cloud-native platform is the right fit, Brivo and Genea both support mobile credentials natively.
Live Access Control Migration with Mobile Credentials
Grade A Dublin office building, live migration, mobile credentials deployed
A Dublin commercial property owner needed to move a flagship building from legacy ACT access control to C•CURE 9000, without interrupting tenant operations for a single working day, and to introduce mobile credentials as part of the same programme.
Live migration on an occupied Grade A building is the difficult case. Tenants expect their card to work on Monday morning whether or not the system behind it changed over the weekend. Evolution designed and ran the migration in orchestrated stages, with the legacy and new platforms operating in parallel through the transition.
HID mobile-enabled readers and HID mobile credentials were deployed alongside the platform change, giving tenants smartphone access. Lift destination control was integrated to the access control platform to manage vertical transport, and a second-floor tenant fit-out was brought onto the building-wide base build system so that tenancy and landlord areas run under one security estate rather than two.
The asset management team highlighted that migrating without disrupting tenants was the critical requirement for a building of that grade, and that the mobile credentials were particularly well received.
FAQs About Mobile Credentials
Generally yes, when implemented properly. A mobile credential is stored in the device's secure element, requires the user's biometric or passcode to present, is transmitted encrypted, and can be revoked instantly. A legacy proximity or MIFARE Classic card offers none of this and can be cloned cheaply. The security advantage comes from the implementation, not from the phone.
Usually some, not all. Mobile credentials require readers with BLE or NFC capability. Many estates have a mix, and migration can be phased by zone, starting with the highest-traffic or highest-risk entrances while cards continue to work elsewhere.
An open mobile credential standard released as version 1.0 by the Connectivity Standards Alliance in February 2026, with founder members including Apple, Google, Samsung, HID, ASSA ABLOY and Allegion. It aims to make mobile credentials interoperable between vendors rather than tied to a single manufacturer's ecosystem.
On supported platforms, yes. Employee badge in Apple Wallet and Google Wallet is available through several access control vendors. Whether it is available to you depends on your current platform, reader estate and licensing.
This is a design decision, not an accident. Options include retaining a physical credential as backup, provisioning a temporary credential at reception, or reception-controlled access with identity verification. The wrong answer is an unlogged override that becomes the routine way in.
Over the life of the system, often. You remove card stock, printing, and the administrative cost of replacements. You add per-user licensing, which is typically annual and recurring. The comparison depends on your headcount, turnover rate and current replacement volume. We will model it with your numbers rather than a vendor's.