Next Up: Google Pay Octopus or Garmin Pay Octopus?

Apple Pay Octopus launch day was a big success, so successful that Octopus apologized for their servers buckling under the demand. What’s next for Octopus, Google Pay? There are some possibilities but when it comes to Android there is the matter of the Secure Element (SE), where it resides and what transaction protocols are supported.

From the NFC hardware angle everything has been ready to go on all smartphone hardware for years, NFC A-B-F is required for NFC certification. The problem has been on the SE side, the black box where all the transaction magic happens. From Global Platform the SE certification organization:

A SE is a tamper-resistant platform (typically a one chip secure microcontroller) capable of securely hosting applications and their confidential and cryptographic data (for example cryptographic keys) in accordance with the rules and security requirements set by well-identified trusted authorities.

There are different form factors of SE: embedded and integrated SEs, SIM/UICC, smart microSD as well as smart cards. SEs exist in different form factors to address the requirements of different business implementations and market needs.

Global Platform Introduction to Secure Elements

SE Wars and Google HCE ‘SE Pie in the Sky’
In the pre-Apple Pay mobile carrier hardware era, carriers used SE SIM or embedded Secure Elements (eSE) + SIM combos that chained customers to service contracts for the privilege of using mobile payments. This is the classic Osaifu-Keitai textbook maneuver pioneered by NTT Docomo: leave those pesky SIM Free whiners in the cold world of plastic cards and hard cash, or crippled digital wallets until they give up and buy an overpriced carrier SIM. This brain dead approach is one reason why Mobile FeliCa ended up being ridiculed as ‘galapagos technology’ even though everybody copied it with inferior crappy me-too products.

This carrier SE hostage situation, i.e. the Mobile Wallet SE Wars, led Apple and Google to follow different strategies to address the problem.

The Apple Pay Way
Apple’s answer of course was Apple Pay. A unique in house strategy of putting a Global Platform certified Secure Element in their A Series/S Series chips then building it out from there. Most eSE go on the NFC controller, but doing it the Apple in-house way has advantages over a NFC chip vendor bundle: control of the eSE applets and ability to update them and the Apple eSE for new protocols in iOS updates. We saw this in action with the addition of FeliCa in 2016, PBOC in 2017 and MIFARE in 2018. We may even see the addition of Ultra Wideband (UWB) Touchless in iOS 14.

What iOS 14 could look like with QR and UWB support

The Google Pay Way
Google’s answer to the carrier owned SE problem was the more convoluted evolution from Google Wallet (2011) to Android Pay (2015) and finally Google Pay (2018). Google first salvo was Host Card Emulation (HCE): “NFC card emulation without a secure element” hosted on Google’s cloud. Later on Google attempted to do the same for FeliCa with HCE-F.

But then something happened that put an end to all this: Google decided to get into the hardware business. And now we have Google Pay and Google Pixel with it’s own embedded Secure Element (eSE). With Pixel, Google decided they didn’t want to be the Secure Element cloud provider for every Android OEM out there especially when the Chinese OEMS are all rolling their own eSE based digital wallet services anyway, completely ignoring HCE. Sure, HCE/HCE-F is still there in the Android developer documentation but it’s a dying vestigial relic of the SE wars.

But Google Pixel depends on vendor bundled eSE + NFC controllers and this makes global NFC support more complicated because Google doesn’t ‘own’ the eSE, at least not in the Apple sense of making their own all in one design. This is one reason why Pixel 3/4 only support FeliCa in Japanese models even though all worldwide models have the same NFC A-B-F hardware.

The end result of all this is the Android market is a very fragmented landscape, there are no global NFC Android smartphones: a device that supports EMV, FeliCa, MIFARE, PBOC out of the box in one globally available package.

Google Pay Octopus and the Android Global NFC Installed Base
Back to our original question, can Google Pay Octopus happen? We already have Google Pay Suica right? Let’s assume that Octopus Cards Limited (OCL) has everything in place for it to happen. Here we run into the problem just described: there are’t any global NFC Android smartphones available globally. Samsung sells them in Japan and Hong Kong, Google only sells them in Japan along with Huawei, Oppo, Sharp, etc.

For OCL this means the potential Google Pay installed base that can support Hong Kong Octopus consists of Samsung Galaxy smartphones that are already using Smart Octopus in Samsung Pay; not exactly a mouth watering business opportunity worth the support expense. If Google Pixel 5 goes deep instead of cheap Hong Kong would have a potential Octopus non-Samsung Android device, but that’s only one new device not an installed base. I only see Google Pay Octopus happening if Google foots the entire support expense.

There is a way forward however for OCL: Garmin Pay Suica. The same Garmin APAC models that support Suica can also support Octopus, the recharge backend is entirely Google Pay. Garmin smartwatches work with any Android 5 and higher smartphone, a much larger installed base that bypasses the fragmented Android landscape. Garmin Pay Octopus would offer Android users a way in, who want to use Octopus on a mobile device but who don’t want to use Samsung or Apple devices.

The conclusion: forget Google Pay Octopus for the time being. Hong Kong is a golden opportunity for Gamin Pay Octopus….if Garmin can get Garmin Pay clearance from Hong Kong authorities and banks, and cut a deal with OCL. It’s certainly in Octopus’ best interest for OCL to help turn the negotiation wheels. It’s also in Google’s interest as Google Pay would supply the recharge backend as it does for Garmin Suica. Big hurdles all, but I hope it happens.

Advertisements

The Self Checkout Barcode Reader Dilemma

Reach out and touch is not something we want to be doing right now. Along with wrangling face masks and Face ID iPhone Apple Pay in the Covid-19 era, we also face another hurdle: self checkout barcode readers. Any volunteers out there who like fondling public plastic? I didn’t think so.

Convenience store self checkout all have the same deal: scan with barcode reader, tap some choices on the checkout touchscreen, scan a rewards card and pay with Apple Pay Suica, etc. The stationary barcode readers at JR East station NewDays are slightly better but you still have the touchscreen to deal with.

Barcode app and plastic variety reward cards were already a pain in the ass before all the fun started and are worse now. Apple VAS and Google Pay Smart Tap for NFC contactless reward cards has been in place for some time but uptake in Japan has been slow and small. So far only 3 contactless NFC point cards exist: Docomo dPOINT, T-Point and PONTA, and only 2 places use them: LAWSON (dPOINT and PONTA) and Tsutaya (T-Point). Part of the problem is that VAS/Smart Tap support depends on 2 factors: the reader and the POS system.

Most modern NFC readers support Apple and Google protocols but POS system support is another matter. Pre-packaged POS system providers like AirPay and J-Mups that are popular with smaller merchants don’t support them yet. This means that only big retailers with deep POS development resources like LAWSON (Mitsubishi Corp group) have added NFC contactless reward card support so far.

Apple Pay Japan supports dPOINT and PONTA cards but there are subtle differences: PONTA card requires Face/Touch ID authentication, dPOINT does not. I have not fully tested dPOINT for point payment but suspect authentication is not required for getting points but required for paying with points. One hopes that with the Covid-19 crisis in full swing, retailers and card empires (JRE Card, etc.) have the incentive to provide customers with the safest contactless experience for both payments and reward cards.

dPoint card can be accessed without Face/Touch ID, PONTA requires authentication

Mobile PASMO Q&A

What is Mobile PASMO?
Mobile PASMO is an app service, identical to Mobile Suica, for Android v6 Osaifu Keitai devices or later. Users can recharge a virtual PASMO card on the device with a registered credit card, purchase or renew commute plans, view use history, restore the PASMO card from the cloud in case of a lost device, PASMO bus transit users can also earn ‘Bus Toku’ points. Mobile PASMO launched March 18. Details are listed on the Mobile PASMO site (Japanese only).

Is it compatible with Google Pay? (Updated)
Not at this time. Users need to be careful: active Google Pay blocks Mobile PASMO transactions. Bank cards are limited to Mobile PASMO app registered credit cards: American Express, JCB, Mastercard, Visa. Credit card registration is processed by PASMO and seems to be the weakest part of the system where users are experiencing the most trouble (the rest of the system appears to be licensed Mobile Suica IT assets). Only Japanese issue cards are accepted.

Is the Mobile PASMO app multi-lingual? (Updated)
Everything is Japanese language only. Android users can download the Mobile PASMO app on Google Play.

Can I use Mobile Suica and Mobile PASMO on the same device? (Updated)
Only 6 recent Osaifu Keitai Type 1 devices support multiple transit card installs. On older Type 2 devices you can only install one and have to choose. As FeliCa Dude explains in his excellent Reddit post, “Mobile PASMO: the “me-too” that’s all about them, and not you” the Mobile FeliCa Android stack on older FeliCa chip devices isn’t like Apple Pay and does not support multiple transit cards or the ability to select one for Express Transit. Type 1 devices updated to Osaifu Ketai 8.2.1 can set one (and only one) ‘main card’ for Express Transit use, with Mobile Suica and Mobile PASMO on the same device. Here is a full device list of Type 1 (Mobile Suica and Mobile PASMO), Type 2 (Mobile Suica or Mobile PASMO), Type 3 (Mobile Suica).

I have a Mobile PASMO capable Type 2 device, which mobile transit service should I use?
It all comes down to commuter pass use, if you live in the Suica/PASMO region and use a JR East line on any part of your commute, Mobile Suica is the best choice that gives you the most options on Apple Pay and Google Pay. If you do not use a JR East line as part of your commute, Mobile PASMO is the natural choice.

Will Mobile PASMO be coming to Apple Pay? (Updated)
iOS 13.4 has some indications that Mobile PASMO might be coming at some point. Mobile PASMO uses licensed Mobile Suica assets and technology, the backend is very similar with a different operator. Apple Pay Wallet does have the ability to host multiple transit cards and select one for Express Transit. In theory a user could have a Suica and a PASMO together in Wallet. We’ll have to wait and see if the PASMO group has enough cloud resources to plug into Apple Pay/Google Pay and how willing they are to deal with non-JP issue credit cards.

Isn’t next generation ‘2 cards in 1’ Suica supposed to fix this? (Updated)
Mobile PASMO throws cold water on the one big happy mobile transit family concept of next generation Suica: sharing resources instead of “me too” fiefdoms. Even if the new card architecture fixes all the current shortcomings, which it is supposed to do, nothing can fix the selfish mindset of transit companies who refuse to cooperate. As FeliCa Dude points out, Mobile PASMO is a boondoggle, the result of JR East and PASMO Association failing to cooperate and mutually host commute plans. I suspect that auto-charge transit company premium branded credit cards are getting in the way. Japanese transit companies need to put aside old grudges and cooperate intelligently to get all transit players on mobile as fast as possible. Everybody loses out if they do not.

UPDATE: Japanese programmers digging into Mobile PASMO details find that PASMO licensed Mobile Suica IT assets for Mobile PASMO service. This makes a lot of sense and is an encouraging sign that Mobile Suica cloud resources can be licensed to host other transit IC cards for mobile (ICOCA, TOICA, manaca, etc.).

UPDATE 2: Junya Suzuki posted an article with more Mobile PASMO system details. One leading company in the PASMO Association (Tobu, Keio or Odakyu) licensed Mobile Suica assets and technology from JR East. Cut and paste IT. As said above, this is encouraging because other transit companies (JR West, JR Central et al) can license Mobile Suica assets and park it on whatever cloud service they want: AWS, Azure, NTT Data and so on. Mobile plumbing for connecting Apple Pay and Google Pay is already in place.

UPDATE 3: the Mobile PASMO device link keeps dying, here is downloadable PDF copy as backup:

Visa Japan signs with Google Pay

Visa Japan finally officially signed with a digital wallet platform and it is Google Pay. As expected it comes with a price: no FeliCa support, no dual mode support, nada, just Visa Contactless that is branded as ‘Visa Touch’ in Japan. The press release outlines recent debit cards from Sony Bank (oh the irony), JapanNet Bank, Resona and Mitsubishi UFJ.

Visa offers dual mode plastic cards that have EMV and FeliCa support in one convenient chip package that work in Japan and abroad. However these new plastic and Google Pay cards are limited to the Visa Touch payment network which is slowly growing in Japan but still full of holes. The most useful payment method for these cards will be the reliable old contact one.

Visa Japan’s long term strategy here is to gradually pull out of the FeliCa based iD and QUICPay contactless payment networks and eventually issue everything on their own Visa Touch payment network. Apple Pay FeliCa support will never sit well with Visa Japan, but now with the Google Pay move we know what Apple Pay has to do to host new Visa card products.

Unfortunately Visa has focused on big marketing pushes like the Tokyo Olympics instead of a consistent and focused drive to build contactless payment support and customer awareness that benefits all players. In a payment market already flooded with payment network logos and acceptance marks, Visa Touch is just one more logo that adds to customer confusion. Visa could have been a leader, instead they gave QR Code players a nice big opportunity, a gift that keeps on giving.

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.