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.
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.
All three fare systems are managed by Cubic Transportation Systems who also run the London Oyster and Sydney Opal systems. Cubic systems all use the same MIFARE smartcard technology but the interesting thing about SmarTrip and TAP is: (1) they are the first Cubic managed digital wallet transit cards, (2) neither system has implemented open loop fare payments for tap and go credit cards.
Ventra, Oyster and Opal all have open loop, and as of this writing Cubic has yet to deliver those transit cards on digital wallets. Why?
The SmarTrip/TAP Apple Pay launch gave us the answer that nobody wants to discuss: open loop support adds a layer of complexity and cost that stymies the support of native digital transit cards. Complexity and higher cost means fewer choices and delays, it’s as simple as that.
Open Loop is sold as the cost effective future of transit ticketing but it’s had a surprisingly rocky time in the American market. The failure is pinned on transit companies but I think credit companies are to blame. The arguments for open loop are plastic era constructs that ignore how mobile digital wallet platforms and mobile apps have changed everything. For example the oft cited open loop benefit of plastic smartcard issue cost savings completely overlooks the cost savings of digital transit cards on smartphones.
It’s high time for the credit card industry to rewrite the open loop marketing script for the mobile era, but they don’t want to do that. Expect more of the same. In the meantime, let’s hope the SmarTrip and TAP Apple Pay rollout is a sign that Chicago will be getting Apple Pay Ventra real soon.
When the AliPay Apple Pay leak surfaced earlier this year the stock story was that Apple Pay must support AliPay and WeChat Pay if Apple Pay is to have any relevance for iPhone users in China. The real story is more interesting and is centered on App Clips, not AliPay or other specific QR code payment players.
Tap or Scan Simplicity The strength of code payments is simplicity and low cost. iPhone is both a radio (NFC) and camera (scanner). NFC always has an advantage over a scanner in that it works without light and can be activated just by the user pointing their device at an NFC reader or tag.
The downside is the NFC reader side of the equation: the reader + cash register/transit gate + transaction software has a higher initial investment than a code scanner attached to a POS system. The promise of App Clips is they finally put NFC, specifically NFC tags, on the same low cost entry bar of QR codes.
App Clips are activated by:
App Clip Codes
Safari App Banners
Links in Messages
Place Cards in Maps
Let’s examine the ‘real world’ App Clip activation triggers: Apple App Clip codes, NFC tags, QR codes. For Apple designed App Clip codes, “You can scan them with your camera or tap one using NFC.14” The #14 footnote is interesting: “Camera support for scanning an App Clip code will be made available in an iOS 14 software update later this year.”
This means those fancy Apple designed App Clip codes are coming after the initial iOS 14 launch, and when they do Apple Pay Code Payments will certainly be coming with them. It boils down to one thing: making App Clips a simple tap or scan process. NFC tags still enjoy the ’point here’ advantage as App Clip does the rest. For visual codes the user has to launch the camera and scan before App Clip takes over.
The Code Payment/App Clip Network Connection Requirement Apple Pay Wallet NFC payment cards have 3 major features that payment apps do not:
Direct side button Wallet activation with automatic Face/Touch ID authentication and payment at the reader
Device transactions without a network connection
Ability to set a default main card for Apple Pay use
Apple Pay Code payments can possibly offer this for dynamic code payments where a scanner reads the code off the iPhone screen. However, static code payments are messy because Apple Pay requires a network connection to process the payment just like apps do. In the Apple Pay code payment scenario suggested by the AliPay screenshot leaks, a static code scan directly activates the appropriate Apple Pay code payment (AliPay, etc.), the user enters the amount, taps ‘Pay’, authenticates, and Apple Pay does the transaction via the network connection. It’s a similar scenario for NFC tag payments.
It’s because of this network connection requirement that I believe Apple is pushing Apple Pay NFC tag and code payments wrapped in the App Clip experience. They will work by themselves of course, but they work better as part of the total App Clip experience. This is where App Clip codes come in.
App Clip codes are Apple-designed identifiers that are uniquely paired to specific App Clips and provide an easy way to find and launch an app experience at the exact place and moment you need it. You can scan an App Clip code with your camera or by tapping one using NFC.14 We will be adding support for them in an iOS 14 software update later this year.
How is this any different from regular NFC tags or QR codes? I suspect it’s a mini qualification program for developers, payment providers and merchants to supply the ultimate App Clip experience. It also works as App Clip branding and advertising for Apple.
Are there special App Clip code tags that push the App Clip experience further than regular NFC tags and QR? I suspect so and that could be fun. Think about it, what if the Apple designed App Clip code NFC tag activated an App Clip with code payment. A QR payment without the static QR code. That would be the ultimate App Clip experience indeed.
The recent Bank of Yokohama Hama Pay app update created some buzz with the addition of an Apple Pay iD Prepaid card option. It’s similar to the Toyota Wallet approach: the bank app links the user’s bank account to an open front end bank payment service with QR code payment for debit and credit and NFC payment for prepaid.
The difference with the Hama Pay prepaid card is that VISA JP issues the iD card which means it cannot be used internationally the same way that the Toyota Wallet Mastercard iD card can; Mastercard supports iOS NFC switching, VISA JP does not.
Another weird thing: the Hama Pay ad blurb uses the ‘Touch Payment’ branding phrase with iD. Up until now VISA JP reserved that exclusively for EMV contactless card issue but not for FeliCa cards, which of course iD is. Does this mean VISA JP will finally sign with Apple Pay? Probably not.
This represents a big evolution of Apple Pay from NFC only to an open front end approach that includes NFC, Code payments and Ultra Wideband. It will be very interesting to see how bank apps evolve in the iOS 14 era as we move away from the plastic era ‘A vs B’ mind set to the bewildering variety of ‘A~Z take your pick’ era of mobile payments. We still have the Apple Pay/Face ID with face mask passcode nonsense…but that’s another post for another day.