This article is aimed at property companies, building managers, and system integrators who are planning or evaluating access control in buildings where Welcome is used. It provides an overview of which access control systems Welcome integrates with, which card readers we recommend, which requirements must be met to support mobile access via Apple Wallet and Google Wallet, and which technical prerequisites must be in place in the building.

Traditional plastic cards and key fobs have long been the standard for access control in commercial buildings. Advances in mobile technology now open the door to a reality where physical cards are replaced by digital credentials in Apple Wallet and Google Wallet, and the mobile phone becomes the only "key" tenants need.

For property companies, this shift creates a more secure, user-friendly, and cost-effective building environment — free from plastic cards and with minimal administration. To succeed, the access control system and card readers must support NFC, BLE, and modern certification standards. The choices made today determine how easy it will be to adopt future features and

integrations.

Welcome has working integrations with more than 20 access control systems. The table below shows recommended minimum versions. The vendor must confirm that the installation meets the version requirement before integration is set up.

ARX er ledende sikkerhetssystem i Norden og det vanligste valget i norske yrkesbygg. Mangler systemet ditt i listen? Ta kontakt – vi vurderer nye integrasjoner fortløpende.

Both Apple and Google offer the ability to store digital access cards in their respective wallets (Apple Wallet and Google Wallet). For mobile access to work reliably, card readers must meet the following requirements:

NFC (Near Field Communication) is a wireless technology that transfers data at very short range, typically a few centimetres. For mobile access control, this means a smartphone can be held up to a card reader to authenticate the user. When card readers support NFC, they can read digital keys from Apple Wallet or Google Wallet and grant access in the same way as a physical card.

Why it matters: Without NFC, the mobile phone cannot communicate securely and effectively with the card reader. NFC is the core technology for contactless data transfer in mobile access

solutions.

ECP optimises communication between the mobile device and the card reader, making data exchange faster and more reliable. This includes rapid initialisation of contactless communication

and efficient handling of multiple security protocols.

Why it matters: Without ECP, users may experience delays, errors, or unstable connections. ECP readiness ensures the mobile key is read quickly and that the user experience is smooth.

MFi stands for "Made for iPhone/iPad" and is Apple's own certification programme for hardware designed to work closely with Apple devices. Card readers intended for use with Apple Wallet require an MFi licence, which guarantees the product meets Apple's technical and security requirements.

Although Google does not have an equivalent formal certification requirement, manufacturers must still ensure that readers are tested and approved for Google Wallet functionality, including the relevant NFC standards.

Why it matters: Without MFi certification, Apple Wallet functionality will not work reliably, and Apple devices may block or restrict access.

The access control industry is evolving rapidly, with new NFC protocols, stricter encryption standards, and increasing requirements around privacy (GDPR) and security. If the card reader is not built to handle future standards, the property company risks having to replace the entire system at a later stage.

Why it matters: Robust hardware and a good update cadence extend the lifespan of the solution and ensure it supports new features and security requirements as they emerge.

A common misconception is that it is enough for the card reader to support Apple Wallet and Google Wallet. That is not the case. For a user to open a door with their phone, two independent components must be compatible:

Both platforms must be supported. Norwegian commercial buildings have a mixed user base of iPhone and Android devices, and a solution that only works for one of them creates friction in daily use and extra work for building management.

The market is moving, and credential support often lags behind reader support. At present, we see the following:

The picture changes on an ongoing basis. We recommend that property companies confirm the current status with Welcome before ordering, especially if Wallet support on both platforms is a must-have for the project.

Key: ✅ In production · ⚠️ Partial / must be verified · ❌ Not yet available · App-based: Mobile access via the vendor's own app, not via Apple/Google Wallet.

Before purchasing or installing, check the make and model in Apple's MFi search. Only card readers listed there support Apple Wallet. Most Apple-certified readers are also compatible with

Google Wallet.

Certification applies to specific models and firmware versions, not the manufacturer in general. Always verify the specific model.

Reusing existing card readers can be a positive step for sustainability, but may also limit the advanced features and services available to tenants. If the readers do not meet NFC support, ECP readiness, or MFi compatibility requirements, the property company cannot offer full mobile access or the security benefits that modern solutions provide.

This creates a trade-off between sustainable reuse and achieving the functionality and user experience that today's technology demands. Experience shows it is worth upgrading readers at lease renewals or major refurbishments, rather than holding back digital services for the entire building.

For the integration between Welcome and the access control system to work reliably, the following must be in place:

Welcome integrates with the access control system server. The system must support modern APIs (REST/JSON, or alternatively SOAP) or other open protocols for communication. All API licences required for the integration must be included in the vendor's offer, including one-off licences, ongoing maintenance, and any transaction costs.

The access control system must be accessible via the internet or VPN for remote administration, support, and updates. Welcome uses Tailscale for secure remote access and requires this to be installed on the server.

The system must have an active internet connection to receive updates and communicate with Welcome and the card reader manufacturers' cloud services (HID, STid, etc.).

If you have questions about a specific combination, or whether your system or readers are on the list, get in touch with us.

Chat with us via the AI chat at the bottom right of the screen, or send an email to support@welcomeworkdays.com.