Passpoint lets a guest’s phone join your hotel Wi-Fi automatically and securely, with no password-of-the-day and no login page on return visits. It works only when the wireless network, the authentication back end and the guest’s first-time onboarding are designed together. That makes it an infrastructure project, not a setting you switch on. This guide explains how Passpoint works, what a hotel network must have in place, which privacy points to plan for and how to prepare a property or a group.
TL;DR
- Passpoint (also called Hotspot 2.0) is a Wi-Fi Alliance programme. A device holding a stored profile finds a matching network and authenticates through 802.1X without a captive portal.
- Guests onboard once, then reconnect automatically. A single profile can cover every property in a hotel group.
- Your access points, controllers and authentication servers must support enterprise-grade security. Coverage and cabling quality decide whether the experience feels seamless.
- Passpoint can expose identifiers such as the Wi-Fi MAC address, so privacy notices and clean traffic separation belong in the design from day one.
- A wireless survey and a network audit before deployment show what must change, which prevents expensive rework.
Table of Contents
- What Passpoint is, in plain terms
- How a Passpoint connection works, step by step
- Passpoint compared with a login page and with Wi-Fi Calling
- Why it matters to a hotel operator
- What your network needs before Passpoint
- Separating guest traffic from staff, payment and operational systems
- Privacy and data: plan it before launch
- A readiness checklist for a hotel or group
- Our view
- Preparing your hotel with Re-Solution
- FAQ
- Sources
What Passpoint is, in plain terms
Passpoint is a certification programme run by the Wi-Fi Alliance, the industry body behind the Wi-Fi brand. It is also known as Hotspot 2.0. According to the Wi-Fi Alliance’s technology overview, a provisioned device can discover compatible networks, match the details a network advertises against the credentials it holds, and authenticate automatically using 802.1X and EAP. Devices and the provider’s authentication (AAA) server also authenticate each other, so the guest’s phone knows it is talking to the real hotel network.
Two terms are worth defining, because they appear in every vendor document:
- 802.1X is the standard that checks who or what is connecting before a device is allowed on the network. It is the same mechanism many organisations use for staff Wi-Fi.
- EAP is the family of methods used inside 802.1X to prove identity, for example with a certificate or a username and secret held in a profile.
The result for the guest is simple. The first stay involves one onboarding step. Every later visit connects without any action.
How a Passpoint connection works, step by step
The sequence matters because each stage maps to something your network team has to configure.
- Advertising. Your access points announce Passpoint capability in their beacon and probe-response frames, which are the small broadcast messages every access point sends. The Wi-Fi Alliance describes this as the start of discovery in its technology overview.
- Querying. Before joining, the device asks the access point for network details using ANQP, a query protocol that runs ahead of association. The answers include the network realm and roaming-consortium identifiers, as the deployment guidelines set out.
- Matching. The device compares those details with the credentials and preferences stored in its profile. If nothing matches, it stays away and shows no login prompt.
- Authenticating. The device and your authentication server complete 802.1X with EAP. Traffic over the air is then encrypted.
- Onboarding, once. A guest with no profile signs up and has the device provisioned. The overview notes that first-time users without credentials go through this step before automatic repeat connections begin.
The onboarding step is where hotels make the design choices that guests notice. It can be tied to the booking, to a check-in message, to the hotel’s app or to a brief sign-up page. Whichever route you choose, the profile it installs must be tied to a stay, so it stops working when the stay ends.
Passpoint compared with a login page and with Wi-Fi Calling
Three things are often confused.
| Captive portal login | Passpoint | Wi-Fi Calling | |
|---|---|---|---|
| What it is | A web page the guest completes to gain access | A stored profile that authenticates through 802.1X/EAP | A phone feature that carries calls and texts over Wi-Fi |
| Guest effort on return visits | Often repeated | None once provisioned | Not applicable |
| Proves the network is genuine | Not by itself | Yes, through mutual authentication | No |
| Role in the hotel | Onboarding and terms acceptance | Automatic secure connection | A service that benefits from a good connection |
The Wi-Fi Alliance overview draws the same line: a login page is a web-based onboarding step, while Passpoint relies on a stored profile. Wi-Fi Calling is a separate phone feature. Passpoint can help a handset reach the Wi-Fi network, but it does not provide calling.
This does not make the captive portal obsolete. Many hotels keep a portal for first-time onboarding, for guests whose devices do not support Passpoint, and for terms and conditions. If you are planning that layer, our guide to captive portal deployment covers it step by step.
Why it matters to a hotel operator
The guest benefit is the one people notice first. They avoid selecting a network and typing credentials again and again, and a provisioned device can reconnect automatically at participating hotspots, including other properties in a chain that share a profile. The Wi-Fi Alliance describes that experience as carrying enterprise-level security.
Trade press reports the same group-wide effect. Hotel Management reported in 2022 that a guest profile can connect automatically across participating properties in a brand, and that Passpoint connections encrypt traffic over the wireless infrastructure. It also noted that roaming at third-party venues is possible, subject to participation and configuration.
For the operator, the practical gains are:
- Fewer Wi-Fi complaints at the front desk. A guest who is already connected when they reach the room has no password to ask for.
- A consistent standard across sites. One authentication design applied at every property is easier to support than a different portal and password routine in each building.
- Stronger security than a shared key. Each device authenticates individually rather than sharing a pre-shared password that circulates for months.
- Better data about use of the property. Because devices are identified, the network can show where connectivity is used, provided your privacy design allows it.
Hotels with several sites gain most, because the profile is the same wherever the guest stays. Our guide to SD-WAN for hospitality explains how the wide-area links behind such a group are usually structured.
What your network needs before Passpoint
Passpoint is a feature of the whole wireless service. Four areas decide whether a hotel is ready.
Access points and controllers
The Wi-Fi Alliance states that Passpoint requires enterprise authentication rather than personal-key or legacy WEP and TKIP security. Your access points and wireless controllers, or your cloud-managed platform, must support the Passpoint capability and enterprise security modes. Older estates often do not. Establish this from an inventory, not from the age of the equipment alone.
Authentication back end
The network needs an authentication server that handles 802.1X with EAP, plus the certificate or profile arrangements that go with it. Decide who issues profiles, how they expire at check-out and how they are revoked if a device is lost. Our 802.1X deployment plan sets out a phased way to introduce this on UK networks, and it applies equally to the staff side of a hotel.
Radio coverage and capacity
Automatic connection only feels seamless if the signal is good in every room and corridor. A guest whose phone joins a weak access point behind a heavy wall will blame Passpoint, not the cabling. Hotel buildings are hard for radio: thick walls, lifts, fire doors and long corridors. A wireless survey measures coverage and interference before you commit, and our piece on why to invest in a wireless site survey explains what it reveals. For new builds and refurbishments, predictive surveys model coverage from plans before anything is installed.
If you are planning for Wi-Fi 7 at the same time, allow for the extra access points that higher-frequency bands can require, as our Wi-Fi 7 readiness guide describes.

Cabling and switching
Every access point needs a data cable and enough power over Ethernet. Finding out mid-project that a floor needs recabling is the most common source of delay and cost. Our hotel Wi-Fi design guide covers how to avoid cabling rework and data risks in UK hotels.
Separating guest traffic from staff, payment and operational systems
Passpoint secures the guest’s connection to the air. It does not decide what the guest can reach once they are on. That is the job of segmentation, and a hotel carries several kinds of traffic that must stay apart:
- guest devices;
- staff devices and back-office systems;
- card payment terminals and the property management system;
- room technology such as smart TVs, door locks, thermostats and other IoT devices;
- building systems and CCTV.
The usual approach is a separate virtual network (VLAN) for each group, with firewall rules between them that allow only what each group needs. Guest devices should be isolated from one another as well as from internal systems. Segmentation also narrows the part of your estate that falls under card-payment security standards, which is a practical reason to design it carefully from the start.
A network audit is the quickest way to learn where your current separation stands. Our network audit checklist shows how findings should be evidenced, and our network access controller guide explains how policy-based access control decides which devices go where.
Privacy and data: plan it before launch
Because Passpoint identifies devices, a hotel must know what is visible and to whom. The Wi-Fi Alliance’s deployment guidelines list information that can be exposed in a Passpoint deployment: the Wi-Fi MAC address, ANQP requests, identity, account or billing data, IMSI (the identifier on a mobile SIM), certificate contents, location and traffic analytics. They also say that what is exposed over the air depends on the authentication method. A MAC address is visible during association, and identity-related material can appear during EAP authentication.
The same guidelines recommend notifying users before personally identifiable information is communicated. In practice, a hotel should:
- choose an EAP method with its authentication design in mind, so that guest identity is not exposed more than necessary;
- state in the onboarding step what is collected and why;
- decide how long profile and connection records are kept, and who in the business can see them;
- align the whole arrangement with its UK data protection obligations, with its data protection lead involved from the design stage.
This is also a good moment to review general wireless hygiene. Our Wi-Fi security guide and network security step-by-step guide cover the wider controls around a guest network.
A readiness checklist for a hotel or group
Use this before you speak to any supplier.
- Inventory the wireless estate. List every access point and controller model, firmware version and licence. Mark which support Passpoint and enterprise security.
- Survey the building. Measure real coverage and interference in rooms, corridors, lifts, function spaces and outdoor areas.
- Check cabling and power. Confirm that every planned access point location has a suitable cable and power.
- Map the traffic. Document guest, staff, payment, room-tech and building systems and how they are separated today.
- Decide the onboarding journey. Choose how a guest gets a profile at booking, check-in or in the app, and how it ends at check-out.
- Plan the authentication service. Decide where it runs, who maintains it and how it scales across sites.
- Write the privacy position. Define what is collected, what the guest is told and how long records are kept.
- Plan support. Decide who answers a guest’s device problem, who monitors the service and what happens when something fails at 11pm on a Friday.
Steps 1 to 4 can be completed before any purchase. They produce the evidence a business case needs and keep suppliers’ quotes comparable.
Our view
Hotels that get Passpoint right treat it as part of the network, not as an add-on. The guest sees one thing: their phone is online when they arrive. Behind that sit access point design, cabling, authentication, segmentation and ongoing monitoring, and a weakness in any of them shows up as a Wi-Fi complaint.
We have more than 35 years of experience as a Cisco partner, and our work covers hospitality alongside education, manufacturing and other sectors. We approach a project in this order: audit what is there, survey the building, design to the findings, and then keep the service healthy through managed support. That sequence keeps the cost of surprises low, because the audit and survey surface cabling, coverage and security gaps before the design is fixed.
For groups, we would also look at the whole estate, because one authentication design across several sites is what makes a shared guest profile work in practice.
Jacob
Preparing your hotel with Re-Solution
If your team wants to introduce Passpoint, we start with evidence. Our network audits establish what the current network can and cannot support, and our wireless surveys measure coverage across the property. Once the service is live, our managed services cover ongoing support and monitoring, and Network as a Service is available for operators who prefer a subscription model. You can see how we work with the sector on our hospitality page, or contact us through the Re-Solution site to discuss a property or group.
For procurement teams weighing how to buy, our guide to NaaS pricing models and the procurement checks for outsourced network management set out what to ask for in a quote.
FAQ
Is Passpoint the same as Wi-Fi Calling?
No. Wi-Fi Calling carries voice calls and texts over a Wi-Fi network, while Passpoint is a way of joining and authenticating on that network. Passpoint can help a phone reach the hotel’s Wi-Fi, but it does not provide calling itself, according to the Wi-Fi Alliance overview.
Do we still need a captive portal if we use Passpoint?
Most hotels keep one. A portal handles first-time onboarding, guests with devices that do not support Passpoint and acceptance of terms. Passpoint then removes the repeated login for guests who already hold a profile. The two work together.
Can Passpoint work across all the hotels in a group?
Yes, when the properties share an authentication design. Trade reporting in Hotel Management describes one guest profile connecting automatically across participating properties in a brand. Each site needs compatible wireless equipment and consistent configuration.
Is our existing Wi-Fi able to support Passpoint?
It depends on the access points, controllers and authentication service. The Wi-Fi Alliance requires enterprise authentication for Passpoint, so equipment limited to personal-key or legacy security will need replacing or upgrading. A network audit gives a definite answer for your estate.
What guest data does Passpoint expose?
That depends on the authentication method. The Wi-Fi Alliance’s deployment guidelines list items such as the Wi-Fi MAC address, identity, location and traffic analytics, and recommend notifying users before personal information is communicated. Plan the privacy notice together with the authentication design.
Sources
- Wi-Fi CERTIFIED Passpoint Technology Overview, Wi-Fi Alliance
- Passpoint Deployment and Implementation Guidelines v1.4, Wi-Fi Alliance
- How brands can streamline Wi-Fi standards across properties, Hotel Management
Recommended
- SD-WAN for Hospitality: A UK Guide for Multi-Site Operators
- Hotel WiFi Design for UK Hotels: Avoid Cabling Rework and Data Risks
- Cloud networking in hospitality: a guide for IT leaders
- 8 Step Guest WiFi Captive Portal Deployment for IT Decision Makers







