I was pleasantly surprised to find some hits coming from a website called limitless possibility, followed the link and discovered a great podcast by Luc-Olivier Dumais-Blais and Yanik Magnan on Japanese transit IC cards, Suica 2 in 1, the new features of FeliCa Standard SD2, Ultra Wideband Touchless and more…things I’ve been writing about for a while that never get any traffic.
Yanik does a much better job of summarizing the transit technology landscape than my messy collection of posts. I wholeheartedly agree that UWB Touchless is the perfect opportunity for Japanese Transit IC members to put aside political differences and merge, or at least ‘harmonize’ their data formats for a real all in one Super Suica. We shall see. There are things coming down the pike such as multi-secure element domain/multi-protocol Mobile FeliCa that might have transit implications. And I thank Yanik for his constructive criticism of my ‘Super Suica’ coverage. It’s very helpful and rare that anybody takes the time these days.
Extra bonus: their discussion of the Japan QR Code payment mess and a sendup of PayPay ‘gamification’ campaigns using the Canadian Tim Hortons roll up the rim thing is hilarious and spot on.
Only TWO WEEKS left before the launch of QR code payment on 23 January! For this new service, we have installed about 1,000 QR code scanners at stations and conducted a series of system and on-site tests. Prominent purple signage will also be on display to help passengers identify the gates providing the new service.
This is the debut of MTR ‘open-loop’ ticketing. Up until now MTR used the ubiquitous Octopus card, the trail blazing transit card that showed the world what smartcard ticketing can do when extended beyond transit to include eMoney payments, transforming a transit card into a transit payment platform. Unlike Japan however Octopus Card Limited (OCL) was late bringing Octopus to mobile. Part of the problem was that Hong Kong mobile carriers never had an Osaifu Keitai-like standard that bridged the Symbian and Android hardware eras. OCL also wasted time with SIM card mobile support before finally launching the mobile Smart Octopus service first on Samsung Pay in late 2018, followed by Apple Pay Octopus in June 2020 and Huawei Pay Octopus in December 2020.
But MTR still faces a problem that most Android devices don’t support FeliCa even though NFC-F is supported across all NFC capable devices. It’s the global NFC dilemma best illustrated in the Google Pay on Google Pixel situation: Mobile FeliCa is installed on all Pixel devices but Google only turns it on for Pixel models sold in Japan. There are many takes on the reasons why. My take is that Google doesn’t want to do the all the global NFC OS level support work that benefits all Android manufacturers. Google’s stance is, ‘don’t ask us, roll your own embedded Secure Element (eSE) solution.’ And so it’s a race of how many ‘Octopus on XX Pay’ digital wallet platforms OCL can line up for Android and wearables.
For MTR, QR Code open loop transit sidesteps this Android hardware mess, but will it be a success when users have to open a smartphone app with a face mask on at every gate? Apple Pay Octopus on Apple Watch sure beats that problem and then some. Long term I think NFC wearables and UWB Touchless will be the QR killer. Time will tell.
That didn’t take long. The announcement Walmart was selling majority control of SEIYU over to KKR and Rakuten was made November 16. And what was the first new management move? Adding Suica and Transit IC payment support which means Apple Pay Suica • PASMO and Google Pay Suica can finally, finally be used for paying at checkout. QR Code PayPay has been in place for awhile already. SEIYU also rolled out a new system recently for self checkout and EMV IC chip payments for SEIYU brand Saison cards (other cards have to be signed…yuck). NFC anything has been entirely missing from the SEIYU payments lineup despite the COVID crisis and a huge push for all things cashless, but Walmart has a long antagonistic history with NFC digital wallet payments.
I only noticed the change this evening when I heard the store announcement over the PA. Sure enough Suica signs were plastered at every checkout. It’s weird but somehow fitting that SEIYU is soft launching long overdue NFC contactless payments with Suica. More will come. I’m sure Walmart leaving town had nothing to do with it. Yeah, nothing at all. SEIYU stores were much better under the pre-Walmart Seibu management. Hopefully this marks a return to better service and clean modern stores.
QR will eventually replace mag strip paper tickets which are increasing expensive to recycle, and the new gates will gradually replace those ingenious paper ticket/Suica combo transit gates made by Omron. I have tried the new gate in Shinjuku and all I can say is…I’m glad I wear my Apple Watch / Apple Pay Suica on the right.
UPDATE: Conflicted Impressions Junya Suzuki has posted a deeper dive into the QR reader design on the new JR East gates with his usual fascinating analysis. Suzuki san is very big on the evolution of Suica away from local processing to a centrally processed unique ID model that does away with stored fare.
His IT background experience really shines through as he makes a convincing argument that a centralized unique Suica ID approach greatly simplifies the IT system by reducing hot-list/off-list refreshes that have to be coordinated between local and central systems.
Perhaps I am missing something in his analysis, but I think there’s a happy medium that leverages the strengths of both for a robust innovative transit fare payment system as the centerpiece of the transit business platform.
Here’s a recap of his observations and reader feedback:
Separate QR reader placement In Suzuki san’s piece JR East tech leads explain that widely separate NFC and QR readers work much better than an all-in-one approach. NFC always reacts faster than QR and this creates problems with the all-in-one reader and smartphones when fast, clean, precise read times are required. The gate QR sensor is made by DENSO. If you have ever used a poky DENSO POS QR+NFC reader at store checkout, you can relate.
Security Invisible Ink As FeliCa Dude points out, JR East is likely using IR transparent ink to create unique ID codes for security. Apparently this is already used for Okinawa Monorail Okica QR paper tickets.
Poor Walk Flow One of the great things about the mag strip paper ticket gates is they pull the ticket into the machine and spit it out at the other end of the gate. This is clever guided incentive to keep walking to pick up the ticket. With QR code transit gates people stop and wait for the reader to do something. Another nice thing about mag ticket machines is they eat the used tickets. The QR paper ticket downside not mentioned by JR East or the media: where do people put their used tickets for paper recycle? Who and what collects them, a bin?
When the AliPay Apple Pay leak surfaced earlier this year the stock story was that Apple Pay must support AliPay and WeChat Pay if Apple Pay is to have any relevance for iPhone users in China. The real story is more interesting and is centered on App Clips, not AliPay or other specific QR code payment players.
Tap or Scan Simplicity The strength of code payments is simplicity and low cost. iPhone is both a radio (NFC) and camera (scanner). NFC always has an advantage over a scanner in that it works without light and can be activated just by the user pointing their device at an NFC reader or tag.
The downside is the NFC reader side of the equation: the reader + cash register/transit gate + transaction software has a higher initial investment than a code scanner attached to a POS system. The promise of App Clips is they finally put NFC, specifically NFC tags, on the same low cost entry bar of QR codes.
App Clips are activated by:
App Clip Codes
Safari App Banners
Links in Messages
Place Cards in Maps
Let’s examine the ‘real world’ App Clip activation triggers: Apple App Clip codes, NFC tags, QR codes. For Apple designed App Clip codes, “You can scan them with your camera or tap one using NFC.14” The #14 footnote is interesting: “Camera support for scanning an App Clip code will be made available in an iOS 14 software update later this year.”
This means those fancy Apple designed App Clip codes are coming after the initial iOS 14 launch, and when they do Apple Pay Code Payments will certainly be coming with them. It boils down to one thing: making App Clips a simple tap or scan process. NFC tags still enjoy the ’point here’ advantage as App Clip does the rest. For visual codes the user has to launch the camera and scan before App Clip takes over.
The Code Payment/App Clip Network Connection Requirement Apple Pay Wallet NFC payment cards have 3 major features that payment apps do not:
Direct side button Wallet activation with automatic Face/Touch ID authentication and payment at the reader
Device transactions without a network connection
Ability to set a default main card for Apple Pay use
Apple Pay Code payments can possibly offer this for dynamic code payments where a scanner reads the code off the iPhone screen. However, static code payments are messy because Apple Pay requires a network connection to process the payment just like apps do. In the Apple Pay code payment scenario suggested by the AliPay screenshot leaks, a static code scan directly activates the appropriate Apple Pay code payment (AliPay, etc.), the user enters the amount, taps ‘Pay’, authenticates, and Apple Pay does the transaction via the network connection. It’s a similar scenario for NFC tag payments.
It’s because of this network connection requirement that I believe Apple is pushing Apple Pay NFC tag and code payments wrapped in the App Clip experience. They will work by themselves of course, but they work better as part of the total App Clip experience. This is where App Clip codes come in.
App Clip codes are Apple-designed identifiers that are uniquely paired to specific App Clips and provide an easy way to find and launch an app experience at the exact place and moment you need it. You can scan an App Clip code with your camera or by tapping one using NFC.14 We will be adding support for them in an iOS 14 software update later this year.
How is this any different from regular NFC tags or QR codes? I suspect it’s a mini qualification program for developers, payment providers and merchants to supply the ultimate App Clip experience. It also works as App Clip branding and advertising for Apple.
Are there special App Clip code tags that push the App Clip experience further than regular NFC tags and QR? I suspect so and that could be fun. Think about it, what if the Apple designed App Clip code NFC tag activated an App Clip with code payment. A QR payment without the static QR code. That would be the ultimate App Clip experience indeed.