Best Practices for Managing Apple and Google Wallet Credentials in Multi-Building Security Systems
Overview
As mobile credentials become the new standard for physical access-via Apple Wallet, Google Wallet, and Bluetooth-many property owners and corporate portfolios are adopting HID or equivalent readers that support Wallet-based credentials.
However, the shift to Wallet credentials introduces a new and critical component: the MOB Key. Understanding what the MOB Key is, who should own it, and how to manage it is essential to maintaining long-term control, flexibility, and security across your properties.
Commercial Real Estate Owners • Property Managers • Multi-Family Operators • Corporate Security Directors • Multi-Site Portfolios
What Is a MOB Key (In Simple Terms)?
Think of the MOB Key as a digital “master key” that unlocks your ability to manage and program mobile credentials on HID or equivalent readers.
When readers are set up to work with Apple or Google Wallet credentials, each reader is “personalized” with a MOB Key. That key tells the reader which Wallet credentials it can trust. Without it, the reader won’t recognize the mobile credentials-and you, your integrator, or your security team can’t make configuration changes.
- If you don’t have the MOB Key: you can’t update reader settings, change credential formats, or troubleshoot mobile access.
- If a third party holds the MOB Key: you are dependent on them every time you want to make a change.
- If BluB0X holds the MOB Key on your behalf: your security provider (BluB0X) can manage, service, and support all your readers and credentials directly, without delay or third-party intervention.
Why It Matters
Every building’s readers must have a MOB Key installed before they can recognize mobile credentials. To update or replace the MOB Key-or to change the reader’s configuration-you must physically connect to each reader (using HID Reader Manager or BluB0X Reader Management, or equivalent) and reprogram it.
This means that whoever controls the MOB Key controls the ability to service your readers.
If your readers are tied to a third party’s MOB Key (for example, a credential broker such as SwiftConnect), then:
- BluB0X cannot reprogram your readers without that key.
- Any troubleshooting, reader replacement, or credential format change requires going back to that third party.
- You lose operational independence and flexibility.
For most property portfolios, this is an unacceptable dependency.
The Core Problem
-
In multi-tenant buildings, different tenants may use different card formats.
-
Increasingly, those tenants also want Apple or Google Wallet credentials for convenience.
-
To support this, the building must have readers loaded with the right MOB Key so the readers can recognize those Wallet credentials.
-
If every building-or every tenant-uses a different MOB Key, you end up with fragmentation:
-
More keys to manage.
-
More confusion for mobile users (who might need multiple Wallet passes).
-
More complexity when reprogramming or selling buildings.
BluB0X’s Recommended Best Practice
1. Use a Single MOB Key Across the Entire Portfolio
Using one MOB Key across all buildings offers clear operational and user benefits:
| Benefit | Explanation |
|---|---|
| Single Wallet Credential | Tenants and employees only need one Apple or Google Wallet pass to access all authorized buildings. |
| Simplified Management | BluB0X can program and service any reader across the portfolio without switching keysets. |
| Faster Onboarding | New buildings or readers can be added using the existing MOB Key-no need for new credential issuance. |
| Easier Support | If a reader needs replacement or a firmware update, BluB0X can do it directly without third-party coordination. |
| Portfolio Consistency | One MOB Key ensures standardized security behavior across all properties. |
2. Maintain BluB0X (or Owner) Custody of the MOB Key
The MOB Key should never be controlled exclusively by a third party (for example, a credential vendor). BluB0X recommends one of the following custodial structures:
- BluB0X Custody: BluB0X securely holds the MOB Key on behalf of the property owner and uses it for setup, maintenance, and support.
- Joint Escrow: The owner and BluB0X each hold an encrypted copy in secure escrow for redundancy.
- Third-Party Use by Permission Only: Credential vendors such as SwiftConnect may use the MOB Key to issue Wallet passes but do not control it.
This ensures:
- Technicians can always service the system.
- The property owner maintains legal and operational control.
- No service dependency or lock-in to outside vendors.
3. Document and Secure the MOB Key
Because the MOB Key effectively controls your entire mobile credential ecosystem, it must be handled like a critical encryption key:
- Store it in an encrypted BluB0X vault or equivalent secure escrow.
- Limit access to authorized BluB0X technical personnel and system administrators.
- Audit any access or usage of the key.
- Include the MOB Key reference ID (MOB####) in each building’s security documentation.
4. Plan for Building Sales or Divestitures
If a building is sold, you have two clean options:
- Transfer the MOB Key (with authorization from BluB0X and the owner) to the new owner.
- Load a new MOB Key into that building’s readers and reissue Wallet credentials only for that building.
Because the BluB0X model keeps you in control, either process is quick, secure, and fully auditable.
What Happens During Reader Setup or Update
Whenever a new reader is installed or an existing one needs an update:
- A BluB0X technician visits the reader (or connects via HID Reader Manager or BluB0X Reader Management, or equivalent).
- The MOB Key is securely loaded into the reader so it can recognize mobile credentials.
- Any credential format changes (card numbers, Wiegand, OSDP, etc.) are applied at that time.
This is why BluB0X-and not a third party-must have ongoing access to the MOB Key. Otherwise, even simple service calls would require outside authorization.
Tenants with Their Own MOB Key
In some multi-tenant buildings, tenants may choose to operate their own security system with their own MOB Key, separate from the base building. This introduces some additional considerations.
If the Tenant Uses a Different MOB Key (Different Access System)
-
The base building will have its own MOB Key and issue credentials for building-wide access (lobbies, elevators, amenities, etc.).
-
The tenant will have its own MOB Key for its private suite or space.
-
Each user will therefore need two separate Wallet credentials-one issued by the base building and one issued by the tenant.
-
Apple Wallet should automatically select the correct credential based on which reader is presented.
-
At the base building doors, the device presents the base-building credential.
-
At the tenant suite doors, it presents the tenant credential.
-
This setup works, but it’s more complex for users because two credentials must be managed.
If Both the Tenant and Base Building Use BluB0X
If both the base building and tenant use the BluB0X system, then a single credential can be used for both. In this case:
- BluB0X links both access systems under the same MOB Key.
- The tenant and base building share credential trust.
- Users are issued one Wallet credential that works everywhere they are authorized.
- Management and auditing are unified within BluSKY.
This is the cleanest, most efficient configuration for multi-tenant properties.
If the Tenant Uses a Different Access Control System
If the tenant’s system is not BluB0X, and they use their own MOB Key through another vendor:
- The tenant manages their own credentials independently.
- Users must carry two Wallet credentials (base building + tenant).
- Each credential is bound to its own MOB Key.
- The Apple Wallet can usually select automatically, but users will see both credentials in their Wallet.
While functional, this arrangement is less streamlined and can be confusing for end users.
Recommendation: Encourage tenants to adopt BluB0X for a unified experience and consistent credential management.
Apple and Google Wallet Experience
When using a single MOB Key across your portfolio-or when both tenant and base building use BluB0X:
- Users have one Wallet pass that works across all authorized areas.
- Apple Wallet (via Enhanced Contactless Polling) and Google Wallet automatically select the correct credential when tapping or presenting the phone to a reader.
- If multiple MOB Keys exist (e.g., tenant plus base building), users will have multiple Wallet passes, and the phone will determine which one to present based on the reader’s configuration.
Simplifying to one MOB Key (and one system) delivers a seamless, intuitive mobile-access experience for tenants, residents, and staff alike.
Summary of Recommendations
| Best Practice | Why It Matters |
|---|---|
| Use one MOB Key for the entire portfolio | Enables single Wallet credential, easy support, and consistent user experience. |
| Maintain BluB0X control or escrow of the MOB Key | Ensures continued service capability and independence from third parties. |
| Secure and document the key | Treats it as critical infrastructure; avoids future loss or dependency. |
| Plan for divestiture | Allows clean building transfer or key rotation. |
| Encourage tenants to use BluB0X | Allows single credential across tenant and base building; reduces confusion. |
In Plain Language
The MOB Key is the digital “secret handshake” between your mobile credential and your door readers. Whoever controls it controls your ability to manage your system.
By keeping BluB0X in control of the MOB Key and using one key across your portfolio-or by ensuring tenants also use BluB0X-you ensure your buildings stay secure, serviceable, and simple for everyone to use.