Great Western Railway glitch that generated ‘golden tickets’ leaves passengers and staff stunned
On a cool morning at a busy station, a passenger slid a phone across a ticket barrier and the gate opened with the same, mechanical ease it always does — except the code scanned was not a paid ticket. Great Western Railway’s digital system had been issuing seat reservations that acted like valid tickets at automatic barriers, creating what employees and passengers dubbed “golden tickets”.
How did Great Western Railway’s system create ‘golden tickets’?
The problem began when Great Western Railway switched its digital ticketing to a new provider. The new software generated digital seat reservations that, when scanned at many automatic barriers, displayed as an anytime single ticket. GWR allows passengers without a ticket to generate free seat reservations intended for people on long-haul tickets, and the system error extended that functionality beyond its intended use.
Who benefited and how far could people travel?
A journalist tested the loophole and was able to travel more than 500 miles, taking first-class journeys spanning multiple companies’ services. The trips included routes outside GWR’s normal service area. Valid tickets had been purchased on all the trains used, but the reservation code alone would have allowed travel across the network without payment for hundreds of miles.
What did staff see and what have operators done?
An anonymous train guard described how the reservation appears at inspection: “It does not show anything untoward… the only way a train crew member would spot it is a reservation and not a ticket is if they manually stop and check the ‘ticket’. ” Frontline staff were left confused when the pattern emerged, and senior railway staff raised alarms once they became aware of the bug.
Great Western Railway identified the issue shortly after switching to the new ticket software provider, SilverRail. SilverRail characterized the fault as a “top priority” to fix. GWR did not disclose how many journeys may have taken place using the reservation loophole. As of March 11, the software error had been patched.
What does this mean for passengers and the industry?
The episode exposed how automated gate systems and digital reservations can interact in unexpected ways when software changes. For passengers, the glitch highlighted the reliance on digital codes and the potential for gaps between reservation systems and fare-collection controls. For staff, it created a practical enforcement dilemma: automatic systems accepted the reservation, while manual checks were the only reliable safeguard.
Railway management acted to close the loophole once the problem was flagged. The provider patched the bug, and internal confusion prompted faster checks of how digital seat reservations are presented at barriers and to train crews.
Back at the station where the story began, the gate now closes and reopens without fanfare, and passengers press their cards or phones as usual. The memory of a morning when a simple reservation could pass as a ticket lingers among staff and travellers. Great Western Railway and its ticketing partner moved to fix the error, but the episode leaves a practical question in its wake: how will operators and software providers prevent the next unforeseen gap between technology and the human work of running trains?
