Direct answer
Card transactions normally use very little bandwidth, so a healthy Starlink connection can support many payment terminals. The common failures are more often caused by poor coverage, crowded mobile networks, unsuitable placement, power problems or all devices competing on one unmanaged network. For revenue-critical events, Starlink should be distributed properly and may be paired with mobile or venue connectivity as a backup.
What matters most
- Payment terminals need reliability and coverage more than very high speed.
- A Starlink router beside the dish will not automatically reach a trader village or distant bars.
- Payment traffic should be separated from guest browsing and heavy production use.
- A second connection can reduce risk, but only if failover and site coverage are designed properly.
Card machines do not need hundreds of megabits
A payment terminal sends a relatively small amount of transaction data. Even a busy group of tills does not usually consume the same bandwidth as guest video, cloud backups, live streaming or cameras uploading footage.
That is why a speed test alone is a poor way to judge payment readiness. A connection can show a high headline speed beside the router while terminals inside a metal bar container or at the far end of the site have an unreliable wireless path.
The connection has to reach every trading point
Starlink provides backhaul: the route from the event to the internet. The event Wi-Fi provides distribution: the network that carries that connection to the bars, trader rows, entrances and operational areas.
Distribution may involve outdoor access points, Ethernet, PoE switches and point-to-point wireless links. The design changes when bars move, structures are added or line of sight is blocked. A site plan with every required payment zone marked is more useful than simply counting terminals.
Containers, trailers and some temporary structures can reduce wireless signal significantly. An access point may need to be installed inside or immediately beside the structure, with suitable power and cable routes.
How the Starlink speed is shared
Our calculator starts with a planning assumption of 300 Mbps and lets customers model up to a 500 Mbps ceiling. This is a simple capacity model, not a promise that the service will hold one exact speed throughout the event.
If 30 active users and devices shared 300 Mbps perfectly evenly, the mathematical average would be 10 Mbps each. Real networks do not divide traffic that neatly. Many terminals sit idle between transactions, while a guest phone or production laptop may briefly use much more.
The network can therefore apply separate access and traffic priorities. Payments and ticketing can be protected while guest use is limited, preventing non-essential traffic from taking the whole connection.
Use the Starlink sharing calculator to see the simple per-user example and a human explanation of the result.
Should Starlink have a backup?
That decision should be based on the consequence of failure. A private event with one bar may accept a single managed connection. A festival with several revenue-critical bars may justify a second Starlink, 4G/5G or tested venue connection.
A backup is not useful merely because a second router exists in a box. It needs power, usable coverage and a defined way to take over. The design can range from a manual backup ready to connect through to managed failover.
What to confirm before relying on Starlink for payments
- A clear view of the sky at the proposed terminal location.
- Stable power for the backhaul and every distribution point.
- The exact locations of bars, tills and traders.
- The type of structure at each trading point.
- Whether each terminal supports Wi-Fi and any payment-provider restrictions.
- Separate guest and operational traffic where both are required.
- Testing before the public arrives, ideally with the actual device types.
- A support contact and agreed response plan during trading hours.
Starlink is a strong tool for temporary events, but the reliable outcome comes from combining backhaul, coverage, prioritisation and support into one plan.
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.