Reports of the Apple Pay EMV Express Transit option coming to TfL in ‘coming months’ notwithstanding, it does nothing for the many TfL users who need to use Oyster. Oyster card on Apple Pay and Google Pay is kinda like Brexit, endlessly discussed but never decided. TfL would like to get rid of Oyster altogether, I imagine the banks like it that way. Hoping that EMV will evolve and fix things is wishful thinking. Either way a decision has to be made at some point about native Oyster on digital.
The feature will undoubtedly be back for the final release but, again, heavy duty under the hood Wallet construction continues in the run up to the Apple Card release and iOS 13. We’ll get lots of new Apple Pay Wallet details at WWDC19.
Express Transit Card for transit cards and Express Mode for Student ID cards in iOS 12 are kind of a mess. They are the same option for the same thing with different names in different places. Express Mode for Student ID is on the card itself, while Express Transit is in Wallet settings.
Express vs Card Clash
Prepaid cards, stored value (SV), present a problem for Wallet. SV cards in Wallet want to be exactly like they are in plastic, tap and be done without any authentication. But what happens when Wallet has multiple SV cards, each one wanting to be an Express Transit or Express Mode card? The fine print on Use Express Transit with Apple Pay illustrates the messy dilemma and limitations of iOS 12 Wallet: you can set one payment card and one transit card per transit network, except for China which doesn’t allow EMV Express Transit at all.
In this scenario an Apple Pay user can set both a HOP card and a payment (credit/debit) card to use on Portland TRiMet. What happens at the transit gate if the iPhone user also has a Student ID card in Wallet with Express Mode turned on? Apple Pay HOP and Student ID card are both MIFARE cards, the payment card is EMV. If TriMet has their backend system act together and are using the latest NFC chip sets from NXP, the gate reader will call up the HOP card and ignore the others. Everything ‘just works’, the user is on their way.
If the transit fare system is not configured correctly, or uses outdated technology, the same Apple Pay user ends up with ‘card clash’ at the transit gate. Instead of automatically selecting the HOP card, the gate says, ‘give me a NFC card’ and Apple Pay goes into default mode that completely ignores Express Transit: the user has to unlock the device then manually select and authenticate a card with Face ID/Touch ID.
Multiple Express Cards in iOS 13 Wallet
There are major Japanese eMoney prepaid cards on Android Osaifu Keitai and its candy wrapper cousin Google Pay that are missing on Apple Pay: WAON, Rakuten Edy and nananco. One ‘missing on Apple Pay’ reason is that iOS 12 Apple Pay Wallet lacks a smart way to deal with multiple Express Transit and Express eMoney Cards. Wallet can hold multiple Suica cards but only one of them can be Express Transit. It’s the same deal for every eMoney card.
This started to change in iOS 12.3 with the addition of Express Transit with Payment Cards. The massive rebuilt of iOS 12.3 Wallet means that iOS 12.3 is basically iOS 13 Wallet already, and the heavy work continues with the temporary removal of Payment Card Express Transit in iOS 12.4 Public Beta.
iOS 13 Wallet will complete the journey, hopefully delivering a vastly improved and unified Wallet UI that elegantly solves the multiple Express Transit/Express Card issue, and eliminates card clash. At a transit gate the user should only have to tap, at checkout the user should only have to select a payment logo on a screen or tell the sales clerk Suica, Mastercard, etc., and pay.
The end of paying with just “Apple Pay”?
More payment options in iOS 13 Apple Pay Wallet will present users with a problem: more choices. Telling the sales clerk “Apple Pay” does’t work anymore except in regions where bank cards remain the only Apple Pay option. In Japan, Apple Pay users already say Suica, iD, QUICPay or NFC Pay. Hong Kong Apple Pay users will have the option to use Octopus or bank cards, and so on.
As Apple Pay matures with more payment options and services, it starts to resemble our real overstuffed wallets. 30 years of using a Mac has not organized my work life one bit. In the long run, I doubt Apple Pay will organize my wallet life any better, but it’s a hell of a lot more fun to use.
Full coverage on the WWDC19 iOS 13 Apple Pay Wish List
JR East already announced the end of Mobile Suica Shinkansen eTicket Service in March 2020 and is busy building a new eTicket system that will start April 1, 2020. This is a huge change, glitches are sure to happen along the way.
A big glitch happened yesterday evening May 24 at 18:00: the Mobile Suica Shinkansen eTicket service went down. Some Apple Pay Suica users experienced performance issues with Suica Recharge in Wallet and adding new Suica cards to Wallet during the outage, Mobile Suica users on Android were affected as well. All services were restored as of May 25 5:30 am local Tokyo time.
During the service outage Mobile Suica users on iPhone (Suica App) and Android (Mobile Suica App) who purchased Shinkansen eTickets could not download purchased eTickets to their device, make any online changes to purchased eTickets, or purchase new eTickets.
JR East will refund any Mobile Suica Shinkansen eTickets that were purchased or could not be used during the service outage. JR East also stresses that any unsuccessful Suica Recharge attempts are not charged to bank cards. See the JR East Support page (Japanese language only) for details and use the link to apply online for a eTicket refund (Japanese language only).
The iOS 12 release in September 2018 was a rough one for Apple Pay Suica users. It brought new problems like random gate errors, and left old problems, like unresponsive Suica Recharge and Suica balance not updating, unfixed. Everyone experienced problems, everyone except A12 Bionic iPhone XS and iPhone XR users, that is.
iOS 12 was especially tough on Revision B iPhone X Suica users. They had suffered from the iPhone X NFC Suica problem, had finally gotten a NFC error free Rev. B iPhone that worked great on iOS 11. The sudden experience of plunging back to error filled square one was a cruel twist of fate that left them confused and upset.
iOS 12.3 fixed everything for everyone, with trouble free wicked fast Apple Pay Suica performance. It is the best Apple Pay Express Transit iOS that Apple has ever delivered. However, Rev. B iPhone X owners are still worried. One owner told me, “I think that I’ll have the same problem all over again with iOS 13.”
This is a perfectly understandable concern, but I’m going to let you in on a little secret: if you are using iOS 12.3, you are already using iOS 13 Apple Pay Wallet. Apple simply has not told you yet.
iOS 12.3 Apple Pay Wallet is a whole new thing. The changes Apple made to it in iOS 12.2~iOS 12.3 are massive. Express Transit performance gains, and the new EMV Express Transit option are equally massive. Most people assume that the Wallet changes are for Apple Card, which they are, but few people understand that the changes are also for the Apple Pay Transit support of HOP, Ventra, NY MTA, and more, which Tim Cook announced along with Apple Card on March 25.
In short, Rev. B iPhone X users, and all iPhone users, have nothing to worry about anymore. If your Apple Pay Suica or Apple Pay HOP is working great on iOS 12.3, it’s going to work great on iOS 13 too.