News / Mobile
Mobile tickets tested on North East buses
In January 2008, Go North East described a mobile-ticket trial in which a passenger could receive a digital ticket and show the handset screen to the driver.
How the trial was meant to work
The operator said the system was built with Atos Origin and Swiftpass. A customer created an online account, added funds by card, and the ticket cost was deducted from that balance. The account could also be replenished by text or configured for automatic top-ups.
The operational argument
Go North East presented the trial as a way to avoid cash and reduce the cash handled on buses. It also said that a ticket was tied to the phone that ordered it and carried coded information intended to make copying harder.
An early mobile-payment test
This was a limited 2008 experiment, not a description of a current ticket product. Its significance lay in combining a handset display, a stored-value account and driver inspection before app-based transport tickets became familiar.
The ticket was an account action
This trial did more than display a fare on a small screen. A passenger created an account and placed money in it; buying a ticket changed that stored balance and produced something for the driver to inspect. The handset was the visible end of an account-based process. A readable screen alone would not tell the operator that a fare had been paid. The coded, phone-linked ticket was intended to bind the display to a particular purchase and make casual copying less attractive.
Cash reduction changes the workflow
Removing cash from a bus affects several people at once. A passenger needs enough balance before boarding; a driver needs a quick way to recognise a ticket; the operator needs fewer cash-handling steps without making replenishment a barrier. The card, text-message and automatic top-up routes were alternatives for keeping the account usable when a journey was about to begin. The trial tested whether that chain could replace a familiar cash exchange without slowing the vehicle.
Following one commuter
A useful way to judge the experiment is to follow one commuter. They add money, select a fare, show the resulting ticket and board while the driver decides whether it is valid. Every link has to be understandable at the moment of travel. A balance that cannot be topped up, a phone that cannot present the ticket, or an inspection that takes too long weakens the convenience claimed by the service. The project made these operational dependencies visible before ticket apps became ordinary.
The service succeeded only when payment, display and inspection occurred quickly enough to fit the brief, public interval at a bus door.