I wouldn't describe 12 years as 'new'.It's therefore a bit rich of them to ask people to delay their journeys because the new method of payment they encourage everyone to use isn't reliable enough.
I wouldn't describe 12 years as 'new'.
I know that, the point I'm making is that Oyster has been the preferred payment method for over a decade, cash was only seen as a backup - which starmill recognised in his post.I thought he was talking about contactless, which isn't 12 years old.
In the early days of Oyster, if the card didn't work, you got a free ride as the assumption was that the equipment was faulty.
TfL have decided not to accept cash any more, the main use of which was as a back-up payment method, for their own operational convenience. It's therefore a bit rich of them to ask people to delay their journeys because the new method of payment they encourage everyone to use isn't reliable enough. Unless there is some evidence that the card is faulty, or has been blacklisted the course of action taken by 34D should prevail, or some other course that doesn't result in prospective passengers being asked not to travel on the bus they're attempting to board.
There remains the facility for drivers to issue an unpaid fare notice for passengers who are at risk.
But 'at risk' is very subjective. Would you want to become involved/embroiled with IRCAS?
How did you ask TFL to explain? Have you phoned them up? They are generally pretty good in resolving these matters.
What was the code on the reader when it didn't let you travel as that would be quite important in knowing whether the issue lies with your bank or with TFL.
I think I'll just stick with my Oyster!
However, an inability to tap out due to a dead battery will mean an incomplete journey fee being incurred. So anyone planning on using this means of payment needs to keep an eye on that.Android Pay has just launched today in the UK, at long last (given how long Apple Pay has been available).
Another way to pay for travel for a lot of people from now on! Interestingly, Google has said that the phone could warn you automatically that you forgot to tap out when leaving stations, which is a clever feature but not one I'd necessarily rely on!
However, if you can see your journey history based on your actual card then I'd have thought the backend system could work it out.
Given the phone has a virtual card (with a slightly different number) I wonder if you can tap out with your standard CPC if that should happen?
Given it's still the same account, and things are worked out later, that should work - in theory?
With Apple Pay, the retailer never sees your card number, so there's no way for TfL to link the transactions together. I don't know how Android Pay works, but I guess that the same applies.
With Apple Pay, the retailer never sees your card number, so there's no way for TfL to link the transactions together. I don't know how Android Pay works, but I guess that the same applies.
I've only ever used Apple Pay once just to check it was set up and working, (as I have an NR discount on my normal Oyster PAYG), but the journey was most definitely linked to my existing contactless account for the same card. I've just double checked my account, and that is still the case showing for that journey, made back in late November.
Anyone care to comment on how this might work? Does it require some integration between Apple's and TfL's systems (as I speculated above)?
I'm not 100% convinced of the discrete works/doesn't work nature of contactless cards. I raised this point on another thread and those who understand the technology better than I have assured me that it's not possible, but I still hold on to the belief that a failing card can work intermittently, depending on the particular reader it is being used with.
I have had similar problems with an Oyster card. On close inspection there was a hairline crack in the edge of the card which had damaged the wire loop (non-technical term!) which runs around the edge of the card. As the card had always been kept in a ticket wallet it was probably more to do with the age of the card than anything else. I would expect that the basic technology of contactless cards is much the same, so the reason for problems you have experienced could also be the same.Absolutely, it's either read or it isn't read, but different readers seem to have different powers. My debit card no longer works at all, but for about a year it partially worked. Some stores it worked about 80% of the time, others it didnt work at all. Sometime flexing the card made it work slightly.
Today I used apple-pay to exit from north acton tube, eventually got a 99 seek assistance. Tried at the next barrier and it worked.
I've seen 3 states
1) Doesn't read
2) Reads but doesn't compute (reads a corrupted value?)
3) Reads and works
Seen the same with oyster (again flexing the card sometimes kicked it back into life)