Direct answer
The most common event problem is not that the terminal suddenly needs more data. It is that the route to the payment provider becomes congested, weak or unstable. Busy mobile cells, poor Wi-Fi coverage, metal structures, overloaded guest networks, power interruptions and untested device settings can all produce the same symptom: a transaction that spins or times out.
What matters most
- A successful test before gates open does not reproduce crowd-time mobile congestion.
- Containers and trailers can block both mobile and Wi-Fi signals.
- Payments should not compete freely with guest streaming or large uploads.
- Testing must include the real trading locations and device types.
The local mobile network changes when thousands of people arrive
A trader may test a terminal in the morning and see a good 4G or 5G signal. Later, the same cell is serving the audience, staff, traders and nearby residents. The phone or terminal can still display signal while the available capacity and responsiveness have fallen sharply.
That is why asking every trader to rely on an individual SIM does not create genuine diversity. Many devices may be sharing the same local mast and the same congestion problem.
Bars, containers and marquees change radio coverage
Wireless signals behave differently around metal, dense walls, wet crowds and temporary structures. A terminal that works outside a container may struggle at the till position inside it. A router at event control may have no useful route through a main stage or large tent to a distant trader area.
Coverage should be planned from the actual device location. For important zones, that can mean placing an access point inside or close to the structure rather than trying to increase power from far away.
One shared guest network can bury operational traffic
Payment transactions are light, but they are sensitive to delay and interruptions. Guest phones can create large bursts of traffic through updates, cloud photo uploads and video. Production devices may upload files or stream content. If all users share one unmanaged network, critical transactions can sit behind traffic that has no operational importance.
Separate networks and traffic policies let the event protect card machines, scanners and staff systems. Guest use can be given limits without preventing the event from offering it.
Power and device configuration are part of connectivity
Temporary power can be interrupted during generator changes, cable moves or local faults. A small switch or access point losing power can disconnect an entire trading zone even though the main internet connection remains healthy.
Terminals can also have their own issues: saved credentials, captive portal expectations, outdated software, aggressive power saving or payment-provider outages. A managed network removes the event connection as an unmanaged weak point, but it cannot guarantee that every third-party terminal or payment platform will never fail.
A useful test happens at the till position
- Test inside each bar, container or trader structure—not only beside the router.
- Use the same type of terminal, till or scanner expected during the event.
- Confirm credentials and whether devices reconnect after a brief power loss.
- Check separation between payments, staff and guest networks.
- Simulate heavier traffic where practical rather than relying on an empty-site speed test.
- Confirm who monitors the network and who the organiser calls during trading.
The important question is how many bars or traders stop taking payments if one connection, switch or coverage point fails. That answer determines the sensible resilience level.
Planning an event in Scotland?
Send the date, location and what needs to stay online.
No technical specification is needed. We will tell you what information matters next.