In article , (Mizter T) wrote:

On 12/02/2015 12:55, David Cantrell wrote:
I've found another way in which Oyster incorrectly charges people too
much.

On Tuesday evening I touched in and got on a train at Waterloo. A few
minutes later we were told that there was no driver. So I got off,
touched out, found the next train on the departures board, touched in,
and travelled.

The result - I was charged for entering and exiting at Waterloo, and
then charged again for my actual journey.

Now, I've emailed the helpline and I'm sure I'll get a refund in a few
days, but most people aren't aware of how error-prone Oyster is and
consequently that they should check their journey history. I wonder how
much TfL and SWT made from that train full of people going nowhere.

It's not an error, the system is operating as programmed. (You're a
programmer, no? Technology, including Oyster, doesn't just do it's
own random thing.)


https://www.tfl.gov.uk/fares-and-pay...touching-in-an
d-out

http://www.oyster-rail.org.uk/same-station-continuation-exits/

Those sites give different stories for the case presented here, unhelpfully.
In any case 2 minutes may be tight at Waterloo to find out about disruption
and exit through the barrier again. It seems so in this case.

--
Colin Rosenstiel