As usual, I tried to get on the train using Apple Pay Suica at the ticket gate, but it didn’t respond at all and I got stuck. At first I thought it was because I was wearing a thick coat, so I held it up again, but there was no response … When I checked the Wallet app, all the credit cards and Suica were gone.
It sounds like he was using Suica on Apple Watch. Sakakura goes on to helpfully explain what can cause this and how to get your Wallet cards back. The most common cause for a lost Wallet is signing out of Apple ID. Another cause is turning off the passcode. As he points out, the notification warning when signing out of Apple ID or turning off the passcode is vague, it doesn’t specially say you are about wipe your credit cards and Suica from iPhone. Some users are not fully aware of the consequences and proceed, only to be rudely surprised when they find Wallet is empty.
In all cases it is easy to restore a lost Wallet. Sign-in to Apple ID, set a passcode, go to Wallet, tap + , tap Previous Card and re-add the listed cards. Suica is easier to re-add as there are no terms and conditions or security code steps involved. As always make sure iPhone has a robust network connection when adding Wallet cards.
Another issue to be aware of with Suica and PASMO is Express Mode deactivation without realizing it. This happens when iPhone Face ID has 5 false reads (easy to do when wearing a face mask), when Apple Watch is off the wrist, or when the iPhone side buttons are inadvertently pressed in a snug fitting pocket (often aggravated by the phone case).
One oddity I have encountered using Apple Pay Suica on Apple Watch is wrist band fit. Apple Pay Suica on Apple Watch works fine at the transit gate under layers of winter cloths but Express Transit is sometimes deactivated with a looser fitting band. I like wearing the braided sports loop but it tends to stretch over time and become loose compared with the snug fitting solo loop. On a recent trip I had to constantly enter the Apple Watch passcode as my winter coat sleeve layers pulled the loose fitting braided sport loop enough to fool wrist detection. From here on I’m sticking with cheaper, more reliable solo loop which never has this problem.
Here are some guides dealing with re-adding Suica and PASMO:
I finally had the chance to use Eki-Net app, aka Eki-Net 2, eTickets (JR East Shinkansen) and Ticketless (JR East Express Trains) reservations on several trips recently, a real world workout. After a shaky launch in March 2020, followed by a major system upgrade in June of this year, the foundation is in place and JR East is going all out to promote Eki-Net for the year-end travel season that will see a considerable uptick compared to last year’s ‘stay home’ and stew regimen. I posted an Eki-Net 2 overview in June that covers the basics, this post is a short followup of impressions.
Using Eki-Net eTickets at the transit gate is clean and easy as the JR East promo videos. The messy part is creating an Eki-Net Japanese online account that is completely separate from your Mobile Suica account and your JRE POINT account. They all link together but are all separate with separate login names and passwords. This is the weak point of using JR East online services, there is no single master login system ID service like Apple ID or Google Account.
Once the Eki-Net online account is setup, with a VIEW credit card duly registered for maximum JRE POINT, using the bare-bone iOS Eki-Net app is a snap. Japanese user reviews of the Eki-Net app are overwhelming negative, but I found the app covers the basics well enough for what it is designed for: finding a discount reservation for your travel date, choosing a seat, purchasing the eTicket and assigning it to a designated Apple Pay Suica (or PASMO) card, or cards if your are purchasing for more than one. Group eTicket purchase and Transit IC card assignment are very convenient features.
My only real quibbles of using Eki-Net boil down to two feature requests.
Apple Pay Support: back in the Suica App Shinkansen eTicket days, you could purchase tickets using Apple Pay or the Suica App registered credit card. Both were convenient. Eki-Net does not support in-app Apple Pay. You make purchases with the app and have to confirm the purchase with the registered card CVV number for security purposes…a pain in the butt, pull out the physical card every time because I never can remember the code. Apple Pay in-app purchase would be great to have and it should be easy enough to arrange the backend so that Apple Pay VIEW purchases earn JRE POINT automatically.
Notifications: in the current version of Eki-Net (v2.1.5) train time notifications are basically email only, once when you make the reservation, another email before train departure and a final email notification when the assigned Apple Pay Suica card or equivilant goes through the Shinkansen gate. There is a link to add the ticket train boarding day/time as a calendar event that does in a pinch, but I would also like to have regular and robust native iOS notification support. For me there is nothing so handy as Apple Watch haptic notifications.
Eki-Net works well enough as is, but having Apple Pay in-app support and iOS notifications would significantly improve the app experience. There is a lot of room for other improvements: it would be great to have smooth integration with other eTicketing services for private rail and other JR Group companies (EX, etc.). Suica is celebrating it’s 20th anniversary this year, Eki-Net is at anniversary #21. The current state of Eki-Net App and eTicketing makes it clear the mobile ticketing journey is just beginning.
FeliCa Dude did his usual public service of posting Mobile FeliCa details for the latest Pixel 6 devices. There wasn’t any change from Pixel 5, so no global NFC Pixel for inbound visitors. Nevertheless it’s a good opportunity to review some important recent developments that have taken place behind the scenes on the Android Mobile FeliCa side and examine some possible 2022 scenarios. Things have changed even if most users don’t notice any difference.
The chart outlines Mobile FeliCa on Google Pixel developments based on information from FeliCa Dude’s tweets.
Mobile FeliCa 4.0 (Pixel 4) freed Android device manufacturers from having to use embedded secure element + NFC chips from the FeliCa Networks supply chain. Any FAST certified secure element will do. This development has resulted in a number of inexpensive Osaifu-Keitai SIM-Free smartphones released by Chinese manufacturers recently that are selling well. Hopefully it will have wider implications for inexpensive global NFC Android devices. There are lots of people in Hong Kong who would buy one to use Octopus.
Mobile FeliCa 4.1 (Pixel 5/Pixel 6) introduced multiple secure element domains. This allows the device manufacturer to ‘own’ the eSE and load or delete Java Card applets. FeliCa Dude thinks that multiple secure element domains (MSED) might play a part in the MIC digital My Number Card due to launch on Osaifu Keitai devices in 2022. My Number card uses NFC-B but MSED allows the Mobile FeliCa secure element to host it anyway, an interesting development.
Mobile FeliCa 4.2 or 5.0? The next version of Mobile FeliCa (MF) will hopefully support FeliCa SD2 next generation features that shipped in November 2020, features that power Suica 2 in 1 Region Affiliate Transit Cards (aka Super Suica) which are going wide in March 2022. These cards really need to be on mobile for future MaaS service plans outlined by JR East which cannot happen until SD2 features are added.
The improvements in MF 4.1 certainly give Android device manufacturers the ability to update MF over the air but don’t hold your breath. Standard industry practice to date has been ‘buy a new device to get new features’. Apple has been a little bit better in this regard: MIFARE support was added in iOS 12 for Student ID cards and iOS 15 fixed some Calypso bugs on iPhone XR/XS and iPhone SE.
A FeliCa Dude Reddit post comment regarding Asus smartphones illustrates the pre-MF 4.0 situation: “any phone that lists ‘NFC’ compliance must support Type F (FeliCa), but as there is no Osaifu-Keitai secure element <aka Mobile FeliCa secure element>, you will be limited to reading and potentially charging physical cards: you cannot use the phone as a card itself.” That was then, this is now.
Most people assume FeliCa support requires a Felica chip but this is not true. The evolution of hardware independent Mobile FeliCa is very clear: the ‘FeliCa chip’ from Sony/FeliCa Networks requirement is long dead and gone. Manufacturers like Xiaomi claim they make special models and add FeliCa chips just for the Japanese market, but that’s just marketing BS: they run Mobile FeliCa on the same NXP NFC chipset they sell everywhere. The majority of smartphones supporting FeliCa don’t have a FeliCa chip, everything from EMV to FeliCa and MIFARE runs on any GlobalPlatform certified secure element on any Android device.
Hopefully the sum of recent Mobile FeliCa developments, along with Garmin Suica, Fitbit Suica and built in WearOS Suica showing up in recent developer builds, indicate that FeliCa Osaifu Keitai services will become standard on Android devices as they have been on all iOS and watchOS devices since 2017.
Note: this post is marked archived as construction was completed.
The JR Shibuya station platform and track realignment of the Yamanote Inner Circle line takes place October 23~24 (unless bad weather postpones it to November 20~21). All Yamanote Inner Circle train service between Ikebukuro and Osaki stations is suspended all day, both days.
JR East posted multilingual information in English, Chinese, Korean (deleted after the construction was finished) that includes detour transfer guidance to non-JR lines during the line closure. The English wording is fuzzy because the exact distinctions between mag-strip commuter passes, Suica commuter passes and Suica IC transit fare are not always clear to the reader. It’s also important to understand detour transfer rules.
Detour Transfers Tokyo area transit operators have special detour transfer rules to deal with transit situations when there is an unexpected stoppage and in-transit users suddenly need to use a different transit route from the normal one to reach their destination. Detour transfers have one rule for Suica or PASMO commuter passes, both mobile and plastic: do not use automatic transit gates during the detour portion of the route, go to a station agent window gate instead and use the reader. The station agent checks the validity of the commuter pass and waves you through, the NFC equivalent of visually inspecting printed tickets and passes. Regular non-commuter pass Suica, PASMO and other transit cards are outside of detour transfer rules and are charged normal IC transit fare.
For example, my normal commute route from JR Asagaya to Tokyu Ikegami has a line transfer point at Gotanda. A Gotanda transfer isn’t possible during the service suspension. Instead I plan to transfer at Shibuya to the Tokyu Toyoko line, ride to Jiyugaoka > transfer to Tokyu Ooimachi line > transfer at Hatanodai to Tokyu Ikegami line > exit at Ikegami.
In this case I make 2 automatic gate reads and 2 station agent window reads with my Apple Watch Suica commute pass: the JR Asagaya start point (automatic gate as always), leaving JR Shibuya (JR station agent window reader) transfer to Tokyu Toyoko line (Tokyu station agent window reader), Tokyu Ikegami (automatic gate as always).
This poster at the Tokyu Ikegami station clearly shows the ‘do not use automatic gates during detour rule,’ and which kinds of tickets can be used for detour transfers: Suica and PASMO commuter passes and all mag strip passes and tickets. For Apple Pay Suica and PASMO commuter passes, always use the station agent window reader on the detour portion and you’ll reach your final destination even with a long detour.
Express Transit Suica ruins the Apple Pay experience for using anything else. You want Apple Pay to work that way everywhere but it doesn’t. Most of the time we trudge along using Apple Pay Wallet with face mask Face ID authorization, although the Apple Pay experience on Apple Watch is a big improvement as well as being a trusted device for secure intent.
iPhone users in America are finally getting a taste of Express Transit en masse with the 2020 rollouts of Apple Pay for SmarTrip, TAP, Ventra and Clipper. Apple recently rebranded Express Transit as Express Mode on their new Wallet webpage (in Japanese it’s called Express Card). The branding change may seem trivial but it has bigger implications for first time users of new Wallet services in iOS 15, Express Mode goes places that Express Transit cannot: digital keys and digital ID.
These functions are not new of course, Express Transit cards and Student ID cards have been opening transit gates and doors these past few years. But Express Mode is for everyone and personal: your keys and badge to unlock your home door, unlock and start your car and get you into the office. With these refinements and additions it’s safe to say that iOS 15 Wallet finally delivers the digital wallet dream people have been talking about since 2010. Wallet can replace your wallet.
What’s new Last year I covered ‘coming soon’ Ultra Wideband Touchless and Code Payment (codeword Aquaman) Wallet developments. The Code Payments feature is still waiting in the wings. Steve Moser kindly confirmed that Aquaman code references are alive and well in iOS 15 with minor changes but this post will focus on announced features. In the WWDC21 Keynote Apple Pay section Jennifer Bailey announced keys and ID. The Wallet features you get from the ones listed on the iOS 15 preview page depend on the device:
Car keys with Ultra Wideband support (shareable) iPhones and Apple Watches equipped with U1 chip* (iPhone 11 and later, Apple Watch 6)
Car keys without Ultra Wideband support (sharable) Home keys (shareable) iPhone XS • Apple Watch 5 and later*
Office key Hotel key “Device requirements may vary by hotel and workplace.”
ID in Wallet iOS 15 devices watchOS 8 devices (the fine print: Not all features are available on all devices)
None of the new features will be available when iOS 15 launches. Expect them with the iOS 15.1 update or later. NFC Car keys launched on iOS 13 and iOS 14 in 2020.
The A12 Bionic • iPhone XS and later requirement for Wallet keys is easy to understand: Express Cards with power reserve. A12 Bionic (and later) powered NFC bypasses the iOS overhead with a direct connection to the secure element. It is vital that people can unlock car and home doors even when their iPhone battery is out of juice. Up to 5 hours of power reserve makes a huge difference, but only for iPhone. *Apple Watch supports Express Mode but not power reserve.
The bigger story is UWB because it is new technology that works with the Secure Element to create a whole new experience. Up to now the Secure Element was exclusively NFC. Not anymore, the Car Connection Consortium (CCC) Digital Key 3.0 specification “maintains support for NFC technology as a mandatory back-up solution.” Digital car key is first and foremost a UWB solution with NFC relegated to the back seat.
UWB connectivity adds hands-free, location-aware keyless access and location-aware features for an improved user-friendly experience…
3.0 addresses security and usability by authenticating the Digital Key between a vehicle and the mobile device over Bluetooth Low Energy and then establishing a secure ranging session with UWB, which allows the vehicle to perform secure and accurate distance measurement to localize the mobile device.
NTT Docomo and Sony demonstrated UWB car keys in action last January running on Android Osaifu Keitai hardware. Sony (FeliCa) and NXP (MIFARE and UWB chipsets) have worked closely to extend both FeliCa and MIFARE into the UWB Touchless era. The CCC Digital Key specification is open to any Secure Element provider. UWB + Bluetooth Low Energy (BLE) is simply another radio communication layer in addition to NFC.
This is significant as it opens up UWB to anything that currently uses the Secure Element and NFC. Apple has not spelled it out but suggest UWB might work with Home keys and there is no reason UWB cannot work with all keys, transit cards and Student ID. The WWDC2021 session video Explore UWB-based car keys is a great introduction and highly recommended viewing if you have any interest in the subject. The session is a bit unusual in that the discussion covers RF hardware and performance design more than software. It feels like the target audience is car manufacturers. There is a lot of detail to get lost in but here are some simple but essential points:
Secure Element improvements: the SE has always used unique keys for mutual authentication, this has been extended with ranging key deviation
Secure communication at a distance: UWB and BLE identifier randomization with secure ranging is an important security feature as UWB Touchless works over much greater distances than NFC reader tapping
Zones: the precise motion and positioning tracking of a paired UWB device with a unique key allows for ‘passive entry’ action zones, walking towards the car unlocks it, walking away locks it, etc. without any other user interaction
RF transceiver and antenna system design: is a deep and difficult art that echos the Suica creation story
JR East (Suica) and Hong Kong MTR (Octopus) have both said they are developing transit gates that incorporate UWB. This makes sense as Mobile FeliCa is now UWB savvy but after watching the WWDC21 session video I can only marvel at the complexity of the big picture because UWB is about mapping and using space and movement to perform an operation.
The engineers face countless problems and challenges to juggle in their quest to build a transit gate that delivers the same FeliCa NFC speed and reliability with UWB…at rush hour. They have to consider radiation patters, system latency and processing power, localization algorithms and much more. If they achieve their stated goal, 2023 could be a very interesting year for transit.
ID in Wallet Lots of people are excited about the possibility of adding a digital driver’s license to Wallet but as 9to5 Mac’s Chance Miller wrote, we don’t know much about about it at this point. Actually in Japan we do. The Ministry of Internal Affairs and Communications (MIC) released an English PDF: First SummaryToward the Realization of Electronic Certificates for Smartphones with a diagram that explains their digital ID system architecture. MIC remarked back in November 2020 that they are in discussions with Apple to bring the digital My Number ID card architecture to Wallet. The Android version is due to launch in 2023 and will likely employ the Mobile FeliCa Multiple Secure Element domain feature described by FeliCa Dude (FeliCa using NFC-B instead of NFC-F). A similar basic architecture with different protocols and issue process will undoubtedly be used for adding digital drivers licenses.
The Privacy question I’ll be very interested to see how ID launches in America this fall. Which outside partner company or companies are providing the service to participating states and running the backend? I suspect it will be something similar to Student ID with Blackboard running the service for participating universities. The biggest security question in my mind is who besides the TSA will use ID in Wallet, and more importantly, how? Some governments and transit agencies are pushing face recognition as a convenience in addition to security. My preference will always be for having my ID on my own Secure Element rather than somebody’s cloud server, an ID that I authorize with my own secure intent.
Wallet UI and usability improvements Wallet App didn’t get the makeover that some users asked for, but there are are a few small improvements. Up to 16 cards can be added in iOS 15, up from 12 in iOS 14. Archived passes and multiple-pass downloads help make Wallet more useable and remove some housekeeping drudgery.
I finally got two WWDC19 Apple Pay Wallet wishes granted: (1) dynamic Wallet cards and (2) region free transit cards. Apple Card does UI things in Wallet no other card is allowed to do. As far as I know this first changed with Disney’s MagicMobile launch on iPhone, Jennifer Bailey calls them “magical moments when you tap to enter.” There are similar low-key card animations in Home key and ID cards. It’s a very small step but I hope Apple adds more over time than just sprinkling seasoning card animations. Done wisely, dynamic cards could improve Wallet usability that convey important card status and account information.
Region free transit cards means that users no longer have to change the iPhone • Apple Watch region setting to add a transit card. In iOS 15 Wallet you get the full list regardless of the region setting. It’s not perfect but it is less confusing than adding a transit card in iOS 14.
Summary The overall reaction to iOS 15 has been somewhat muted but there are lots of new details. Apple Pay Wallet additions for home keys, office key, hotel key and ID build on technologies that have been on the Apple Pay platform for some time but Apple is leveraging them in new ways.
The unveiling of UWB Touchless is important and cutting edge, that might revolutionize secure transactions. The next step not only for car keys but for transit and other services that up to now have been limited to NFC. And this time, unlike NFC, Apple is leading the way for UWB.
The bottom line is that UWB opens up a lot of possibilities for many current NFC based solutions. Expect UWB Touchless support for Wallet cards in the near future that use Express Mode in new ways, and new UWB based features for a much smarter Wallet.
Zones Zones are is one of the exciting aspects of UWB Touchless, where functions are triggered by the simple act of walking towards or away from the car. It will be interesting to see how this is applied to UWB Touchless transit gates.