Why EFTPOS at events fails, and how a payment network helps
Card terminals need very little bandwidth. What they need is a connection that answers every time. At events they often run on SIM cards or on the public WiFi, and both fail the same way: when the crowd peaks, so does demand. Mobile networks can congest when people gather, and an open guest network shared with hundreds of phones slows down for everyone, terminals included.
The fix isn't a faster connection; it's separation. Payment devices get their own network that only they can join, with coverage planned at every till, bar and stall, and priority over guest traffic where the equipment supports it. Our guide to EFTPOS at events explains why terminals fail in more detail.
Guest WiFi and the payment network, side by side
| Setting | Guest WiFi | Payment network |
|---|---|---|
| Who can join | Anyone with the password on the signage | Only your terminals, POS devices and scanners |
| Network name | Easy to find and type | Named for staff, never shown on public signage |
| Share of the connection | Limited per device so no one hogs it | Kept clear for transactions at peak times |
| What devices can reach | Guests kept apart from each other where equipment supports it | Payment devices only; guests and staff can't reach them |
| Coverage planned for | Seating, foyers and gathering areas | Every till, bar, stall row and entry gate |
Payment networks are one of several separate networks for events: staff, guests, payments, devices and cameras.
What goes on an event payment network
Anything that takes money or lets people in.
EFTPOS terminals
WiFi card terminals at bars, food stalls, merchandise and registration desks, each tested from the spot where it will sit on the day.
POS tablets and registers
Point-of-sale apps on tablets or laptops that sync orders and stock, often working alongside a terminal.
Ticket and wristband scanners
Handheld scanners at gates and doors, where coverage has to hold up inside a queue of people. See ticket scanning WiFi.
Order and receipt printers
Kitchen and bar printers that receive orders over the network and hold up the line if they drop out.
Stallholder devices
For market stall WiFi, a shared payment network that stallholders join with a password the organiser hands out, separate from shoppers.
Send a floor plan or the venue name. We reply with what the network needs and one written quote.
PCI-style separation, in plain English
The card payment industry expects payment devices to be kept apart from public networks. On an event network that comes down to three things: guests can't join the payment network, devices on the guest side can't see or reach payment devices, and only the people who need it have the payment network password.
We build the network to do those three things. What we don't do is certify your payment setup: your terminal provider and payment processor remain responsible for their devices and any compliance requirements. If they have specific network requirements, send them through and we'll set up the payment network to match. The same approach works for pop-up store WiFi, where POS and EFTPOS run for weeks rather than a weekend.
Planning EFTPOS internet for an event
- Number of terminals, POS devices and scanners
- Whether each terminal uses WiFi, SIM or both
- A map of tills, bars, stalls and entry gates
- Any network requirements from your payment provider
- Busiest trading times, such as interval or gates opening
- Whether stallholders bring their own terminals
- Who on your team holds the payment network password
- Whether payments need a backup connection
Questions people ask
Can EFTPOS terminals run on event WiFi?
Yes, as long as they're on a dedicated payment network rather than the guest WiFi. EventWiFi sets up a separate network name, password and VLAN for terminals, POS and scanners, with coverage checked at every till and gate. That keeps transactions moving when the guest network is busy and keeps payment devices out of reach of the public.
Why do EFTPOS machines stop working at busy events?
Usually because they're competing for a congested connection. SIM terminals rely on mobile networks, which can congest when a crowd gathers, and terminals on public WiFi share it with hundreds of phones. A dedicated payment network with its own coverage, plus a backup connection, removes most of that competition at the moments that matter.
Do market stallholders need their own internet?
Not necessarily. Many markets run a shared payment network that stallholders join with a password the organiser hands out, kept separate from shopper WiFi. Stallholders with SIM terminals can keep using them, though mobile signal can drop at busy times. Coverage is planned along the stall rows from the market layout.
Is a separate payment network PCI compliant?
Network separation is one part of what card security standards expect, but EventWiFi doesn't certify compliance. We build the payment network so guests can't join it or reach payment devices, and only authorised people have the password. Your terminal provider and payment processor remain responsible for their devices and any compliance requirements, so check with them.
How much bandwidth do EFTPOS terminals need?
Very little per transaction. The issue at events is reliability at peak, not speed. The payment network still needs coverage at every terminal position and a share of the connection that guest traffic can't take over. If tablets also run POS apps that sync stock or orders, include them in your device count.
Can ticket scanners use the same network as EFTPOS?
Yes. Ticket and wristband scanners often share the payment and ticketing network, because both need to work at peak moments and neither should share space with guests. Gates get their own coverage planning, since scanners move along queues. Check with your ticketing provider whether scanners keep working offline if the connection drops.
