Good old William S. Burroughs hit the nail on the head explaining what the title of Naked Lunch really meant: that awkward frozen moment when everybody in the restaurant sees exactly what is on their fork. iOS developers staring at the App Store fork don’t like what they see: an Apple platform that’s supposed to be a level playing field, where the reality is that Apple plays favorites and cuts side deals, a losing game of lowering standards.
Octopus Cards Limited (OCL) released an iOS Octopus app for tourists last week that perfectly illustrates what’s at stake in Apple’s losing game of lowering standards. The long delayed Apple Pay Octopus launch in June was very successful but OCL shut inbound visitors out by limiting the Apple Pay Octopus service to Hong Kong issue bank payment cards. This is something that Apple Pay Suica has never done. All Apple Pay cards and iPhone users from around the world are welcome to use Suica. This is why Suica remains the gold standard of what a transit card on mobile should be.
Instead of following the Suica example, the Octopus Tourist app adds an Octopus card to Apple Pay Wallet with a non-Hong Kong issue card. However the currency charged to the users Apple Pay cannot be in local HKD currency. OCL forces the users to choose another currency which because the default currency for the life of the card. This adds an invisible surcharge over using local currency transitions, 4% or more, which is OCL taking a cut.
This is called forced Dynamic Currency Conversion (DCC) and is a credit card compliance rule violation. Visa, Mastercard and all stipulate that merchants cannot impose any requirements on the cardholder to use a non-local currency. Why OCL is so brazenly breaking these rules, and why Apple is allowing this level of gouging in a major app from a major Apple Pay payment provider is not good at all. As FeliCa Dude says, “Apple should swiftly rebuke this kind of grasping banditry lest it poison their platform.”
If Apple does nothing, I think we’ll have the answer Tim Cook didn’t give at the Congressional hearings. Okaaaay?
A reader pointed out that not only was I wrong, he reported that iOS still uses the PassKit Suica Shinkansen call with Ekinet eTickets. Notification Center throws out the same ‘Shinkansen’ Suica Notification when the user goes through a JR East Shinkansen gate with an eTicket.
This is handy for the user event transaction record even though the Shinkansen transit fare is not recorded: eTickets have nothing to do with Suica balance transactions, they’re along for the ride so to speak. The interesting thing is that the Shinkansen notification does not show when using the JR East ‘Touch and Go’ Shinkansen service which does use the Suica balance. It also does not show when using the JR Central Shinkansen SmartEX/EX Reserve eTickets which are cloud based like Ekinet.
The eTicket side attraction offers some insight into the ‘what stays offline and local, what goes to the cloud’ dilemma JR East (JRE) faces as it closes in on the next generation ‘2 in 1’ Suica architecture due for release in spring 2021. JRE has said many times and in many ways that the future of the Suica platform will combine cloud services with the fast local processing of the FeliCa powered Suica architecture. However, details are few, with different pieces dribbled out in bits like the new Ekinet Shinkansen eTicket service.
What’s the overall vision and goal of next generation Suica which I call Super Suica? There’s a lot of ground to cover to find out so let’s examine things in 2 basic categories: the card architecture (offline and local) and the payment platform (cloud) even though those distinctions are increasingly blurred. Here is my take based on what JRE has announced so far.
Super Suica: the Transit Card
The next generation ‘2 cards in 1’ Suica architecture hosts partner transit cards and services on Suica infrastructure, effectively extending the Suica system to non-JRE transit companies. 2 in 1 partner transit cards gain the benefit of Suica hardware and Mobile Suica infrastructure with considerable cost savings related to plastic card issue and management. The heart of Super Suica remains the offline stored fare. JRE hopes to grow Mobile Suica cloud services as much as possible with the lower cost next generation Super Suica architecture.
Stored Value Update, Region expansion and Commuter Pass Changes Starting with the basics, it’s a no-brainer that Super Suica will raise the current ¥20,000 stored value limit, likely doubling it to ¥40,000. This would put it in line with other eMoney prepaid cards like WAON and nanaco, also similar to the recent Hong Kong Octopus stored value update. The increase would have broad appeal to tourists, business travelers and shoppers everywhere and extend the JR East ‘Touch ‘n Go” ticketless Shinkansen service area.
A long standing hurdle for Super Suica to clear is the transit IC card region limitation. The current transit card architecture assigns cards to a unique areas and the stored value doesn’t work across regions. Transit systems within the same card region such as JR East and PASMO have their fare systems connected so that a user’s transit card can enter a JR East station then exit a PASMO member station with the fare instantly calculated and deducted from the offline card balance.
This region limitation is a real problem for transit users in fringe areas. In order to use an IC transit card they have to exit and re-enter separate transit company gates at specific transfer station points. There is a Japanese word for this: matagaru which means ‘dismounting the saddle’. The only viable options are mag strip commuter passes or paper tickets.
The ‘2 in 1’ Super Suica concept has special meaning for commuter passes. The current Suica only supports 2 basic patterns via a card id commuter pass account number: JR East only lines, and connected commuter passes covering JR East and connecting lines. 2 in 1 Super Suica will support commuter passes on non-JR East lines and bus lines.
Super Suica: the Platform
The primary aim of Super Suica is extending the platform reach with shared infrastructure to rural areas too small to establish their own local transit cards. Pay close attention to the transit cards outside the pink area, with the exception of PiTaPa. These are 2nd tier local area transit cards currently orphaned from eMoney or transit interoperability. There are also ‘off the map’ areas such as Utsunomiya Light Rail and Iwate Transit Co. Ltd. who have announced Super Suica agreements with JRE. These are the initial target areas.
Super Suica enlarges the pink area to include those 2nd tier and off the map cards. Those who sign on join the common interpretability area for transit and eMoney, and also gain access to Mobile Suica hosted Apple Pay Suica, Google Pay Suica and Osaifu Keitai. This is a real boon for smaller areas who, up to now, couldn’t afford to launch their own card operations. I suspect it will be very attractive to all transit card operators who run on shoe string budgets, they can save money by offloading card operations to JRE and get the mobile goodies.
What does Super Suica mean for the major transit cards like ICOCA and TOICA? It depends on what kind of deal JRE offers them. Even if the majors don’t sign on directly I see them getting access to the new Suica card format and Mobile Suica IT assets. At the very least we’ll see something similar to Mobile PASMO: licensed Mobile Suica IT assets rebranded as Mobile ICOCA, Mobile TOICA, etc.
2 in 1 Reward Points and Auto-Charge In addition to the 2 in 1 commuter passes, Super Suica also supports different reward point systems. Users will be able to exchange points for a Suica recharge just like they do now with JRE POINT and Rakuten Pay points. Auto-Charge for 2 in 1 partner branded credit cards will certainly be supported as well. Points and Auto-Charge may seem mundane but they are very important to customers and transit companies, a vital part of luring foot traffic, new businesses and visitors to local areas in an era of shrinking passenger traffic.
Expanding and leveraging the Recharge Backend The ever expanding Mobile Suica recharge backend is a fascinating development mostly ignored by the media even though it’s where the action is. Suica and the other transit cards are a huge green pasture full of cash (less) cows waiting to be milked by card companies and payment platforms. JRE lets them milk Mobile Suica cows for a cut. Up until Apple Pay Suica came along in 2016, JRE was the only recharge backend. As of July 2020 there are 5: JRE, Apple Pay, Google Pay, Mizuho, Rakuten. 2 in 1 partners will have the ability to add their own recharge backends with apps, if they so choose.
Other points to remember: the recharge backend only works on iOS and Android platforms, point rewards can be used for Suica recharge. Currently that only works with JRE POINT and Rakuten Points but this will be extended to the ‘2 in 1’ partner point systems.
MaaS Suica It’s clear that the really big Super Suica changes will be on the cloud side. Transit card eMoney has been a huge success, but Suica has to evolve to remain a viable payment platform in today’s hyper competitive world of mobile payments.
That next step is Suica NFC Tag payments. Think of it as Suica transactions without a reader, where your smartphone is both Suica card and Suica reader and let’s call it MaaS Suica. JRE joined the MaaS alliance in November 2019 closely followed by an December 2019 press release announcing NFC Tag tests with 4 partners: JRE (Suica), DNP (NFC Tags), Sony (FeliCa) and AquaBit Spirals (NFC Tag SmartPlate payments software).
JRE & us (AquaBit Spirals) have announced to conduct technical verification for the use of NFC tags focusing on transportation and ‘payments’, and that the role of Sony is to investigate technical specs as part of promoting a lifestyle through ‘FeliCa’ tech. You may know what we mean😉
AquaBit Spirals CEO Tomohiro Hagiwara
It’s clearly implied by the diagram and by comments from AquaBit Spirals CEO Tomohiro Hagiwara that Suica powers the NFC Tag payments middle section via the cloud. This means the Suica card balance on smartphones works ‘over the cloud’. Suica is unchained from the NFC reader and can be used to pay for any kind of NFC Tag linked service or item.
NFC Tags and App Clips level the playing field with QR One of the ways PayPay and other QR Code players disrupted the Japanese market so quickly was leveraging the low entry point bar of static QR codes combined with mobile smartphone apps. All stores need is an official QR Code sticker. Small merchants are freed from having to invest in POS hardware to go cashless.
The pieces appear to fit very nicely now: the NFC background tag sheet pops-up ‘while the screen is on’, the right code snippets load in for a simple focused task, the user can Sign In with Apple ID if needed, and pay with Apple Pay. Simple, uncluttered action; no apps, no Safari launch. And we have background NFC tag reading on every current iPhone model.
MaaS Suica combined with new technologies like App Clips and background tag reading iPhone has the potential to take the Suica eMoney payment platform to a whole new level. Success depends on how aggressively JRE promotes the service and how they license it to sister transit card operators. It would be great if we got MasS Suica, MaaS ICOCA etc. working seamlessly as a single mobile payment just like transit cards do now.
Based on what JRE has said over the past 2 years in the press and in recent company announcements, it seems we’ll have 3 basic versions of Suica: (1) Hard-wire Suica (what we have now) for major stations and stores, (2)Wireless Suica, a simplified low cost cloud based gate terminals to cover rural stations not currently on the Suica map, (3) MaaS NFC Tag Suica to cover everywhere else.
There will be 2 kinds of Super Suica partners:
Direct 2 in 1 partners host cards on Super Suica with all the benefits of Mobile Suica.
Indirect partners get the new Suica card architecture, New FeliCa OS improvements, Mobile Suica IT assets and wireless Suica gate system technology. The arrangement will be similar Mobile PASMO who licensed Mobile Suica IT assets but run their own cloud service with their own backend mobile recharge, commuter passes and reward points.
If Mobile PASMO is any indication, I think most of the major transit card players will end up as indirect partners. It would be great if Super Suica turned out to be an all encompassing nationwide thing on digital wallet platforms. The truth is that commuter passes, recharge backends, auto-charge and point reward empires are the crown jewels. Transit companies will always want to keep those in-house.
Next generation Super Suica won’t be a slam dunk national transit card that does it all, but it will be start line towards that goal. Think of it as a new foundation of shared infrastructure and services with transit companies working toward a cohesive de facto standard that has lots of mobile potential.
The timing is also good: in these COVID challenged times all transit companies are under enormous pressure to streamline, consolidate and bury old grudges. The current situation will likely drive Super Suica uptake as the payoff is more mobile services with reduced operating costs. Another case of COVID driven ‘unfortunate success’. I remain hopeful that, in the end, we’ll be pleasantly surprised.
Apple Pay Octopus has been in service for a week so I asked for some Apple Watch field impressions on Twitter. Overall, users seem pretty impressed:
I am using it daily and it is really out of this world. I use it on my watch and now I can literally go out for a jog or hike with just wearing the watch.
It works perfectly on my AW so far. But from I’ve heard on LIHKG, there some users facing the difficulties on the express mode. Mostly are requiring passcode when going through the gate.
It’s mostly positive. However there’re times where the reader isn’t sensitive enough and need to linger the watch longer. Also going to work first thing in the morning but forgetting to enter pass code in the apple watch is frustrating since it doesn’t inform you need to unlock.
Been using AW Octopus everyday. Use cases include MTR, tram, ferry, 7-11, eating meals at all sorts of restaurants like Tai Hing, Ki’s Roasted Goose, Pret etc. Octopus on Apple Pay drastically improved HK’s cashless experience. It’s definitely okay for me to go out with only AW. Not even with my phone. Feels really good. The speed of payment is also very remarkable. However, the reader in Tai Hing seems to need an extra second to detect my AW, not sure why. Plus AW users might want to wear it on the right wrist, which makes passing MTR gates easier.
Using it everywhere. All good and same speed as physical card, expect bus and some small shops were like a heartbeat slower. Also twice there was no “ping” confirmation sound. Tried AW on my right for mtr, its only good for that, imo left is more comfy for other occasions…
… after so many years of waiting, finally an apple pay suica experience in HK.
You can follow the Twitter thread here. I have noticed a few small gate lag hiccups on my Apple Watch Suica since upgrading to watchOS 6.2.5/6.2.6. The lag is especially noticeable if a workout is in progress. The passcode request at the gate could indicate that Express Transit is deactivated somewhere along the way, either by a loose band activating the wrist detector into thinking Apple Watch was taken off the wrist, or it could be something else.
My Apple Watch insisted that I create a 6 digit passcode recently and disabled the 4 digit passcode option for a few days. Who knows, the passcode requests that some HK users are seeing could be a watchOS bug or an Octopus reader side issue that can be addressed with a firmware update.
Apple Watch is still prone to OS version performance issues that disappeared from iPhone with A12 Bionic and Express Transit with power reserve. Apple Pay transactions on A12 Bionic and later bypass most of the iOS layer and are directly handled in the A12/A13 Bionic Secure Enclave and Secure Element. It makes a big performance difference for Suica and Octopus.
Hopefully the next watchOS update will improve Suica and Octopus performance. Better yet let’s hope that Apple Watch 6 introduces a Apple S6 chip with Express Transit with power reserve. That would solve the watchOS version NFC performance issues for good, just like it did for iPhone.
As of June 2020, Express Transit can be used with 8 transit networks: Japan (Suica and compatible nationwide), China (Beijing, Shanghai and China T-Union), Hong Kong (Octopus), United Kingdom (Transport for London), New York City (MTA OMNY compatible stations and buses) and Portland (HOP). Here are some Express Transit card tips and other observations for Apple Pay Wallet users that I have learned from years of daily Express Transit Suica use.
1) Face ID Express Transit use with face masks and tight pants
The most important thing to remember is that Express Transit only works while Face ID/Touch ID is ‘On’, when Face ID/Touch ID is disabled Express Transit is ‘off’.
Express Transit doesn’t care if you are wearing a face mask. However it is easy to disable Face ID iPhone without realizing it, resulting in a rude passcode request at the transit gate. Face ID face mask users need to be extra careful as five misreads disable Face ID and Express Transit. The passcode is required to re-enable Express Transit.
Users can mitigate some of this by turning off Raise to Wake in option in Settings > Display & Brightness. If you still have problems the last resort is turning off Face ID for unlocking iPhone, be sure leave it on for Apple Pay.
All iPhone users, both Face ID and Touch ID, need to be aware when putting iPhone in tight pants pocket: pressure on the side buttons initiates shutdown/SOS mode which disables Face/Touch ID and Express Transit. This is worse with a case because iPhone in a case is thicker and tighter in pant pockets, with more pressure on the side buttons.
2) Apple Watch Express Transit works for 10 minutes off the wrist
Suica and Octopus on Apple Watch are the ‘killer’ watch app that quickly becomes second nature. Its nice in colder months because Apple Watch works at the gate under layers of clothes, it beats digging iPhone out of a pocket. The biggest complaint I hear is from left wrist Apple Watch users. Most transit gate readers are on the right side so the user has to reach over to the reader. This will be a bigger pain with new JR East transit gates that place a slated reader on the right side. Some commuters migrate Apple Watch to the right wrist to deal with it.
One interesting aspect of Apple Watch Express Transit is that it works for 10 minutes off the wrist. This is by design in case the transit card needs servicing by a station attendant. After 10 minutes, Express Transit turns off and requires the passcode to work again.
3) Multiple Express Transit Cards
The addition of EMV Express Transit in iOS 12.3 introduced the concept of having multiple Express Transit cards, one payment credit/debit card for transit use and one native transit card for each transit network (Suica, Octopus, Beijing, Shanghai, HOP, etc). The fine print tells a different story: if you have a China mainland transit card set for Express Transit, all other NFC-A protocol cards (EMV, MIFARE) are turned off.
There’s more to the story not covered in the Apple support doc: China T-Union Express Transit cards are incompatible with all other Express Transit cards. A set of reader images shows the issue. Turning on Express Transit for China T-Union turns off all other cards, both native and EMV payment cards. China T-Union cards are a bit messy in that older card formats like Beijing City Union are migrating to the new spec that does not support plastic card loading for mobile. Shanghai remains with the old spec with plastic card transfer for now but will also likely migrate in the future.
Shenzhen cards are also migrating from the legacy FeliCa (blue and orange) cards to the new China T-Union (red and green) cards. This is probably one immediate reason behind the ‘one at a time’ Express Card issue that Apple will hopefully fix it in a future iOS version. It’s not a problem as most users only use one Express Transit card at a time and can turn them on and off as needed. It’s interesting to developers because it reveals some current architectural limits of iOS 13 Apple Pay.
A reader asked me about using face masks with Express Transit. The great thing about Express Transit with Suica and Octopus is that the user doesn’t need Face ID or Touch ID to use transit or buy stuff. It’s very convenient to have, especially in our face mask era. iOS 13.5 added a small Face ID tweak for easier passcode entry when wearing a face mask. It helps with the basic unlock but for me regular Apple Pay authentication is still a pain.
The reader wanted to know if the iOS 13.5 Face ID tweak affected Express Transit. It does not. You don’t need Face ID to use Apple Pay Express Transit. But Face ID needs to be ‘on’ in order for Express Transit to work and finding the right information on Apple support pages is a little confusing. The reference page you want is If Face ID isn’t working on your iPhone or iPad Pro>If you need to enter your passcode:
The key sentences are outlined in red. Wearing a face mask is not a problem with Express Transit and Face ID turned on. However, “five unsuccessful attempts to match a face,” turns off Face ID and Express Transit. You need to enter your passcode to turn on Face ID and Express Transit again.
Unfortunately turning off Face ID wearing a face mask with five unsuccessful attempts without realizing it is easy to do and trips up a lot of Express Transit users who are not aware of it. That’s why I suggest turning off the ‘Raise to Wake’ option in Settings > Display & Brightness. Doing so reduces the chance of ‘five strikes’ and makes Face ID with face mask life a little easier.