View Single Post
  #27   Report Post  
Old February 13th 15, 09:43 PM posted to uk.transport.london
Barry Salter Barry Salter is offline
external usenet poster
 
First recorded activity at LondonBanter: Jul 2003
Posts: 329
Default Oyster charging for journeys that don't happen

On 13/02/2015 6:23 AM, Roland Perry wrote:

"If you touch in on a yellow card reader to make a journey and
then decide you don't want to make it or you can't because of
service disruption and touch out again to exit your Oyster card
will be charged. We apply charges to discourage fare evasion.
However, you may be able to get a refund if this happens."

The burden here is far too much on the innocent traveller.

The alternative is for the gateline assistant to let everyone out
*without* touching out, and then go to the Ticket Office to get the
touch *in* cancelled...except that's not an option at Waterloo because
SWT don't "do" Oyster at Ticket Offices, and even if they did, you'd
have missed half a dozen trains by the time you got to the front of the
queue. (Possibly a slight exaggeration).

A Ticket Office is unable to resolve a "double touch" where an OSI is
involved, as they can only cancel the last *exit* touch. So if you were
travelling Piccadilly Circus - Waterloo (LU) - Waterloo (NR) -
Wimbledon and such a situation occurred, the exit touch at Waterloo (NR)
would have to be cancelled, and then you'd have to go back down to the
Underground station and touch *out* again to close the journey
properly...assuming you were still within the maximum journey time.

Or you just wait 'til the following day and go to the Oyster website
(assuming your card is registered) or phone the Helpdesk and they'll
sort it out for you with significantly less faffing around...

Cheers,

Barry