Swiftlane

Mobile Access Control Systems: 2027 Credentials, Costs & Guide

Updated:
Mobile access control for building entrances

Mobile access control lets residents, tenants, and staff unlock doors with a credential stored on their phone instead of a fob, card, or code. For most properties, the 2027 decision isn't whether to support phones. It's which credential mix to run: app-based Bluetooth, wallet-based NFC, encrypted fobs, PINs, or a hybrid of all four, and what each one costs to buy, issue, and support.

That decision is getting easier to make, and harder to postpone. In February 2026, the Connectivity Standards Alliance released Aliro 1.0, a shared credential standard for phones, wearables, and access readers backed by Apple, Google, Samsung, and major lock and reader makers. Wallet-based keys are already live in multifamily and commercial buildings. And every reader you replace in the next budget cycle will either support mobile credentials or lock you out of them for the life of that hardware.

This guide is built for property managers, owners, IT and security leads, and asset managers making that call. It compares the five credential types side by side, explains how mobile credentials actually work (including offline behavior and what happens when a phone dies), breaks down 2027 per-reader and per-credential costs, and ends with a buyer's checklist you can use in vendor evaluations.

If you're still deciding between keyless entry categories in general, start with our keyless entry systems guide. This page assumes mobile is on the table and helps you decide how to deploy it.

How We Researched This

This guide draws on Swiftlane's experience deploying access control across 3,000+ multifamily and commercial buildings, plus conversations with property managers, building operators, and security integrators about issuing, revoking, and supporting credentials at scale.

Technical claims are sourced to manufacturer documentation (NXP, HID, Apple, Google) and the Connectivity Standards Alliance. Cost ranges come from integrator and reseller pricing published in 2025 and 2026, and from resident fee schedules posted by a publicly traded apartment operator. Installation labor varies widely by market, so treat every range here as a starting point for quotes, not a final budget.

Key Takeaways

  • The decision is the credential mix, not just "mobile or not." Most properties run mobile as the primary credential, with an encrypted fob or PIN as the fallback.
  • Mobile credentials remove per-credential hardware costs, not all costs. You still pay for mobile-capable readers, and many platforms charge a per-user or per-door software fee.
  • Modern encrypted fobs aren’t the weak link; legacy 125 kHz prox is. Mobile's biggest advantage over a good smart card is speed of issuing and revoking, not encryption alone.
  • Mobile access keeps working offline when the system is designed for it. Credentials stored at the door controller let phones, fobs, and PINs open doors during an internet outage.
  • Plan for every resident, not just the tech-comfortable ones. Wallet tap-to-unlock, smartwatch support, and a non-phone fallback make mobile workable for older residents and anyone without a compatible phone.

Table of Contents

Related Posts

The 5 Access Credential Types Compared

Five credential types cover nearly every property: two mobile, one physical, one code-based, and a hybrid that combines them. Here's how they compare on the factors that drive the decision.

Credential type How it works Security model 2027 cost signal Best property fit Watch out for
Mobile BLE credential Phone app talks to the reader over Bluetooth, by tap-in-app or hands-free Encrypted, bound to the enrolled device No per-credential hardware; mobile-capable reader about $250 to $700; software or license fees vary Multifamily, offices, mixed-use Phone battery and Bluetooth permissions; needs a fob or PIN fallback
Mobile NFC (Apple Wallet / Google Wallet) Credential stored in the phone's wallet; user taps the reader Key held in the phone's Secure Element; no app opening at the door No per-credential hardware; NFC wallet-capable reader about $250 to $700; software or license fees vary High-turnover rentals, resident convenience Provisioning still runs through the provider's app; device and OS minimums; reader must support the wallet protocol
Encrypted fob / card 13.56 MHz smart credential (MIFARE DESFire EV3, HID Seos or iCLASS SE) Mutual authentication; AES-128 on DESFire EV3 About $7 to $15 per credential; reader about $200 to $600 Mixed demographics, condos, backup for mobile Ongoing issuing and replacement; resident fees of $35 to $115 per lost fob at some communities
PIN / keypad User enters a code at the door None; the code isn't tied to a person Keypad hardware ranges widely, from about $180 to $1,000 Gates, amenities, vendor backup Codes get shared; weak audit trail
Hybrid (mobile + fob + PIN) One platform, several credential types per door Only as strong as the weakest credential enabled on each door Highest upfront (multi-technology readers) Portfolios, new developments Requires a unified platform so every credential is managed in one place

Sources: reader ranges from AIS and Treasure Valley Solutions; credential pricing from CDW and Avon Security Products; lost-fob fees from UDR community fee pages (New York, San Diego); DESFire EV3 cryptography from NXP; Secure Element storage from Salto's Apple Wallet key documentation. Full cost breakdown in the 2027 costs section below.

Mobile BLE Credentials

Bluetooth Low Energy credentials live inside an access control app. The phone and reader exchange an encrypted credential over a short-range Bluetooth link, either when the user taps an unlock button or automatically as they approach. Because Bluetooth doesn't require the phone to touch the reader, BLE supports hands-free entry and readers mounted behind glass or inside a door frame.

Mobile NFC and Wallet Credentials

Wallet credentials sit in Apple Wallet or Google Wallet and work like a contactless payment card: hold the phone or watch near the reader and the door opens. On iPhone, the key is stored on the device's Secure Element, and Express Mode lets it work without unlocking the phone. Residents still add the key through the provider's app the first time, so "no app required" applies at the door, not during setup.

Encrypted Fobs and Cards

Modern smart fobs are a different technology from the 125 kHz proximity fobs many buildings still use. A MIFARE DESFire EV3 credential, for example, uses hardware AES-128 encryption and application-level authentication. That makes it far harder to clone than legacy prox. Its weakness is operational: every move-in, lost fob, and move-out still involves a physical object. For a deeper look at fob systems, see our key fob systems guide.

PINs and Keypads

PINs are cheap and need nothing in the user's pocket, which makes them useful for gates, amenity doors, and one-time vendor access. But a code identifies whoever knows it, not a specific person. Shared codes break audit trails, so PINs work best as a fallback or for time-limited access.

Hybrid Deployments

A hybrid system lets each door accept more than one credential type. It's the most practical setup for most properties, because it supports residents without smartphones and gives everyone a backup. Just remember that a door is only as secure as the weakest credential it accepts. If a door takes both mobile credentials and legacy prox fobs, its real security level is prox.

Mobile Credentials in Depth

A mobile credential is a digital access credential issued to a specific phone or watch and checked by the reader the same way a card would be. The difference is in how it's delivered, stored, and revoked.

BLE vs. NFC vs. Wallet Credentials

Factor App-based BLE App-based NFC Wallet (Apple / Google)
How the user unlocks Tap in app, or hands-free on approach Hold phone to reader Hold phone or watch to reader
Range Short range, but no contact needed A few centimeters A few centimeters
App open at the door? Usually yes, or running in the background Usually yes No
Works when the phone is dead No No Apple Wallet keys: yes, for up to 5 hours with Express Mode on
Reader mounting Can be mounted inside or behind a surface on some systems Must be reachable for a tap Must be reachable for a tap
Device requirements Bluetooth and app permissions on NFC-capable phone iPhone or Apple Watch on supported models; Android 9.0+ with NFC for Google Wallet

Sources: Power Reserve and Express Mode from Swiftlane's Apple Wallet page and Salto's key documentation; Google Wallet requirements from Google's corporate badge documentation; inside mounting from Entegrity.

Most modern platforms support more than one method, and that's what you want. BLE handles hands-free and older phones; wallet credentials give the fastest tap and keep working on a low battery. Aliro 1.0 also standardizes all three transports, NFC tap plus Bluetooth LE and Ultra Wideband for longer-range entry, so expect more readers to support both styles over the next few years.

Device Binding and Tokenization

A mobile credential is issued to one enrolled device, not to an account that can be logged into anywhere. When a resident gets a new phone, the old credential is retired and a new one is issued. That's what makes mobile credentials hard to share: there's nothing to hand over.

Wallet credentials add another layer. On iPhone, the key is stored in a dedicated security chip, and the issuer's documentation notes that Apple doesn't see which spaces a user accesses or when. The reader receives a credential, not the resident's personal data.

App-based credentials vary more by vendor. Swiftlane's app-based mobile access, for example, supports Bluetooth unlock, with credentials securely stored on the user's device, in the cloud, or both. Whatever system you evaluate, ask exactly what the app stores on the phone and what it sends to the cloud.

Keycards vs. Mobile Credentials

The real gap isn't mobile versus cards. It's modern credentials versus legacy ones.

Factor Legacy 125 kHz prox card/fob Encrypted smart card/fob Mobile credential
Clone resistance Low High (mutual authentication, AES) High (device-bound, encrypted)
Issuing In person, physical handoff In person, physical handoff Remote, by invite
Revoking Deactivate in system; fob may still be in someone's pocket Same Deactivate in system; credential removed from device
Per-credential hardware cost Low About $7 to $15 None
Works without a phone Yes Yes No

If your building still runs 125 kHz prox, moving to either encrypted fobs or mobile is a meaningful security upgrade. If you already run encrypted smart cards, mobile's advantage is mostly operational: no inventory, no handoffs, and revocation that doesn't depend on getting a fob back. For a fuller side-by-side on cost and convenience, see key fob vs. mobile access.

Offline Behavior: What Works When the Internet Goes Down

Mobile credentials don't need the phone or the building to be online at the moment of entry. BLE and NFC communicate directly between phone and reader, and the access decision should happen locally.

In Swiftlane's architecture, credentials and access decisions are stored at the door controller. During an internet outage, PINs, fobs, mobile credentials, and face recognition generally keep working. What may be limited is cloud management: issuing or revoking credentials, syncing event logs, and some remote unlock and intercom features. Cellular fallback and battery backup are available as deployment options. Compatible Swiftlane readers also cache authorized credentials on-device, so residents can unlock over Bluetooth without an internet connection.

When you evaluate any system, ask the vendor two questions. Where’s the access decision made: in the cloud or at the door? And how long can a door run offline before it stops accepting recent permission changes?

Phone-As-Key for Older Residents

Yes, older residents can use their phone as a key, and most already carry one that works. Pew Research Center found that 79% of U.S. adults 65 and older own a smartphone, while 14% own a cellphone that isn't a smartphone.

The practical gap is setup and habit, not ownership. A few choices make a big difference:

  • Offer wallet tap-to-unlock. There's no app to find at the door, and an Apple Watch works too.
  • Help with setup in person. A short, staff-assisted enrollment at move-in can head off later support calls.
  • Keep a non-phone option. An encrypted fob or PIN for residents who don't have or don't want a compatible phone.
  • Consider face recognition as an alternative where it's offered and residents opt in. It needs no phone at all, though it brings its own consent and privacy rules (covered briefly in the security section below).

Mobile Access Control Costs in 2027

Phone-as-key pricing has no per-key hardware cost, but it isn't free. You pay for readers that support mobile credentials, installation at each door, and usually a recurring software or credential license. Here's what each line item costs based on 2025–2026 published pricing.

Cost line item Typical range (2025–2026 observed) Source
Mobile-capable reader (BLE/NFC), hardware only $250 to $700 per reader AIS
Encrypted smart card / mobile-ready reader, hardware only $200 to $500 per reader Treasure Valley Solutions
Example: HID Signo 40 mobile-ready reader $437.83 list price ID Security Online
Fully installed door (reader, lock, controller, wiring, setup) $1,500 to $3,500 per door Safe and Sound Security; Treasure Valley Solutions
Cloud platform software $3 to $15 per door per month on the low end; up to $30 to $200 per door per month for full-featured platforms Treasure Valley Solutions; Safe and Sound Security
Mobile credential license (where charged per user) Example: HID Mobile Access Enterprise, $4.99 per user per year MSRP, 20-license minimum Tape and Media (HID reseller)
Encrypted fob or card (for fallback) About $7 to $15 each CDW; Avon Security Products

Two caveats matter more than any single number. First, installation labor dominates the per-door total, and it varies by region, door type, and whether existing wiring and locks can be reused. The installed ranges above come from integrators in specific markets, so get local quotes. Second, software pricing models differ: some platforms charge per door, some per user, some per credential, and some bundle mobile credentials into the platform fee. Compare total cost over three to five years, not the monthly line.

What a Lost Fob Really Costs

Mobile access control compared to key fob system

Fob costs don't stop at purchase. Residents at UDR communities, for example, are charged anywhere from $35 to $115 per replacement key or fob. Those fees are the resident's cost, not yours, but the staff time behind them is yours: finding inventory, programming the new fob, deactivating the old one, and handling the handoff.

To estimate your own annual physical-credential cost, use your actual numbers:

Annual fob cost = (fobs issued at move-in + fobs replaced) × cost per fob + staff hours spent on fob tasks × loaded hourly rate

Mobile credentials remove the first half of that formula and most of the second. What remains is the software fee, plus a smaller fallback fob inventory for residents who need one.

Retrofit vs. New Installation

If your doors already have electrified locks and network-connected controllers, adding mobile is mostly a reader swap and a software change. If your current readers are 125 kHz prox only, they can't read mobile credentials, so readers are the main capital line. Older Wiegand-wired readers can often stay in place for a transition period, but plan to move to OSDP readers as part of the upgrade (see the architecture section below).

Swiftlane Pricing

Swiftlane doesn't publish standard pricing; every quote is built for the property. Request a demo for a quote built around your building.

Mobile Access Control Architecture

A mobile access control system has five layers: the credential, the reader, the door controller, the cloud platform, and the integrations around it. Knowing which layer does what is the fastest way to judge reliability and vendor claims.

  1. Credential (phone or watch). Holds the encrypted mobile credential in an app, or in Apple Wallet or Google Wallet.
  2. Reader. Mounted at the door, gate, or elevator. Talks to the phone over BLE or NFC, and often reads fobs, cards, or PINs too. Our mobile access control readers guide covers reader hardware in detail.
  3. Door controller. Receives the credential from the reader, checks it against locally stored permissions, and releases the lock. This is where the access decision should happen, so the door keeps working without internet.
  4. Cloud management platform. Where staff issue and revoke credentials, set schedules and door groups, and review audit logs. Changes made here sync down to each controller.
  5. Integrations. Property management software (PMS), video intercom, visitor management, and elevator controls connect to the platform so access follows the resident record automatically.

What Happens During an Unlock

  1. The resident taps their phone or approaches the door.
  2. The reader and phone exchange an encrypted credential over NFC or BLE.
  3. The reader passes the credential to the door controller.
  4. The controller checks it against stored permissions: who this is, which doors they can open, and when.
  5. If it matches, the lock releases and the event is logged locally.
  6. The event syncs to the cloud platform for reporting, immediately or once connectivity returns.

Reader-To-Controller Wiring: Wiegand vs. OSDP

Many existing readers connect to controllers over Wiegand, an older one-way protocol with no encryption on the wire. Upgrading the phone-to-reader link doesn't secure the reader-to-controller link. Security integrators recommend migrating to OSDP readers so mobile credential deployments gain security end to end, not just at the reader.

PMS Integration: Where the Time Savings Come From

One of the biggest operational wins comes from connecting access control to your PMS. When a lease starts, the resident's credential is issued automatically; when it ends, access is removed without anyone remembering to do it. If you're evaluating integrations, our property management software integration guide covers what to ask.

Mobile Access Control by Property Type

The same credential types apply everywhere, but the right mix depends on who's coming through the door and how often access changes.

Property type Primary credential Fallback What matters most
Multifamily apartments Mobile (wallet + app) Encrypted fob or PIN Move-in/move-out speed, guest and delivery access, PMS sync
Commercial and enterprise offices Mobile (wallet badge + app) Encrypted card Role-based access, schedules, multi-site management, audit reports
Condos and HOAs Mobile + encrypted fob PIN for gates and amenities Owner preferences, board approval, residents without smartphones
Mixed-use Mobile, with separate permission groups Encrypted fob or card Keeping residential, retail, and office access separate on one platform
Student housing Mobile Encrypted card or fob Semester turnover, frequent credential reissues

Multifamily Apartments

Multifamily is where mobile pays off fastest, because access changes constantly. New residents can get credentials before move-in day, departing residents lose access the day the lease ends, and nobody waits at the office for a fob. Mobile credentials typically cover the front entry, garage, elevators, amenities, and package rooms from one phone. Pair them with a video intercom so guests and couriers can be let in remotely, and time-limited access so vendors don't need a key.

Commercial and Enterprise Offices

Offices care most about role-based permissions and reporting. Staff, tenants, cleaners, and visitors each need different doors at different hours, and security teams need audit logs they can export. Wallet badges are now widely available: Google Wallet corporate badges work on Android 9.0 and later with NFC, and Apple Wallet supports employee badges on iPhone and Apple Watch. For multi-site portfolios, the ability to manage every building from one dashboard matters as much as the credential itself.

Condos and HOAs

Condo associations usually need the most flexible setup. Owners vary widely in age and comfort with technology, and some will want to keep a physical fob. A hybrid deployment, mobile plus encrypted fobs with PINs for pool gates or amenities, lets the board modernize without forcing anyone onto a phone. Boards should also ask how credentials transfer when a unit sells and how renters are handled.

Mixed-Use Buildings

Mixed-use properties need one platform that can keep separate groups apart: residents shouldn't reach office floors, and retail staff shouldn't reach residential amenities. Look for door groups, schedules, and separate admin roles per tenant or use, so each manager controls their own users without seeing everyone else's.

Student Housing

Student housing combines semester turnover with frequent credential reissues, which makes it a natural fit for mobile credentials. See our access control for student housing guide for semester-cycle planning.

Mobile-First, Not Mobile-Only

The most reliable deployments make mobile the default credential and keep at least one non-phone option on every door. Going mobile-only saves a little on fobs and costs a lot in lockouts, support calls, and residents who feel left out.

When Fobs and Cards Still Make Sense

  • Residents without a compatible phone, or who don't want their phone to be their key.
  • Staff and vendors who share devices, work in gloves, or can't carry a personal phone on the job.
  • Backup during outages or phone failures, such as a dead battery on a phone without wallet Power Reserve.
  • Transition periods, while residents move from the old system to the new one.

Keep those fallbacks encrypted. A 13.56 MHz smart fob is a reasonable backup; a legacy prox fob left active on the same door undercuts the security of everything else.

Roll Out in Phases

Start with one building, one entrance, or one user group. A contained pilot surfaces problems like reader placement, Bluetooth range, and onboarding confusion before they reach every resident. Once issuing, revocation, and support workflows are stable, expand building by building.

Run Hybrid Access During the Transition

Keep existing fobs active while mobile credentials roll out, then retire them on a set date once most residents have enrolled. Announce the date early, repeat it often, and give holdouts an easy path to either set up mobile or request an encrypted replacement fob.

Make Enrollment the Easy Part

Adoption depends on how fast someone gets to their first successful unlock. Send invites before move-in, keep setup to a few steps, and give residents a one-page guide covering app setup, adding the key to Apple Wallet or Google Wallet, and what to do if their phone is lost. Offer in-person setup help for anyone who wants it.

Train Staff Before Residents Rely on It

Leasing staff, property managers, and maintenance teams should all know how to issue and revoke credentials, set temporary vendor access, read the audit log, and walk a resident through common fixes. If staff can't troubleshoot a credential in a couple of minutes, residents will end up back at the front desk asking for a fob.

Plan for Edge Cases Up Front

Decide in advance how you'll handle a lost phone, a new phone, a dead battery, a resident with no smartphone, a caregiver who needs regular access, and a short-term guest. Each should map to a specific credential, such as a temporary mobile credential, a time-limited PIN, or an individually assigned fob. Avoid shared codes or shared fobs as a workaround; they erase the audit trail that makes mobile access worth having.

Security, Privacy, and Compliance

Mobile credentials close the biggest weakness of legacy systems, cloneable prox fobs, and they make revocation nearly instant. They also introduce new questions about lost devices, relay attacks, and personal data. Here's how to evaluate each.

Lost or Stolen Phones

A lost phone is less risky than a lost fob in two ways. The credential can be revoked from the admin dashboard the moment the loss is reported; Swiftlane, for example, removes building access as soon as it's revoked. And the phone itself is protected by a passcode or biometrics. For Apple Wallet keys, users can also suspend the key by putting the device in Lost Mode through Find My.

One caveat: wallet keys in Express Mode open doors without unlocking the phone, which is what makes them fast. Treat a lost phone like a lost fob and revoke it right away.

Relay Attacks

A relay attack uses two devices to extend the range between a legitimate credential and a reader, tricking the reader into thinking the credential is present. Security researchers note that BLE and NFC mobile credentials solve prox-card cloning but introduce relay risk that systems need to defend against. Defenses include timing checks, short validity windows, and newer standards: DESFire EV3 includes a proximity check against relay attacks, and Aliro 1.0 uses asymmetric cryptography between devices and readers. Ask vendors what relay protections their readers use.

Encryption From Phone to Lock

Check every link in the chain. The phone-to-reader exchange should be encrypted, the reader-to-controller connection should use OSDP rather than unencrypted Wiegand, and the controller-to-cloud connection should be encrypted in transit. A system is only as strong as its weakest link.

Audit Trails

Every unlock, denied attempt, and permission change should be logged with the person, door, and time, and exportable for investigations or insurance claims. Individually assigned credentials are what make those logs meaningful; shared PINs and pooled fobs undermine them.

Privacy and Data Handling

Mobile access systems handle resident names, unit numbers, phone identifiers, and entry logs. Ask each vendor:

  • What data the app collects, including whether it uses location or Bluetooth in the background.
  • How long entry logs are retained, and whether you can set the retention period.
  • Who can see the logs, and whether access is limited by role.
  • How resident data is deleted at move-out.

Wallet credentials have a privacy advantage here: on iPhone, the key is kept in the device's security chip, and Apple doesn't see which spaces a user enters or when.

Face Recognition and Biometric Laws

Some mobile access platforms, including Swiftlane, also offer face recognition as a phone-free credential. Biometric credentials fall under separate state laws, such as Illinois BIPA, Texas, and Washington, with their own consent and retention requirements. If you're considering face recognition alongside mobile, see our face recognition access control guide for compliance details.

Mobile Access Control Buyer's Checklist

Use this list in vendor demos and RFPs. If a system can't check the items that matter most for your property, expect workarounds later.

Credentials

  • Supports Apple Wallet and Google Wallet, plus app-based BLE for phones without wallet support
  • Supports encrypted 13.56 MHz fobs or cards and PINs as fallbacks on the same reader
  • Lets you disable legacy 125 kHz prox on doors where it's no longer needed
  • Credentials are bound to one device and reissued automatically when a phone is replaced
  • Has a published plan for Aliro support

Reliability and Offline Behavior

  • Access decisions are made at the door controller, not in the cloud
  • Doors keep accepting credentials during an internet outage
  • Cellular fallback and battery backup are available
  • Wallet keys keep working on a low or dead battery where the phone supports it

Management and Integrations

  • Cloud dashboard covers every building and door in your portfolio
  • Role-based permissions, door groups, and schedules
  • Instant revocation and automated move-out offboarding
  • Integrates with your PMS
  • Integrates with video intercom and visitor management, if you want a single front-door workflow
  • Bulk invites, templates, and self-serve onboarding for residents

Security and Compliance

  • Encrypted phone-to-reader communication with relay protections
  • OSDP reader-to-controller wiring, or a clear upgrade path from Wiegand
  • Hardware listed to UL 294, the safety standard for access control system units
  • Exportable audit logs and alerts for failed attempts
  • Configurable data retention and role-limited access to logs
  • Consent workflows, if biometric credentials are offered

Cost

  • Clear pricing model (per door, per user, or per credential) and total cost over three to five years
  • Reuses existing locks and wiring where possible
  • No separate fees for wallet credentials, or those fees are disclosed up front

Where Swiftlane Fits In

Swiftlane is a mobile-first access control platform used in 3,000+ multifamily and commercial buildings. It combines mobile credentials, face recognition, video intercom, and visitor access in one system, so every credential type is managed from one dashboard.

  • Wallet and app credentials. Residents can add a Resident Key to Apple Wallet from the Swiftlane app and unlock with a tap from iPhone or Apple Watch. Swiftlane also supports Google Wallet unlock through an NFC-based digital access pass on compatible readers, including SwiftReader X and Z10/Z20 hardware. Both wallet options are separate from Swiftlane's app-based Bluetooth unlock.
  • Works on a low battery. With Power Reserve, Apple Wallet keys work for up to five hours after the iPhone needs a charge.
  • Phone-free backups. Face recognition works without a phone, if enrolled, alongside PINs and fobs.
  • Built to work offline. Credentials and access decisions are stored at the door controller, so PINs, fobs, mobile credentials, and face recognition generally keep working during internet outages. Cellular fallback and battery backup are deployment options.
  • Instant revocation. Revoking access in Swiftlane removes the resident's building access, including Apple Wallet keys.
Real-World Example: 2B Living

Senior Property Manager Nelly Litovskaya of 2B Living replaced legacy intercom systems across 26 San Francisco properties with Swiftlane. Before the switch, her team regularly traveled to buildings to let in vendors, maintenance crews, and emergency personnel. With mobile access and remote management, access can now be granted from anywhere, and tenant records update automatically through PMS integrations. According to Litovskaya, the change reduced site visits, lowered operating costs, and gave residents more control over guest access.

See how Swiftlane mobile access control works, or request a demo for a quote built around your property.

FAQs

What is a mobile credential in access control?

A mobile credential is a digital access credential stored on a phone or smartwatch, either in an access control app or in Apple Wallet or Google Wallet. The phone presents it to the reader over Bluetooth or NFC, and the system checks it the same way it would check a card or fob.

Are mobile credentials more secure than keycards?

They're more secure than legacy 125 kHz prox cards, which are easy to clone. Compared with modern encrypted smart cards like DESFire EV3, the encryption is comparable; mobile's advantage is that credentials are bound to one device, can't be handed off, and can be revoked remotely in seconds.

How much does phone-as-key access cost?

There's no per-key hardware cost, but you'll pay for mobile-capable readers (about $250 to $700 each, hardware only), installation, and usually a software or credential license. Fully installed doors typically run $1,500 to $3,500 each, depending on market and existing hardware.

Does mobile access control work without internet?

It should. BLE and NFC communicate directly between phone and reader, and well-designed systems store credentials at the door controller so doors keep working during an outage. Remote unlock, credential changes, and log syncing may wait until the connection returns.

What happens if a resident's phone battery dies?

On supported iPhones, Apple Wallet keys with Express Mode keep working for up to five hours after the phone needs a charge. App-based credentials don't work on a dead phone, so residents need a fallback such as a PIN, an encrypted fob, or face recognition where available.

What happens if a phone is lost or stolen?

Revoke the credential from the admin dashboard as soon as the loss is reported. For Apple Wallet keys, the resident can also suspend the key by putting the device in Lost Mode through Find My.

Do residents need the app to use Apple Wallet or Google Wallet keys?

Not at the door. Residents typically add the key to their wallet through the provider's app the first time; after that, they just tap their phone or watch to unlock.

Which phones support mobile access?

Most current iPhones and Android phones support app-based BLE credentials. Wallet credentials need supported devices: iPhone and Apple Watch for Apple Wallet, and Android 9.0 or later with NFC for Google Wallet. The readers must also support the wallet protocol.

Can older residents use mobile access?

Yes. Most adults 65 and older own a smartphone, and wallet tap-to-unlock works like paying with a phone. Offer in-person setup help and keep a fob or PIN available for residents who prefer it.

Can mobile access work with my existing fobs and readers?

Often, yes, during a transition. Many readers accept both mobile credentials and 13.56 MHz fobs, so residents can switch gradually. Legacy 125 kHz-only readers can't read mobile credentials and will need to be replaced.

Subscribe to the Multifamily Newsletter

Get the latest news and updates in multifamily and commercial real estate.

Loading the secure form…

Read more