Apple Pay Card Clash Issue – Resolved!
Great news!
Thanks to everyone who helped!
I have both my Chase and NatWest cards set up on Apple Pay. I noticed that when I tap in and out at a tube station, Transport for London (TFL) randomly switches between my cards instead of consistently using my default. As a result, I end up being charged twice for two missed journeys. For instance, when I traveled from Heathrow yesterday, it charged my Chase card when I tapped in, but used my NatWest card when I tapped out.
I removed my Chase card months ago due to this issue, but after a trip to Athens, I re-added it to avoid NatWest’s foreign transaction fees. While using Apple Pay on the Greek subway, it properly registered my default card (Chase), which makes me believe the problem lies solely with TFL.
I’m curious if anyone else is experiencing this issue. Is it a known problem with Apple Pay? Thank you!
It sounds like you’re experiencing a frustrating issue with Apple Pay and Transport for London (TfL). From what you’ve described, it seems that TfL’s system struggles to consistently recognize the default card when multiple cards are present, leading to unexpected charges. This isn’t an uncommon issue, and some users have reported similar experiences.
One workaround you might consider is temporarily removing one of the cards while using Apple Pay with TfL, especially if you’re primarily using one card for your journeys. Alternatively, always double-check which card is selected in your Wallet app before tapping in and out at the station.
It’s worth bringing this up with TfL’s customer service, as they may have insights or solutions. Hopefully, with feedback from users, they can improve the system to better accommodate Apple Pay transactions in the future! If you find a more permanent solution, please share it with the group!