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
You must be logged in to post a comment.