IT journalist Junya Suzuki was answering a question of mine regarding dual mode (EMV/FeliCa) credit/debit cards which are somewhat mainstream, even on Docomo dCard, but the plastic issue Sumi Trust Visa contactless cards are EMV only.
I guess Visa Japan still wants to promote payWave (banded as Visa Touch in Japan) over better customer service. Because if Visa was promoting better customer service, they would offer dual mode for plastic cards and Apple Pay like Mastercard and American Express do.
Visa Japan has yet to sign directly with Apple Pay, the reason why Japanese issue Visa cards don’t work for Apple Pay Suica Recharge, but there may be hope. Suzuki san’s tweet suggests Visa Japan might finally sign with Apple Pay, “in the very near future.”
I certainly hope so, but given that Visa Japan has ‘been in discussions with Apple’ to officially join Apple Pay Japan since the service launched in October 2016, and have done nothing the whole time, I’ll believe it when I see it.
Okay A12 Bionic and FeliCa fans, try this on iPhone XS/XR with Apple Pay Suica on iOS 12.4 b4:
Initiate a Suica Recharge
While the recharge is processing swipe up and you will feel the haptic feedback bump indicating the recharge process has been cancelled, the Apple Pay ‘ka-ching’ all done sound and checkmark never happens
On the Suica Recharge screen tap cancel and go back to the main Suica card screen where the recharge is processing and updates the Suica balance
So, the Suica Recharge process barrels along without giving feedback. iOS didn’t do this before, is it a bug or a feature, and what’s happening? It’s related to what I observed in the previous post where the Suica FeliCa prepaid transaction and EMV Apple Pay postpay processing happened simultaneously because the A12 Bionic Secure Enclave processes FeliCa transactions directly without iOS.
We now have an explanation why EMV Express Transit went missing in the first few iOS 12.4 beta releases: Apple was doing lots of heavy duty Wallet optimization to make the prepaid recharge process fast and bulletproof.
But why? We have an explanation for that too: Apple wants the Apple Card EMV postpay to prepaid Apple Cash card recharge performance to befast and absolutely bulletproof. The Apple Cash connection with Apple Card is a huge selling point, and Apple is making damn sure that people are going to love it for the reliable Apple Cash e-money recharge performance, even if that means breaking Suica recharge a little to do it.
This kind of aggressive optimization is a good ‘problem’ for Suica to have, and because all things Suica, from the UI changes to the Express Transit performance improvements since iOS 12.2 have been a testing ground for Apple Card, unavoidable. After all, Apple Pay Suica is the closest thing to Apple Card with Apple Cash that Apple has going, making Suica a great test environment for new Apple Pay development. Hopefully Apple will fine tune and fix remaining Suica recharge issues before the final release and Apple Card debut.
Apple Pay Suica on A12 Bionic iPhone XS/XR is different from other devices because basic FeliCa transactions bypass iOS and go directly to the Secure Enclave. You can see this in action with Express Transit power reserve, but if you observe carefully you can catch it in other ways.
I caught a glimpse today buying ice coffee at a JR station NewDays shop (supplied by Doutor btw). I was recharging Suica with Apple Pay and forgot it was still processing when I touched iPhone XS to the reader. The payment went through without a problem, the recharge completed a few seconds later.
Is this a iOS 12.4 beta thing or did A12 Bionic iPhone do this all along? I suspect it did all along and makes sense: the payment transaction bypassed iOS which was busy processing the Apple Pay recharge and wasn’t ready to post a balance update to the Secure Enclave. Prepaid and postpay processing at the same time…very interesting.
Most people think all Express Transit is the same, but Suica Express Transit prepaid is very different from EMV Express Transit postpay. Suica settles the transit bill in less than 200 milliseconds (ms) locally right at the transit gate, while EMV Express Transit leisurely (500 ms) tells the gate, ‘I am bank card XXX, put it on the bill’ for settlement later between the bank and the transit agency. For EMV there is a lot of backend system work to make that happen, and even then the user sometimes has to tap twice:
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.
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.