I’ve always said that if Apple Watch ever gained direct Suica loading with parental controls, Apple could make a killing selling it into the Japanese education market. watchOS 7 Family Setup is almost there for the JP market but needs one more thing: Family Suica.
The service outline is simple and combines what car keys do in Wallet with digital key sharing and Apple Cash Family does with transfers and limits. A master Apple Pay Suica ID is setup on an iPhone and manages family member Apple Pay Suica on other devices. The master ‘organizer’ would transfer stored fare (SF) via Messages and set spending limits just like Apple Cash Family does. Simple intuitive convenience.
Apple Pay Family Suica also needs transferable commuter passes. That way a parent can set one up for a child, transfer it to Apple Watch and renew it remotely. Transferable commuter passes would also be handy in our COVID teleworking era as working parents might not need a pass every working day. A “hey honey can I borrow your pass today,” thing that plastic transit card users do all the time.
So far nobody has managed to to produce a smartwatch that matches the super convenience of Apple Watch and Apple Pay Suica. If JR East and Apple produce Family Suica, they would effectively future-proof both next generation Suica and Apple Watch in the Japan market.
After posting about the global NFC possibility of Pixel 5 and Fitbit, a reader forwarded some interesting Pixel 4 FeliCa information. We all know the official story that FeliCa only works in the Japanese Pixel 4 SKUs and no other models. However, there are indications that Google installed FeliCa capable hardware in all Pixel 4 models worldwide all this time but only enables the Japanese SKUs.
The reader asked me to post some information so that we can find out the truth with help from other readers of this blog. We are looking for non-JP Pixel 4/4a SKU users who can tag read their Pixel 4/4a device with another Android device loaded with the NXP NFC TagInfo app downloaded from Google Play. The steps to do this:
Install the TagInfo app, turn off NFC-A and NFC-B reads as we only want to read NFC-F tags (screenshot directly below)
Tag read the Pixel 4/4a with the TagInfo installed Android device
Take a screenshot of the NFC scan results #1
Tag read the Pixel 4/4a a second time, take a screenshot of scan results #2
Read #1 (Before Enablement): If FeliCa is present the Primary System Code in the Detailed protocol information section should be 0xFFFF. Additionally, Mobile FeliCa 4.1 will show a pre-enablement IDm starting with 05:FE.
Read #2 (After Enablement): On a JP Pixel 4 in the screenshot below, the Common Area (0xFE00) will be present, and the Primary System Code will have changed to 0xFE00, that of the Common Area. On non-JP models enablement doesn’t happen, read #2 will match read #1.
Enablement means running the Osaifu Keitai app. Let me know by Twitter @Kanjo or email the following: (1) the Pixel 4/4a model, (2) if the read #1 result indicates FeliCa with System Code OxFFFF, (3) if the first 4 digits of the IDm begin with 05:FE in read #1. Both reads should look identical so also let me know if anything changes in read #2.
The Premise What does it mean if all Pixel 4/4a models have FeliCa, does it change anything? It simply means that Mobile FeliCa is loaded and present in all Pixel 4/4a devices but Google only turns it on, and pays for, full activations on Japanese models. This doesn’t change anything in the short term. The real value is that it helps us understand what Google is up to and possible changes that might be coming later on with Pixel 5: i.e. global NFC just like Apple.
The Results Readers shared results that indicate Mobile FeliCa 4.1 present in every SKU regardless of country and match the Japanese model ‘before entitlement’ state. Mobile FeliCa is ready but the entitlement step does not occur as some system parameter prevents the Osaifu Keitai app from running.
This means Pixel 4/4a all have the same NFC hardware and Mobile FeliCa software installed, but non-JP models block Mobile FeliCa apps from running. This would explain reports of Pixel 4 users rooting a USA SKU device, changing some parameters and running Osaifu Keitai.
It’s that time of year again to think about FeliCa support on the Google Pixel platform as Pixel 5 approaches. Ever since Pixel 3 things have been the stuck in a rut: the same global NFC (A-B-F) chip is used in all models but only FeliCa keys for card emulation are installed on Japanese models, i.e., no Suica for you if you don’t have one of those.
I used to think that Google was going cheap instead of deep. Google is cheap here actually, and lazy, but there are some other reasons. It goes back to the problem many people had with Google Pay Japan FeliCa support to begin with: it’s only a UI candy coating on top of the aging Osaifu Keitai stack and apps. Instead of doing a true top to bottom Google Pay global NFC solution like Apple did, Google Pay Japan FeliCa support is just surfing on the Osaifu Keitai board. And of course the Android Pay HCE-F thing is long since dead, it’s eSE or nothing now.
The real problem is this: Osaifu Keitai is a domestic platform, Osaifu Keitai apps (Suica, etc.) are domestic apps. The various Osaifu Keitai partners and developers don’t want to deal with the extra expense of multi-lingual localization and support. But neither does Google, hence the logjam.
Google’s recent purchase of Fitbit might be the agent of change that finally breaks the jam. The Osaifu Keitai model doesn’t extend to wearables. Google Pay has to come up with something new to replace Fitbit Pay, something that works across paired devices seamlessly if Google Pay Suica is to exist on a Fitbit smartwatch paired with Pixel.
There is something new this time around that didn’t exist, or at least didn’t exist as a developer product back in 2018: Mobile FeliCa Platform and Mobile FeliCa Cloud for supporting all kinds of Mobile FeliCa services worldwide. I’m sure this arrangement got Suica on Garmin Pay.
Taken together I think there is a better chance Google will go deep instead of cheap, hopefully sooner than later. Google Pay Suica and Google Pay PASMO on Pixel and Fitbit devices from anywhere would be a very welcome development.
Additional Security Options: state of the art encryption, integrity protection option for ‘cost-balanced system solution use cases where higher priority is given to high-speed transactions while meeting the required security needs’. The new chip also complies with Public Transportation IC Card Protection Profile (PTPP).
The new hardware chip is NFC Forum Type 3 Tag compliant and works with NFC Forum certified devices.
As I explained previously, one big aim of Super Suica is sharing resources and services to reduce costs. Right off the bat Extended Overlap Service looks exactly what Super Suica wants to do: host other transit company commuter passes and reward points. The new FeliCa Japanese press release graph illustrates this, it almost looks like dual mode services in a single mode card. I think Super Suica is going to leverage the shit out of it.
Another interesting feature is the Value-Limited Purse Service. Super Suica will certainly get a stored value purse upgrade from the current ¥20,000 limit. I’m curious to find out if next generation Suica uses the new feature for additional stored value services.
One big question is when does FeliCa Networks upgrade Mobile FeliCa with all these new features and when do licensed developers get the goods. Sony and NTT Docomo already demoed Android Osaifu Keitai smartphones using FeliCa Secure ID and digital car keys with Ultra Wideband ‘Touchless’ in January. I think it’s safe to assume licensees get new FeliCa chips and upgraded Mobile FeliCa at the same time.
This is just a cursory overview. I have fingers crossed that FeliCa Dude will post something to Reddit that will delight and enlighten us when he has the time. In the meantime we have Apple Pay PASMO coming down the pike very soon in what I hope is a preview of more to come in 2021.
UPDATE FeliCa Dude has posted an excellent overview on Reddit covering the new features and what they mean for operators. More than ever I am convinced that the big new marquee features, Extended Overlap Service and Value-Limited Purse Service will be playing major roles in Super Suica.
9 months is a quick turnaround for announcing and launching an entirely new mobile transit service across 2 digital wallet platforms: Android (Osaifu Keitai) and Apple Pay. It sure beats Cubic Transportation Systems who have yet to get Apple Pay Ventra out the door more than a year after it was first announced in March 2019 on the far less complex Chicago transit area.
While many Apple Pay users in Japan are happy to have PASMO, there is always that nagging question: if I already have Apple Pay Suica that works nationwide, what’s the point of Apple Pay PASMO? All the major transit cards are cross compatible, the only difference is commuter passes…and reward points. As FeliCa Dude so astutely explained in his excellent Reddit post, Mobile PASMO is a boondoggle, the result of JR East and PASMO Association failing to cooperate and mutually host commute plans…and points.
All Japanese transit cards are slightly different versions of Suica. There could easily be one national transit card and Japanese users absolutely would love having it, but ICOCA, TOICA, manaca, SUGOCA, Kitaca, nimoca and Hayaken want to hang on to commuter passes…and points. The good news is that (1) Mobile PASMO got off the ground in a very short time, (2) JR East is providing Mobile Suica cloud assets. I suspect Mobile Suica is likely hosting Mobile PASMO as well but whatever deal they cut is hush-hush.
Suica growth, the CASHLESS tax rebate effect, COVID and all that Junya Suzuki beat me to the punch today with an excellent piece that covers the Apple Pay PASMO announcement and several recent Suica trends including the recent addition of Suica to Square. The most important one to me is the July 2020 edition JR East factsheet Suica section: “Number of e-money available shops”. The number of Suica ready stores increased 50% YOY by 324,000 in the March 2019~March 2020 fiscal year with store growth outside of station areas increasing the most.
This is a direct result of the CASHLESS Tax Rebate program which provided merchant subsidies for cashless infrastructure. That program ended June 30 but there is talk in government circles of implementing a similar program to boost the economy and drive cashless use in the COVID era.
Suzuki san points out what I have said in other posts, Mobile Suica growth from the October 2016 Apple Pay Suica start point is remarkable: 9.3 million users as of March 2020. And the growth rate is accelerating. Smaller and less expensive mobile devices like Apple Watch with Apple Pay Suica and Garmin Suica make the mobile transition attractive for a wider number of users.
With restricted travel in the COVID era every single transit company in Japan is facing tremendous pressure to reduce costs. Moving away from high cost plastic transit cards with cut and past Mobile Suica IT assets and next generation Suica card architecture will be the easiest way to do that.
The rush to mobile It starts now. Apple Pay PASMO marks the start point of a transit IC card rush to mobile digital wallets. Mobile PASMO is rebranded Mobile Suica. With next generation aka Super Suica coming in 2021, at the very least I think we’ll see similar arrangements from JR West ICOCA, JR Central TOICA and other major transit IC cards. With the addition of MaaS NFC Tag Suica, we’ll see a faster, wider uptake of Mobile Suica and sister services for payments everywhere.
And for those Open Loop advocates out there Junya Suzuki has some surprising analysis regarding the Japanese transit scene: despite some limited installation such as Okinawa Monorail, he does’t see transit companies going in for Open Loop in any big way. Mag strip paper ticketing will gradually be eliminated as next generation transit gates go into service over the next few years but mobile transit cards and paper QR Codes will be the replacement, not Open Loop.
As I have said before, the whole ‘Open Loop vs Closed Loop aka EMV contactless bank cards vs Native IC transit cards’ debate is pre-mobile plastic era out of date thinking. Mobile wallets and apps have tossed that whole game out the window for good. Why do you think QR Code payments and UWB Touchless are coming to Apple Pay in iOS 14? It’s a whole new crazy game. Better get used to it.