Apple Pay Global NFC Lineup Updated with iPhone 11/Apple Watch 5

The Apple Pay Japan page has a special place in Apple’s web site galaxy. It is the only page that lists global NFC specs for Apple devices. This was the page where we learned about global FeliCa iPhone 8/iPhone X/Apple Watch 3 because Apple didn’t announce anything. So the Apple Pay Japan page check is a ritual and final word of global NFC support for every new Apple device.

There were no surprises after the latest new iPhone announcement. We all knew the Apple Pay Japan device spec list would be updated with iPhone 11/iPhone 11 Pro/Apple Watch Series 5 at some point, which it finally was this week. The ritual and peace of mind is always a good thing.

Just one last little question for Apple: when does the Hong Kong Apple Pay page finally join the Apple Pay Japan page for global NFC device specs now that iOS 13 Hong Kong Wallet mentions travel cards and Apple Pay Octopus is coming soon?

Advertisements

Pixel 3 Global NFC Evolution

Reader feedback and discussion from my earlier post analyzing the fuzzy state of iPhone 7 FeliCa and its possible support of Apple Pay Octopus, resulted in some interesting discussion about the Pixel 3 Japanese FeliCa model. From FeliCa Dude’s epic Reddit Octopus on iPhone 7 post:


<reader comment> Regarding the Pixel though, are you sure that the non-Japanese Pixel 3 models even have an eSE <embedded secure element>? I was under the impression that these were HCE <host card emulation> only.

<Felica Dude answer> All the Pixel 3 devices have an eSE, but it might not be able to be enabled by the end-user, and even if it is possible, it won’t be provisioned. A teardown of the global edition Pixel 3 XL (G013C) reveals a <NXP> PN81B.

The NXP PN81 announced in February is all-in-one off the shelf global NFC chip that includes both the frontend NFC A-B-F hardware and the necessary embedded secure element (eSE) + keys for EMV, FeliCa and MIFARE. The odd thing is that the Google Pixel 3 Japanese model apparently doesn’t use the PN81 for FeliCa, and has a separate FeliCa chip sitting in the fingerprint sensor assembly inside the back case.

Google Pixel 3 JP SKU iFixit teardowns do not exist but I did run across an interesting article from the Keitai Watch site showing a Pixel 3 JP SKU being taken apart for repair at an iCracked repair shop.

Just for kicks, I called the iCracked shop and asked about repairing a faulty FeliCa Pixel 3 device. The Pixel 3 repair technician explained that a FeliCa chip replacement was not expensive because it is not on the motherboard, “it’s attached to the fingerprint sensor assembly.” Look carefully at the picture from Keitai Watch piece and you can see the back case with fingerprint sensor assembly that the technician was referring to.

Disassembled Pixel 3 JP model from Keitai Watch

This presents a very strange situation. All Pixel 3 SKUs have the FeliCa ready PN81 chip but don’t use it, while Pixel 3 Japan SKUs might have another separate FeliCa chip attached to the back case finger sensor assemble. Google alludes to this on the Pixel 3 support page: If you purchased your Pixel 3 or Pixel 3a phone in Japan, a FeliCa chip is located in the same area as the NFC. There is also the recent batch of Pixel 3a Japan SKUs with bad FeliCa chips, but reports of bad NFC (EMV) Pixel 3a international SKUs have not surfaced; this also suggests a separate FeliCa chip. Why have two FeliCa chips in a device when one will do?

My take is different from FeliCa Dude: the Pixel 3 does not use the PN81 eSE or ‘pie in the sky’ HCE for anything. Instead, Google Pixel 3 uses the Titan M chip Secure Enclave as the virtual eSE for EMV and MIFARE, similar to what Apple does with the A/S Series Secure Enclave. Titan M FeliCa support was either not ready, or Google wanted to test the Japanese market before making a custom hardware commitment.

The point of all this is that Google has laid the foundation for a global NFC Pixel 4 made possible by a custom Google chip. The Titan M is Google’s answer to Apple’s A/S Series Secure Enclave that can host any kind of virtual embedded secure element for any kind of transaction technology, from EMV to PBOC.

I might be wrong, but even if my virtual eSE on Titan M take is incorrect, taken all together with the NXP PN81 development, I think Pixel 4 will finally be the global NFC Android device that many have hoped for.

UPDATE: extensive testing by FeliCa Dude did not support my eSE on Titan theory. The chip in question is the FPC1075 chip interface between the fingerprint sensor and the SPI bus. Pixel 4 is not global NFC, which says it all and knocks everything back to square one: there is no separate FeliCa chip, it’s a NXP PN81 chip all the way. Google hardware support page wording is very misleading, nothing more.

While the screen is on: Background Tags and Apple NFC Evolution

Background NFC tags work when the iPhone screen is on

NFC background tag support that allows users to scan NFC tags without an app arrived with A12 Bionic iPhone XS/XR and iOS 12, but the feature is only becoming truly useful with the enhanced NFC tag support in iOS 13 Core NFC. The Japanese and UK governments have already announced ID card NFC tag support for iOS 13, Jennifer Bailey previewed a new NFC tag Apple Pay feature in May, and the iOS 13 Shortcuts app lets users deploy NFC tags to create their own HomeKit automations. These are exciting developments that are just the start of new powerful and innovative NFC services on the Apple platform.

Apple’s strong point is the tight integration of software services across different devices that no other platform can match. Apple Pay Suica works on iPhone and Apple Watch, but the latter combination of technology, function and size makes it a completely different and beguiling experience. Apple Pay on Apple Watch is its own special thing.

A Temporary Split in the NFC Evolution Line?
The evolution of Apple NFC on both iPhone and Apple Watch was in lockstep up until the arrival of A12 Bionic in 2018. The A12 Bionic NFC powered background tag and Express Transit power reserve features only work on iPhone XS/XR. Apple Watch Series 4 does not support these NFC features, nor does watchOS support the Core NFC framework, this means that NFC tag Apple Pay on Apple Watch is out of the question.

Is the feature split temporary or does it represent a different line of NFC evolution for Apple Watch? The absence of Core NFC makes sense because watchOS does not support 3rd party apps, at least not yet. Express Transit power reserve however, would be a great feature to have on Apple Watch as iOS 13/watchOS 6 Apple Pay Express Transit rolls out to Chicago Ventra, Brisbane myki and Hong Kong Octopus.

Getting that feature on Apple Watch depends on how quickly Johny Srouji’s A team can implement the A12 Bionic Secure Enclave design that handles basic Apple Pay transactions directly and bypasses the OS, on the S Series chip. I cannot believe they are not pushing hard to deliver the goods as soon as possible, perhaps even with Apple Watch Series 5 featuring a S5 Bionic chip.

Delivering a S5 Bionic would get Express Transit power reserve on Apple Watch with NFC performance gains as well. It would also give Apple the option to add NFC background tag reading later on as watchOS becomes more powerful and independent.

The iPhone 7 FeliCa Question
There is one fuzzy area of iOS 13 Core NFC and it is iPhone 7 FeliCa support. At WWDC19 Apple announced that all devices, iPhone 7 and above, would support the enhanced NFC tag lineup: NDEF, FeliCa, MIFARE, ISO 7816, ISO 15693, VAS. But this does not match up with Apple’s own device specs for adding a FeliCa Suica card to Apple Pay:

Apple is telling developers that all iPhone 7 models are good for FeliCa but telling customers that only iPhone 7 JP models are good for FeliCa. This means we get one of two scenarios:

  • iOS 13 retroactively adds FeliCa support to all non-JP iPhone 7 models. Apple can do this by adding device specific FeliCa keys as iPhone 7 NFC hardware is the same for all models worldwide.
  • iOS 13 Core NFC FeliCa tags work but non-JP iPhone 7 models (without FeliCa keys) do not work for FeliCa transactions at the terminal.

The latter ‘FeliCa keys vs. No FeliCa keys’ scenario is illustrated in a comment post by Reddit user FelicaDude, if I understand correctly, that without device specific FeliCa keys iPhone 7 only works in basic Read/Write mode without encryption, with FeliCa keys iPhone 7 works in Read/Write encryption mode necessary for local offline processing with payment terminals (i.e. Suica):

The international iPhone 7s can do basic FeliCa read/write without encryption, because they embed a FeliCa-capable CLF <contactless frontend>. Apple has chosen not to provision them with Osaifu-Keitai keys, probably to avoid paying royalties to FeliCa Networks for each device.

FelicaDude Reddit

The initial iOS 13 beta 3 release build (17A5522f) did not support iPhone 7 but the revised build (17A5522g) released yesterday does. I am intrigued that something is going on with iOS 13 and iPhone 7. It’s probably a vain hope that it could be connected with the upcoming Apple Pay Octopus transit card launch which requires a FeliCa capable device, though it does makes sense for Apple to launch the Apple Pay Octopus with a wide footprint of supported devices. Let’s keep fingers crossed that iOS 13 adds full FeliCa support to all iPhone 7 models and transforms them to the global FeliCa iPhone devices they deserve to be.

UPDATE
FeliCa Dude has answered and posted the definitive take of iPhone 7 FeliCa support for all things from Octopus to iOS 13 Core NFC. We own him thanks for taking the time to cover all the angles in such detail.

Tweets of the Day: QR Code Tipping Point

I think we are witnessing the QR Code tipping point in Japan. After yesterday’s 7pay ‘latest in a series of QR Code payment system security meltdowns’, IT journalist Tsutsumu Ishikawa tweeted, “It’s time to promote FeliCa for Japanese cashless.” Ishikawa san also retweeted Twitter user S: “QR is so over,” who goes on to say that the low bar QR Code entry point only resulted in incompetent players setting up payments systems. The resulting mess and confusion ends up destroying the very cashless migration momentum the industry worked hard to create.

Mobile FeliCa has a 15 year track record of fast secure transactions that just work. Ishikawa san is right, the Japanese payments industry needs to leave any remaining Galapagos syndrome nonsense (which was a setup btw) in the past and focus on promoting FeliCa again. Apple Pay is a global NFC platform with FeliCa support as a given on every iPhone and Apple Watch it sells. Google Pay supports FeliCa too. For Apple and Google, it’s just one NFC thing. That’s all the support and encouragement necessary for the industry to march confidently into the future and ignore the QR Code sideshow.

Apple Pay Octopus and the Pixel 4 Global NFC Question

Apple Pay Octopus on iOS 13 this fall puts Pixel 4 and Google Pay in an awkward market position. Pixel 3 is a success in the Japanese market because of the inclusion of a dedicated FeliCa chip in Japanese models. Non-JP Pixel 3 models have a global NFC ready NXP PN81 chip but FeliCa is not activated for some reason, inbound users cannot use Google Pay Suica, or anything else, in Japan.

The question for Pixel 4 is this: will Google Pay use all the features of the NXP PN81 chip, or go with a custom implementation of FeliCa on their own chip for a global NFC device along with an enhanced Google Pay that seamlessly incorporates and builds on Osaifu Keitai software (killing off JP carrier Osaifu-Keitai SIM nonsense for good) instead of simply candy wrapping it, like they do for Pixel 3 JP Google Pay.

If Google goes with the first choice, Google Pay Octopus becomes a future possibility. It would also force other Android smartphone manufacturers to follow suit.

If Google keeps that same Pixel 3 arrangement they have for Pixel 4, a separate hardware model for Japan, Google Pay Octopus becomes a murky proposition. More of the same would be a shame. I hope Google does the smart thing and the right thing: global NFC on all devices is the way to go.

10/16 UPDATE: We have an answer: Pixel 4 is not global NFC, FeliCa support is restricted to JP models, the same story as Pixel 3. Google did the cheap thing again and chose not to buy FeliCa keys for all Pixel 4 models.