Home |
Search |
Today's Posts |
|
London Transport (uk.transport.london) Discussion of all forms of transport in London. |
Reply |
|
LinkBack | Thread Tools | Display Modes |
#21
|
|||
|
|||
Oyster charging for journeys that don't happen
|
#22
|
|||
|
|||
Oyster charging for journeys that don't happen
|
#23
|
|||
|
|||
Oyster charging for journeys that don't happen
|
#25
|
|||
|
|||
Oyster charging for journeys that don't happen
On Fri, 13 Feb 2015 13:32:50 +0000
Roland Perry wrote: In message , at 07:18:41 on Fri, 13 Feb 2015, remarked: What do you suggest? Landside validators to confirm you've left the platform. Nah, there's a far more simple solution - if no one goes through the gates on a touch out (infra red beam not triggered) before they close THEN you deduct a penalty fare otherwise you refund. -- Spud |
#26
|
|||
|
|||
Oyster charging for journeys that don't happen
On Fri, 13 Feb 2015 09:39:18 -0600,
wrote: In article , (Roland Perry) wrote: In message , at 07:18:41 on Fri, 13 Feb 2015, remarked: This is such a fundamental fraud vector that whoever designed the system to allow it (while penalising innocent passengers whose platform was changed at the last minute) should be hung out to dry. What do you suggest? Landside validators to confirm you've left the platform. Which will be even less well understood than pink validators? "If you enter and exit at the same station without travelling, you must touch your card at a ticket machine or validator to avoid beeing charged a (penalty) fare." Easy to understand. -- jhk |
#27
|
|||
|
|||
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 |
#28
|
|||
|
|||
Oyster charging for journeys that don't happen
In message , at 22:43:23 on Fri, 13
Feb 2015, Barry Salter remarked: 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, What if the traveller was using Contactless - can the SWT ticket offices deal with hiccups then? 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... Would that require you to find someone to let you back airside in order to come back with a touch-out? I'd be reluctant to touch-in, in case it triggered yet another layer of problems. assuming you were still within the maximum journey time. Given that the exercise started when SWT cancelled a train, would Delay Repay allow you to add the time queuing at the ticket office to the overall journey delay? 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... What a performance! Just because SWT was a driver short. -- Roland Perry |
#29
|
|||
|
|||
Oyster charging for journeys that don't happen
|
#30
|
|||
|
|||
Oyster charging for journeys that don't happen
|
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Oyster error - how does this happen | London Transport | |||
They said it would never happen... | London Transport | |||
Why would this happen? | London Transport | |||
Oh dear.....I'm sure it wont happen. | London Transport | |||
What will happen to KX Thameslink? | London Transport |