Pixel 4 goes cheap instead of deep

As I tweeted earlier today, the updated Pixel Phone Help hardware pages tell the whole story: if you purchased your Pixel 4, 3a or 3 phone in Japan, a FeliCa chip is located in the same area as the NFC.

This is a little misleading because as FeliCa Dude pointed out in tweets, the Pixel 3 uses the global NFC PN81B ‘all in one chip’ from NXP. There is no separate ‘FeliCa chip’:

All the Pixel 3 devices have an eSE…A teardown of the global edition Pixel 3 XL (G013C) reveals a <NXP> PN81B.

FeliCa Dude

Pixel 4 teardowns will certainly reveal a PN81B or similar all in one NFC chip from NXP. Google could have gone global NFC with Pixel 4 and given Android users everywhere access to Google Pay Suica. Unfortunately Google went cheap instead of deep, sticking with the same Pixel 3 policy of only buying FeliCa keys for JP Pixel models.

Why is Google turning off FeliCa on Pixel models outside of Japan? I doubt it is a licensing restriction because the whole point of NXP PN81 is having all the global NFC licensing pieces, NFC A-B-F/EMV/FeliCa/MIFARE, all on one chip, all ready to go. It could have something to do with Google Pay Japan. For Apple Pay Japan, Apple licensed all the necessary technology and built it into their own Apple Pay.

Instead of that approach Google Pay Japan is a kind of candy wrapper around the existing ‘Osaifu Keitai’ software from Docomo and FeliCa Networks, and all of the existing Osaifu Keitai apps from Mobile Suica to iD to QUICPay. That’s why having a ‘Osaifu Keitai’ Android device is a requirement for using Google Pay Japan. Perhaps Google is content in candy wrapping things instead of retooling it all as basic Google Pay functionality and letting Android OEMs benefit from that.

Whatever the reason, the moral of this story is that Google Pay Suica will not be a transit option for inbound Android users during the 2020 Tokyo Olympics. Unfortunately, the Android equivalent of the global NFC iPhone has yet to appear.

Advertisements

Tokyo Cashless 2020: Blame the Japan Cashless Payments mess on VISA and EMVCo, not FeliCa

1️⃣ Dear JR East, we need a new Suica Charge App
2️⃣ Consumption tax relief with the CASHLESS rebate program
3️⃣ Are Apple Maps and Siri really Apple Pay level ready for the Tokyo Olympics?
4️⃣ > Blame the Japan Cashless Payments mess on VISA and EMVCo, not FeliCa

Tokyo Cashless 2020 is a series covering all things cashless as Japan gears up for the big event. If there is a topic that you’d like covered tweet me @Kanjo


Japanese journalist Akio Iwata just published a piece explaining why VISA has not signed with Apple Pay in Japan. It is paywalled and I have not read it, but Japanese readers noticed similar points in my earlier piece Why Visa refuses to join Apple Pay Japan and tweeted about it. The subject is timely and worth visiting again after the events of the past year.

Some western business journalists and industry pundits look at the Japanese payments market and write about failure: the failure of FeliCa to be universally accepted, the failure of Japanese society to use cashless payments instead of hard cash. It’s a kind of cut and paste narrative construct journalism that you see too much of these days, like the recent Financial Times piece, or worse the NFC TIMES. The narrative is persuasive enough to blind some Japanese journalists as well.

This kind of reporting plays to the expectations of a certain readership, but it completely fails to capture or explain the massive changes happening in Japan right now, set in motion by the arrival of Apple Pay in late 2016. The bulk of the cut and paste argument is that FeliCa failed to take off in Japan and because Japan failed to switch to the EMV ‘world standard’, that’s why we have the current messy situation. End of story. I don’t buy this argument at all.

FeliCa was around long before the EMVCo consortium got it’s NFC act together in the early 2000s. NFC-A is Philips, NFC-B is Motorola, NFC-F is Sony. The ISO/IEC 14443 standard was supposed to include NFC-F but the ISO ultimately decided not to include it. EMVCo created the EMV contactless standard on ISO/IEC 14443 NFC A/B.

With lots of help from JR East, NFC-F was added to the ISO/IEC 10373-6 and GSMA/GCF (Global Certification Forum) TS. 26, TS. 27 specifications. From April 2017 GCF certification for all NFC mobile devices requires NFC-A, NFC-B and NFC-F support.

It is this later development, and especially the fruit of that development, Apple Pay Suica, that I believe is unacceptable to VISA and by extension EMVCo. VISA cooperates with Apple Pay in other countries because it promotes EMV, VISA refuses to cooperate with Apple Pay in Japan because it promotes FeliCa. Instead of promoting bank card use and new services VISA is promoting technology.

I have long suspected that VISA simply does not want anything to do with Apple’s support of the Global NFC standard put in place by the NFC Forum and GSMA/GCF in 2017. It’s not only Apple…VISA refuses to support dual mode (EMV/FeliCa) Docomo iD/NFC for Android Osaifu Keitai users abroad which Mastercard, American Express and JCB do. VISA simply wants to bide time until NFC Pay/EMV contactless support in Japan is everywhere and then simply ignore FeliCa (NFC-F) all together…

Unfortunately this strategy has only accomplished one thing: it provided an opening for QR Code payment system players…

Why Visa refuses to join Apple Pay Japan

My argument is simple. The VISA and EMVCo mindset is stuck in the one size fits all single mode plastic card era. This is easy to understand as the plastic card issuing business is a very lucrative one.

But like all things there is a downside: instead of embracing the full promise of global NFC digital wallets that can match the best NFC technology for the job with multiple mode cards that do everything and ‘just work’ everywhere, we have the contactless payment turf wars which are really just plastic era fighting moved to a digital arena.

Instead of pursuing the advantages of digital wallets that merge the best of native transit cards on the front end with the best of bank cards on the back end, where they perfectly complement each other, we have bank cards fighting to be everything, which they are not and will never be. This is why Apple markets Apple Card as ‘a new kind of credit card, created by Apple, not a bank.’ It’s the reason why Apple Card is Mastercard brand, not VISA.

In Japan specifically we have VISA refusing to join Apple Pay Japan and for the most part Google Pay, and VISA Japan key player Sumitomo Mitsui fighting on and off with Mobile FeliCa key player Docomo. And the result? None of this nonsense helped strengthen VISA Japan’s market position one bit. On the other hand VISA’s arrogance pulled all the other card companies down with it and provided a huge opening for the Japanese QR Code players like PayPay.

When I wrote Why Visa refuses to join Apple Pay Japan the frenzy of Japanese QR Code payments was just getting underway. Over a year later I think this conclusion is stronger than ever and the only one that explains the reality of the current market. VISA may like to think that the Tokyo Olympics is the last great opportunity to finally kill FeliCa. That’s not going to happen.

Only by setting aside the past and embracing the multimode digital future with forward looking cooperation, can VISA (and by extension EMVCo) help bring order to the payments chaos of the Japanese market. Only cooperation can deliver the promise of cashless payments to Japan, and strengthen the long term market opportunities for all players.

The JAPAN CASHLESS Rebate Inflection Point

On the eve of the CASHLESS Rebate program launch I wrote:

Regardless of whether the CASHLESS rebate is ‘a success’ or not, it will be a tipping point. Already I notice a shift in public perception: if a store is cash only, it definitely looks behind the times in the minds of customers. I think that’s the whole point.

Consumption tax, Cashless rebates and Coffee shops

It really doesn’t matter if the CASHLESS Rebate program is a success or a dud. It’s an inflection point tick mark in the mind of Japanese society, the ship of Japan is making a tiny course correction that will veer the vessel off in a very different direction over time. We already have the big changes that the Apple Pay Suica ‘black ship’ brought to Japan since 2016, and that was just the start.

Junya Suzuki, Japan’s top journalist for all thing cashless, posted a new article: The Real Reason for the Cashless Rebate Program. Suzuki san makes the same argument: the Cashless Rebate Program is an inflection point, but with much more detail and depth. It’s a great read and worth a look even just for the pictures and captions.

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.

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.