The latest OMNY bump in the road perfectly captures the downside of making contactless credit/debit cards a one size fits all solution. As the New York Post piece (via MacRumors) points out, some Apple Pay Express Transit users are being double charged for fares. Perhaps they didn’t know that Express Transit was enabled in the first place, perhaps the iPhone passed too close to the OMNY transit gate reader. It’s a classic “you’re holding it wrong” situation that has nothing to do with Apple Pay Express Transit and everything to do with the current EMV architecture and how banks implement it.
Part of the problem is that OMNY is new, it’s not working across the entire MTA system yet, and open loop EMV bank cards will never replace all classic MetroCard fare options. That job is for the MIFARE based OMNY transit card due in late 2021. Until the system is complete Metro users will have to juggle different cards and deal with a very long transition. Transport for London (TfL) users have had MIFARE based Oyster cards since 2003, contactless credit/debit cards have been ubiquitous since the 2012 London Olympics when open loop was added to the TfL Oyster fare system.
To Biometric or not Biometric? Open Loop credit/debit cards on transit gates instead of native transit cards always come with banking and credit industry baggage. Even in the contactless card heaven that is said to be London, there are a surprisingly number of gotchas: minimum limits for using cards, max limits that require PIN codes. It’s an endless loop of banks pushing one way and merchants pushing back.
The golden uptake for Apple Pay in Japan was Suica and is the same story everywhere: it’s all about getting rid of coins for transit, coffee, sandwiches, etc. The small stuff. This is the 20,000 JPY prepaid heavenly region where Apple Pay Suica sings and banks so desperately want to shut out all other players and keep all the marbles. But bank cards have an authorization problem: banks set spending limits not the card architecture. The line is always changing, what works today might not work tomorrow. The prepaid Suica architecture itself is the firewall that does away with user authorization because local processing transaction at the transit gate or store reader is all the authorization necessary.
Coke ON is one more point gimmick app that offers a free beverage for points, bottle top ‘stamps’, earned with purchases via FeliCa/Coke ON IC (Transit IC, Rakuten, nanaco, PiTaPa, WAON), credit cards and QR (LinePay, PayPay aka Line PayPayPay) linked via Coke ON. Up until now Suica was excluded from earning stamps but will join the other Coke ON IC cards starting January 14.
The Coke ON app is not particularly user friendly. It wants your data, your location and your Bluetooth to connect to Bluetooth enabled Coke vending machines. And it seems overly aggressive, at least according to a very long Twitter thread. I’m not sure what exactly the issue is for the user but it seems related to location services and suspect card reads.
Japanese users have complained about Apple Pay Suica location based transaction notification details since the default feature appeared with the iOS 12.2 Suica make over. I have no problems using Apple Pay Suica on iPhone 11 Pro to buy drinks without Coke ON. The problem described in the tweet thread could be a Coke ON incompatibility with Mobile Suica despite Suica compatibility listed on the vending machine side. Hopefully this is fixed for the Coke ON Suica debut, however I don’t plan on giving away my iPhone data to collect Coke ON app bottle top stamps.
Apple Pay Ventra The native Chicago Ventra transit card on Apple Pay is a big deal that was announced back in March. It represents the first major native transit card for the USA on Apple Pay. The much smaller Portland transit system HOP card landed safely in Wallet in May, but Ventra is still listed as ‘coming soon.’ The fault is not with Apple but with Cubic Transportation Systems who operate transit fare systems for Ventra, New York OMNY, Transport for London (TfL) Oyster, Sydney Opal, Washington DC Metro, and many more. For all of their supposed system expertise, Cubic was extremely slow rolling out Apple Pay Express Transit on TfL and has yet to deliver a single native transit card on Apple Pay or Google Pay. I hope Cubic does a better job in 2020.
Apple Pay Octopus The Apple Pay Octopus ‘now you see it, now you don’t’ saga of 2019 was strange and ultimately sad. The Apple support side was all ready to roll with iOS 13. Octopus Cards Limited announced Apple Pay support back in July with ‘coming soon’ website artwork that was pulled when the launch was officially delayed on December 19. My take is that OCL parent Hong Kong MTR made, or was forced into, a political decision to limit services, starting with the unexplained service outage of Smart Octopus during the Hong Kong Polytechnic University siege. This is not a popular opinion.
Readers have reported riot damage to MTR infrastructure and suggest this might be a reason for the Apple Pay Octopus delay. I don’t buy it. Hong Kong MTR, or someone higher up, wants to limit services and control movement, not open them up. But this introduces great risk: moving people are moving money. Limit services and the flow of people, and you limit the flow of money. In this scenario Hong Kong doesn’t have a future. More than anything, I hope Hong Kong gets it’s future back in 2020.
AquaBit Spirals CEO Tomo Hagiwara took up my challenge earlier this year to raise the Japanese Softcream Cashless Index (SCI) to ‘over 5’ in time for the Tokyo Olympics. I figure if mundane softcream stalls are cashless, Japan is truly cashless. Today his company is teaming up with industry heavyweights JR East, Sony and DNP to deliver on that promise and bring inexpensive MaaS (Mobility as a Service) NFC tag payments (via AquaBits SmartPlate) to the masses, and the masses of merchants who don’t want to shell out for NFC reader checkout hardware. It’s the first real NFC challenge to inexpensive, infrastructure light QR Code payment schemes that leverage the established base of mobile networks and smartphones. Small businesses only need to sign up for an online payment service and put a NFC tag sticker on the checkout counter.
Since all NFC flavors (NFC A-B-F) are required for smartphone NFC certification, Read/Write FeliCa tags work on any smartphone with NFC-F even if FeliCa transactions keys for card emulation (Suica, iD, QUICPay, etc.) are not installed. Translation: inbound Android devices can use NFC tag FeliCa payments even if they can’t use Suica.
The one remaining question on the Apple side of the equation is what NFC tag integration Apple Pay has in store. Jennifer Bailey announced NFC tag Apple Pay testing back in May without a delivery date, and no details since. Ideally an NFC tag integrated Apple Pay would use Sign in with Apple to streamline or eliminate 3rd party payments service account signup within an app, and without an app via background NFC tag reading. The more ‘it just works’ integration, the better. Nobody wants to signup for a PayPay-like service on the spot just to buy hotdogs and beer at a stadium game, or softcream.
I suspect there are a few reasons for the brouhaha. The Oyster IC transit card has been around since 2003, open loop EMV contactless cards service started in 2012, Apple Pay support arrived in 2015. MTA on the other hand only started OMNY with very limited open loop transit service in late May. The majority of MTA users still do the MetroCard manual swipe thing. In short TfL users are very familiar with Oyster transit IC cards, contactless bank cards and Apple Pay. They are well aware of the Express Transit difference. The same is true for Apple Pay users in areas like Sydney with a similar transit card system.
MacRumors did a good job of reporting the initial Express Transit on TfL test ramp up before the official debut. Joe Rossignol’s explanation of Express Transit mode support in “parts of Japan” is rather odd though. Which parts does he think don’t work?
The Suica part covers JR East, but since Suica is part of the Japan Transit IC Mutual Use Association this means that Apple Pay Suica works with the PASMO, ICOCA, manaca, nimoca, Pitapa, Toica, Sugoca, Kitaca and Hayaken parts. The Okinawa part will be joining in April 2020. Maybe Rossignol means the parts outside of the blue/pink square mutual transit use area? Most of these are already transit compatible with Apple Pay Suica (the ones with IC arrows pointing at them). This leaves the ones without IC arrows, which will be joining with Super Suica in 2021.
With the exclusion of the soon to join Okinawa OKICA, Apple Pay Suica already covers all the major transit parts in Japan. I have no idea which Apple Pay Suica incompatible parts Rossignol is referring to. The Minobu line? The Oigawa Railway? It is a mystery.