xPSK network: things, communities and concessionsMulti-Tenant WiFi
Stadium concession WiFi: keys for vendors, tills and handhelds on event day
You can assign every stadium till, handheld, kitchen screen and fan phone to the right network lane on event day. Choose xPSK for devices you host, 802.1X EAP-TLS for devices you own and manage, and the open network for fans. You can then revoke one leaver's key under PCI DSS v4.0.1 Requirement 2.3.2 without rekeying...
14 min read

Watch the explainer
Use xPSK, a unique WiFi key per device, when tills and handhelds cannot hold a certificate and vendors change between events. Use 802.1X EAP-TLS certificate login when you own and manage the device. A key per device lets you revoke one leaver's access, as PCI DSS v4.0.1 Requirement 2.3.2 expects, without rekeying every till.
Which network should each concession device join on event day?
The rule of thumb is one lane per device type, not one SSID per vendor. Purple Access runs three networks on the access points you already own: open, secure and xPSK. On each one, identity sets the VLAN, the virtual LAN that keeps traffic apart on shared cabling. This is the Identity-Based Networks model.
- xPSK gives each device or vendor its own pre-shared key on one SSID. Vendors call it iPSK, MPSK, DPSK or PPSK. RADIUS, the authentication protocol that checks credentials and returns policy, matches the key and returns the VLAN.
- Secure uses IEEE 802.1X, the standard for port-based network access control, with EAP-TLS. EAP-TLS authenticates the device with a certificate instead of a shared secret. Your identity provider (IdP) decides which group the device belongs to.
- Open uses a captive portal, the sign-in page a fan sees before browsing. It carries fans, attendees and bring your own device (BYOD) phones, never tills.
Put tills, card terminals, order handhelds, kitchen display screens, receipt printers and vendor laptops on xPSK by default. Move a device to the secure network only when three things are true. You own it, you manage it through mobile device management (MDM), and it can hold a certificate. Keep fans on the open network, where Engage runs guest marketing and Shield runs DNS filtering. The guest WiFi guide covers that lane.
Why the shared vendor key stops working
Many grounds run an SSID per concessionaire, with one key typed into every device. That design fails on two counts. Every extra SSID adds beacon traffic on every radio in the bowl, so airtime shrinks as the vendor list grows. The key also leaks with every staff change.
PCI DSS v4.0.1 Requirement 2.3.2 says wireless keys must change when anyone who knows them leaves the company or the role. Concession teams often include casual staff, and rosters change between fixtures. With a shared key, each departure means rekeying every till on that SSID before the gates open.
{"tone":"warning","title":"The shared key fails at the first leaver","text":"PCI DSS v4.0.1 Requirement 2.3.2 says wireless keys must change when anyone who knows them leaves. With one key per vendor SSID, one casual leaver means rekeying every till on that SSID."}
How do you choose a lane for a stadium device?
Answer four questions per device type, not per device. Two terms first. MDM is the tool that enrols and controls devices you own. Your QSA is the Qualified Security Assessor who confirms your PCI DSS scope.
{"title":"Which network should this stadium device join?","start":"q1","nodes":[{"id":"q1","question":"Is the device a fan, attendee or personal staff phone?","help":"Fans ordering from their seat count here, as do casual staff on their own phones.","options":[{"label":"Yes","to":"o1"},{"label":"No","to":"q2"}]},{"id":"q2","question":"Do you own the device and manage it through MDM?","help":"House-owned handhelds and office laptops usually qualify. Concessionaire and caterer kit usually does not.","options":[{"label":"Yes","to":"q3"},{"label":"No","to":"q4"}]},{"id":"q3","question":"Can it hold a client certificate and run an 802.1X supplicant?","help":"Check the device's WiFi settings for EAP-TLS or enterprise security.","options":[{"label":"Yes","to":"o2"},{"label":"No","to":"q4"}]},{"id":"q4","question":"Does it take card payments or sit in your PCI DSS scope?","help":"Ask your QSA if unsure. Tills and card terminals usually do.","options":[{"label":"Yes","to":"o3"},{"label":"No","to":"o4"}]},{"id":"o1","outcome":"Open network with a captive portal","detail":"Keeps fans and personal phones off every payment VLAN. Engage handles guest marketing; Shield handles DNS filtering.","link":"[Read the guest WiFi guide](www:/guest-wifi-guide)"},{"id":"o2","outcome":"Secure network: 802.1X EAP-TLS","detail":"The certificate identifies the device and your IdP group sets the VLAN. Retiring the device in MDM ends access.","link":"[See how the three lanes fit](pillar:)"},{"id":"o3","outcome":"xPSK: one key per payment device","detail":"Each till gets its own key and lands on the payment VLAN. Revoke one key when someone leaves; the rest keep trading.","link":"[See the xPSK network](product:access/networks/xpsk)"},{"id":"o4","outcome":"xPSK: one key per vendor or device","detail":"Kitchen screens, printers and vendor laptops share a vendor VLAN. Revoke the vendor key when the contract ends.","link":"[See the xPSK network](product:access/networks/xpsk)"}]}
All four outcomes run on Purple without new hardware. The open lane belongs to your guest WiFi programme rather than your concessions plan. When concessionaires own their trading devices, that kit lands on xPSK, because you cannot manage their certificates.
Which option fits which event-day scenario?
The table maps the devices you will find on a concourse walk to a lane. Each recommendation states the condition that makes it right.
{"caption":"Stadium concession WiFi: which lane for which device","asOf":"2026-06-10","columns":[{"key":"s","label":"Scenario"},{"key":"r","label":"Recommendation","highlight":true},{"key":"w","label":"Why"}],"rows":[["Concessionaire card terminal at a permanent kiosk","xPSK, one key per terminal, payment VLAN","You revoke one terminal without touching the rest; evidence for PCI DSS Req 2.3.2"],["Pop-up vendor till for one fixture","xPSK, one key per till, payment VLAN","Issue on arrival, revoke at close; no shared key to rotate"],["Pop-up vendor screens, printers and laptop","xPSK, one key per vendor, vendor VLAN","Fewer keys on a busy morning; one revoke ends the set"],["Kitchen display screens and receipt printers","xPSK, one key per device, back-of-house VLAN","Headless kit may have no supplicant or certificate store you can reach"],["House-owned order handhelds in MDM","Secure: 802.1X EAP-TLS","The certificate is the identity; retiring the device in MDM ends access"],["Club office and ticket office laptops","Secure: 802.1X EAP-TLS with your IdP","Joiners, movers and leavers follow Microsoft Entra ID, Okta or Google Workspace"],["Contract caterer fleet on its own MDM","xPSK, one key per device","You do not control the caterer's certificates or MDM"],["Casual staff personal phones","Open network with captive portal","Keeps BYOD off payment and vendor VLANs"],["Fans ordering from their seat","Open network with captive portal","Guest lane; Engage for marketing, Shield for DNS filtering"]],"footnote":"Recommendations assume Purple Access on your existing Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi access points.","download":{"filename":"stadium-concession-wifi-scenarios.csv"}}
Two rows deserve a comment. A contract caterer may run its own MDM and certificate authority, but you control neither. Unless you choose to trust certificates issued by the caterer, xPSK keeps the access decision in your hands.
Pop-up vendors get one key per vendor for non-payment kit. They arrive with devices you have never seen and leave the same night. Payment devices are the exception: a pop-up till still gets its own key on the payment VLAN.
How does xPSK work for vendor tills and handhelds?
xPSK gives you one concessions SSID for the whole ground. Every device joins with its own key, and the key decides where its traffic goes. Purple holds the keys in its cloud RADIUS service and returns the VLAN for each one.
{"kind":"flow","direction":"lr","caption":"How one xPSK SSID puts each concession device on its own VLAN","alt":"A till, handheld or kitchen screen joins one SSID, Purple cloud RADIUS checks its key, and the device lands on a payment or vendor VLAN or is refused.","nodes":[{"id":"a","label":"Till, handheld or screen","sub":"Joins the one concessions SSID with its own key","tone":"neutral"},{"id":"b","label":"Your access point","sub":"Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist or Ubiquiti UniFi","tone":"neutral"},{"id":"c","label":"Purple cloud RADIUS","sub":"Matches the key to a device and a vendor","tone":"brand"},{"id":"d","label":"Payment VLAN","sub":"Card terminals and tills only","tone":"success"},{"id":"e","label":"Vendor VLAN","sub":"Screens, printers and vendor laptops","tone":"success"},{"id":"f","label":"Key revoked","sub":"Device refused when it next connects","tone":"danger"}],"edges":[{"from":"a","to":"b","label":"Its own key"},{"from":"b","to":"c","label":"RADIUS request"},{"from":"c","to":"d","label":"VLAN for tills"},{"from":"c","to":"e","label":"VLAN for vendor kit"},{"from":"c","to":"f","label":"Unknown or revoked key","style":"dashed"}]}
How the key sets the VLAN
When a till associates, your access point sends a RADIUS request to Purple. Purple matches the key to a device and a vendor. It then returns the VLAN in the standard tunnel attributes defined in RFC 3580. The access point places the till on the payment VLAN. A kitchen screen with a different key lands on the vendor VLAN through the same SSID.
Revocation works the same way in reverse. Revoke one key, and that device is refused when it next connects. Every other till on the concourse keeps trading.
Should keys be per device or per vendor?
Issue a key per device for anything that takes card payments. That gives you evidence for Requirement 2.3.2 at the finest grain: one leaver, one key, one device. It also lets you isolate a single lost or faulty terminal.
Issue a key per vendor for non-payment kit such as kitchen screens, printers and a back-office laptop. The vendor's devices share a VLAN, and one revoke ends the set when the contract ends. Fewer keys means less admin on a busy matchday morning.
What you set in the console you already run
You change one WLAN setting, and nothing on the hardware. Each vendor names the feature differently:
- Cisco Meraki: set the SSID's association requirement to Identity PSK with RADIUS.
- HPE Aruba: use MPSK, multiple pre-shared keys, on the WLAN.
- Ruckus: use DPSK, dynamic pre-shared keys.
- Juniper Mist: use Multi PSK on the WLAN.
- Ubiquiti UniFi: use PPSK, private pre-shared keys.
Point the WLAN at Purple as its RADIUS server, then follow the Purple support article for your platform for the exact steps. The same xPSK network also runs on Cambium, Extreme and Fortinet. That keeps one key policy across a mixed estate. The xPSK network page sets out what Purple runs for you.
Where the pattern already runs
Per-key access is not new to Purple. About 1 million students and residents connect through Purple's community networks. Two examples show the pattern under peak load and with shared devices.
- Higher education move-in. Move-in day looks like a matchday: a wave of new devices arrives at once, and every one needs access fast. Across 40 buildings, residents joined Purple's community networks with their own keys. The result was 60% fewer helpdesk tickets at move-in (Purple's own data). Murray State University has signed a five-year deal for Purple PSK WiFi.
- Public sector shared devices. St George's Healthcare NHS Trust runs patient iPads for family calls on Purple. The trust saves £12k a year. Like a stadium till, a ward iPad is a shared device with no single person's identity behind it.
{"tone":"proof","title":"Per-key access at scale","text":"About 1 million students and residents connect through Purple's community networks. Across 40 buildings, Purple saw 60% fewer helpdesk tickets at move-in."}
When is 802.1X EAP-TLS the better choice for stadium devices?
EAP-TLS wins when three conditions hold together. You own the device. You manage it through MDM. It can store a client certificate and run an 802.1X supplicant, the software that answers the network's login challenge.
When all three hold, the certificate becomes the device's identity. Purple's secure network checks it against your IdP, such as Microsoft Entra ID, Okta or Google Workspace. The device's group then sets the VLAN. Joiners, movers and leavers flow from the directory you already maintain. Retire a handheld in MDM, and its network access ends with it.
Good fits on a stadium estate:
- A house-owned fleet of order-at-seat handhelds enrolled in MDM.
- Club laptops in the ticket office and the back office.
- Hospitality-suite tablets you buy, enrol and maintain yourself.
EAP-TLS fits poorly in three cases. Concessionaire tills belong to someone else, so you cannot push a certificate to them. Headless kit such as printers and kitchen screens may lack a certificate store you can reach. A pop-up vendor arriving at 10am for a 3pm kick-off has no time for enrolment. Each of those cases goes to xPSK.
The two lanes are not rivals. A ground can run both on the same access points: EAP-TLS for what you own, xPSK for what you host. Both sit on Purple, so one console gives you a single pane of glass for every policy.
What does each option cost to run on event day?
The licence is rarely the largest cost. The larger costs are staff hours on matchday morning and the effort of producing evidence for your next PCI DSS assessment. The table compares the three ways to connect concession kit.
{"caption":"Running cost of three ways to connect concession devices","asOf":"2026-06-10","columns":[{"key":"f","label":"Factor"},{"key":"p","label":"Shared PSK per vendor"},{"key":"x","label":"Purple xPSK","highlight":true},{"key":"e","label":"Purple 802.1X EAP-TLS"}],"rows":[["SSIDs to broadcast","One per vendor","One for all concessions","One for managed devices"],["First setup","Low: create SSID, share key","Low: one WLAN setting, Purple as RADIUS","High: certificates, MDM profiles, IdP groups"],["Adding a vendor on event day","New SSID or shared key handed out","Issue keys in the console","Not suited: enrolment takes too long"],["A leaver under PCI DSS Req 2.3.2","Rekey every device on the SSID","Revoke one key, issue one key","Revoke the certificate or disable in the IdP"],["VLAN assignment","Fixed per SSID","Per key, returned by RADIUS","Per IdP group, returned by RADIUS"],["Devices supported","Any WPA2-Personal device","Any WPA2-Personal device","Devices with a supplicant and certificate store"],["Main running cost","Staff hours rekeying before gates open","Console time to issue and revoke keys","MDM and certificate lifecycle"],["Evidence for an assessor","Weak: one key, many people","One key per device, revoked per leaver","One certificate per device"]],"footnote":"Effort ratings reflect event-day operation on existing access points. No option needs new hardware.","download":{"filename":"concession-wifi-running-cost.csv"}}
Shared keys look cheap because setup is quick. The cost arrives later, every time a key changes. Each change means someone visiting every affected device on the concourse before gates open.
xPSK moves that work to the console. You issue and revoke keys centrally, and no device needs touching when someone else leaves. EAP-TLS has the lowest event-day effort of all, but only once the certificate and MDM groundwork exists. If you do not run MDM today, that groundwork is a project in its own right.
Uptime matters as much as effort. A till that cannot authenticate cannot trade. Purple's cloud runs at 99.999% uptime (Purple's own data), across 80,000+ live venues in 90 countries.
What changes the answer for your stadium estate?
Five conditions bend the rule of thumb. Check each one against your own estate before you commit.
Who owns the device
Ownership is the first fork. If you own and manage the device, EAP-TLS is open to you. If a concessionaire or contract caterer owns it, xPSK is the default, because you control the key but not the device.
Whether the WLAN is in your PCI DSS scope
Ask your QSA whether the concession WLAN carries account data or connects to your cardholder data environment. If it does, Requirement 2.3.2 applies. A key per payment device then gives you clean evidence for each leaver. PCI DSS also treats network segmentation as a way to reduce scope, so a dedicated payment VLAN helps. Read the standard in the PCI SSC document library.
How often your vendors change
A ground with the same 10 concessionaires all season can issue keys once and revoke them rarely. A venue that hosts concerts, conferences and markets as well as fixtures changes vendors every week. High turnover pushes every unmanaged device to xPSK, with a key per vendor for non-payment kit.
What your controller supports
Each of these platforms supports a per-key WLAN, but local key lists live on the controller and behave differently by platform. Running xPSK through Purple's cloud RADIUS keeps the key list off the controller and in one place. Check your platform's documentation before you mix local and RADIUS-backed keys on one SSID.
How many grounds you run
A group with several stadiums, or a caterer serving many venues, often runs mixed hardware. One ground may run Cisco Meraki and another HPE Aruba. Purple is hardware-agnostic, so the same key policy and VLAN naming apply at both. Concessionaires behave like tenants with their own segment. The multi-tenant WiFi guide covers that pattern in depth.
What is the recommended default for stadium concession WiFi?
The default is xPSK on Purple for every concession device you do not manage. Use a key per device for payment kit and a key per vendor for everything else. Add EAP-TLS for the fleet you own and manage. Keep fans on the open network.
{"title":"Which lane fits your concession devices?","options":[{"name":"Purple xPSK network","fitsWhen":["Concessionaires or caterers own the device","Tills and card terminals in PCI DSS scope","Headless kit with no certificate store","Vendors change between fixtures"],"notWhen":["You own the device, manage it in MDM and it holds a certificate"]},{"name":"Purple secure network (802.1X EAP-TLS)","fitsWhen":["You own the device","It is enrolled in MDM","It can hold a client certificate"],"notWhen":["The device belongs to a concessionaire","A pop-up vendor arrives on event day"]},{"name":"Purple open network (captive portal)","fitsWhen":["Fans and attendees","Casual staff on personal phones"],"notWhen":["Any till, terminal or vendor device"]},{"name":"Shared PSK per vendor SSID","fitsWhen":["A temporary bridge while you migrate"],"notWhen":["Staff change between fixtures","The WLAN is in PCI DSS scope"]}],"recommendation":"Run Purple xPSK for every concession device you do not manage, with a key per payment device. Add Purple EAP-TLS for your managed fleet and keep fans on the open network."}
{"tone":"tip","title":"The default in one line","text":"One xPSK SSID for all concessions on Purple: a key per till on the payment VLAN, a key per vendor for everything else. Revoke, never rekey."}
Your first action
Export your current concession SSIDs and the devices joined to each. Count how many devices share each key: that number is the rekeying cost of your next leaver. Then add one xPSK SSID on the access points you already run and point it at Purple as RADIUS. Move the tills for your next fixture first. Retire each per-vendor SSID once all its devices hold their own keys. The xPSK guide for things, communities and concessions shows how this lane serves the rest of your estate.
Frequently asked questions
Will xPSK work with the access points we already own?
Yes. Purple's xPSK network runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You switch the WLAN to the vendor's per-key mode, such as Meraki Identity PSK with RADIUS or Ruckus DPSK, and point it at Purple. You need no new hardware and no rip and replace.
How does xPSK give evidence for PCI DSS v4.0.1 Requirement 2.3.2?
It lets you act on the key-change rule one device at a time. Requirement 2.3.2 says wireless keys must change when anyone who knows them leaves the company or the role. With a key per payment device, you revoke the affected key and issue a new one. Every other till keeps trading, and you avoid rekeying the whole concourse.
What does xPSK cost to run compared with a shared key?
xPSK costs less staff time per change than a shared key. A shared key forces you to retype the new key on every device after each leaver. xPSK moves that work to the console: one revoke, one new key, one device. Setup is one SSID instead of one per vendor, which also returns airtime in a dense bowl.
Can we migrate from per-vendor SSIDs during the season?
Yes. Run the new xPSK SSID alongside your per-vendor SSIDs, then move devices fixture by fixture. Start with the tills, because they carry the PCI DSS exposure. Once all of a vendor's devices hold their own keys, retire that vendor's SSID. Only WLAN settings change on the access points, so the move fits between fixtures.
Should we use 802.1X EAP-TLS instead of xPSK everywhere?
No. EAP-TLS is the stronger choice only for devices you own, manage through MDM and can load with a certificate. Concessionaire tills, kitchen screens and pop-up kit fail at least one of those tests. Run EAP-TLS for your managed fleet and xPSK for everything you host. Both run on Purple, so one console holds every policy.
How do we onboard a pop-up vendor on the morning of an event?
Issue one key for the vendor's non-payment kit and one key per payment device, each mapped to the right VLAN. The vendor enters the key on each device at the kiosk. When they leave, you revoke the keys. Nothing changes on the SSID or the access points, and nobody else's key needs rotating.
Do fans and concession devices share a network?
No. Fans and attendees join the open network through a captive portal, on their own VLAN, and never see the concession SSID. Concession devices join the xPSK SSID with keys that land them on payment or vendor VLANs. Guest marketing on the open lane runs through Engage, and DNS filtering runs through Shield.
Frequently asked questions
Will xPSK work with the access points we already own?
Yes. Purple's xPSK network runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. You switch the WLAN to the vendor's per-key mode, such as Meraki Identity PSK with RADIUS or Ruckus DPSK, and point it at Purple. You need no new hardware and no rip and replace.
How does xPSK give evidence for PCI DSS v4.0.1 Requirement 2.3.2?
It lets you act on the key-change rule one device at a time. Requirement 2.3.2 says wireless keys must change when anyone who knows them leaves the company or the role. With a key per payment device, you revoke the affected key and issue a new one. Every other till keeps trading, and you avoid rekeying the whole concourse.
What does xPSK cost to run compared with a shared key?
xPSK costs less staff time per change than a shared key. A shared key forces you to retype the new key on every device after each leaver. xPSK moves that work to the console: one revoke, one new key, one device. Setup is one SSID instead of one per vendor, which also returns airtime in a dense bowl.
Can we migrate from per-vendor SSIDs during the season?
Yes. Run the new xPSK SSID alongside your per-vendor SSIDs, then move devices fixture by fixture. Start with the tills, because they carry the PCI DSS exposure. Once all of a vendor's devices hold their own keys, retire that vendor's SSID. Only WLAN settings change on the access points, so the move fits between fixtures.
Should we use 802.1X EAP-TLS instead of xPSK everywhere?
No. EAP-TLS is the stronger choice only for devices you own, manage through MDM and can load with a certificate. Concessionaire tills, kitchen screens and pop-up kit fail at least one of those tests. Run EAP-TLS for your managed fleet and xPSK for everything you host. Both run on Purple, so one console holds every policy.
How do we onboard a pop-up vendor on the morning of an event?
Issue one key for the vendor's non-payment kit and one key per payment device, each mapped to the right VLAN. The vendor enters the key on each device at the kiosk. When they leave, you revoke the keys. Nothing changes on the SSID or the access points, and nobody else's key needs rotating.
Do fans and concession devices share a network?
No. Fans and attendees join the open network through a captive portal, on their own VLAN, and never see the concession SSID. Concession devices join the xPSK SSID with keys that land them on payment or vendor VLANs. Guest marketing on the open lane runs through Engage, and DNS filtering runs through Shield.