It all connects: JR East QR Eki-Net Tickets


One of the great things about Japanese trains is how seamlessly they connect nationwide. Buy a ticket and travel to your destination anywhere in the country even on a different JR company line. This is the legacy of JNR with ticket office staff that knew everything inside out and got you the best connections at the best price. But even in local regions cross company thru transit is a given. There is a small catch however: you must have a ticket specifically designated for the destination on a different connecting company line. For paper tickets that is.

The great innovation of Suica and the Transit IC standard was that it did away with the need to purchase special connecting tickets. Just tap and go, each company transit gate automatically calculates and deducts the stored fare (SF) from Suica. Another innovation of Suica was IC fare. IC fare is slightly cheaper because it is ticketless, the fare collection is automatic and less expensive to process. The cheaper IC fare is also encouragement to use IC cards instead of paper tickets for local travel. As of FY 2021 JR East says 95% of Tokyo area transit uses Suica/PASMO.

Nevertheless, despite Suica being around 20 years and the Transit IC standard in place for 10, paper mag strip tickets are still with us. Why? A number of reasons but the biggest one being they are essential for long distance interconnected transit. Travelers can get on a local JR West train in the Osaka region, transfer to the Shinkansen and ride to Tokyo, transfer to a JR East local train and ride to their destination with a single purchased set of paper tickets, usually with a discount when purchased far enough in advance. Can’t we already do this with Suica and the like? Yes and no.

Bad JNR Breakup
The 1987 breakup of JNR had some bad repercussions that are still with us today. It came at a crucial point just as the next generation ticketing Suica smart card was in development, delaying deployment for many years. This delay fossilized the JR Group ticketing system to mag-strip paper. Post breakup JR companies developed their own transit IC card systems without larger JR Group integration, limiting coverage to high volume traffic areas where they could recoup transit IC system installation costs. This resulted in large sections of lower traffic rural lines being left off the Suica/Transit IC map with mag-strip paper tickets the only option. I experience this situation whenever I travel from Tokyo to Minobu. Suica only goes to Kofu, but the Minobu line is not wired for Transit IC as the Minobu station signage makes very clear.

The transition from mag-strip paper tickets
When JR East unveiled their next generation transit gate prototype in late 2019 with Suica and QR Code readers but no paper ticket slot, it was clear that closed loop QR ticketing was the transition plan for retiring paper tickets. Mag-strip paper recycling costs are increasing and mechanical paper ticket transit gates are expensive to purchase (said to be 10 million JPY per unit) and maintain. Migrating to QR eliminates these costs…but it will be a long transition. The end of mag-strip paper tickets will only be happen when all JR Group companies, and connecting private transit companies, implement QR that covers all station points paper does now.

Filling the gaps
Despite all appearances, JR Group companies have been busy creating a foundation of new services that fall into basic categories:

Extensions: (1) Closing Transit IC gaps on their respective systems with hard wired stations or readers installed on trains for tap-in/tap-out transit, (2) Extending Transit IC beyond JR Group systems with lower cost cloud based solutions or government subsidized installations for connecting transit operators.
Cross region transit between Suica-TOICA-ICOCA-SUGOCA regions (Atami, Maibara, Shimonoseki, etc.), this has started with through cross region Transit IC commuter passes, the next step is through cross region for regular cards.
Online Reservation and Ticketing: Eki-Net, EX/Odekake-Net that cover eTicketing for Shinkansen, Ticketless reservations for express trains and special seasonal package tickets.
Special Issue: Suica/PASMO for disabled users with discounts that replace paper passes

By company:

JR East
Suica is extending to cover the entire rail network starting in the Tohoku region in March 2023 with a new lower cost cloud based Suica system (aka Super Suica Cloud), Suica is also extending to cover Tohoku region bus companies via the Suica 2 in 1 Region Affiliate Card program that kicked off in 2020. Suica/PASMO for disabled users will also launch

JR West
Has been extending ICOCA with the final extensions coming to the Shimonoseki region in March 2023 along with the Mobile ICOCA launch.

JR Central
Announced TOICA will be coming to all lines and stations “soon”, along with more EX non-Shinkansen ticketing options and EX-MaaS package tours that cover train, hotel, car rentals, etc.

In short QR will be a mobile only default replacement for paper while JR East-Central-West are extending Suica-ICOCA-TOICA to be the default mobile + physical card mode for local travel. This covers all of Honshu but we still don’t know what Transit IC expansion + QR plans there are for the financially weaker JR Group companies: JR Hokkaido, JR Kyushu, JR Shikoku.

The Eki-Net QR Super Suica Cloud Connection
One of the little noticed key aspects of the JR East Eki-Net QR Ticket announcement is the initial service launch area and time: Tohoku. This is the same area where the Cloud Suica extension is launching in March 2023. Eki-Net QR starts here over a year later, between October 2024~March 2025. This new Suica system has a few tricks up the sleeve that give a clue how Cloud Suica and Eki-Net QR complement each other. Let’s start with the new Suica/PASMO cards for disabled users launching in, yet again, March 2023. Fare discounts for disabled users are very complex as they are certified by the resident local ward or city. Up until now paper passbooks were manually examined at entrance or exit to verify the fare discount.

Suica/PASMO disability fare cards are the first time the discount is validated by the Suica system. Look very carefully at the valid use regions because Suica 2 in 1 Region Affiliate cards were designed to support special fares on non-JR East transit and region affiliates will support Suica/PASMO disability cards when they launch. As both Cloud Suica and QR will use the same cloud linked transit gates, it’s a given they will also share the same backend validation system.

The new cloud based gate validation system going online in March 2023 (on right) will certainly validate both Suica and QR

Where does Eki-Net QR fare fit?
The online reservation and ticketing apps we use now (Eki-Net, EX, etc.) will be the same apps people will use to buy and display QR Code tickets. We already use QR Codes to pickup paper tickets from a station kiosk, displaying the same QR Code to go through a gate is the next natural step. The essential question is which fare tier QR tickets reside in. Currently JR East has 2 basic fare tiers:

  • eTicket and Ticketless (Suica / Transit IC cards)
    Less expensive fare tier for regular local transit, Eki-Net Shinkansen eTickets with bigger discounts, Eki-Net Ticketless Express Train Reservations with bigger discounts
  • Paper Tickets
    More expensive fare tier for regular transit, cash purchase only for local travel, credit card purchase for express train and Shinkansen tickets, seasonal tickets, special package tours, and so on.

The logical progression is that Eki-Net QR tickets simply replace the paper ticket tier. There’s a huge variety of one-off specials and package tours that don’t fit well in the Suica eTicket/Ticketless box that would be ideal for QR treatment. We shall see but I suspect JR will want to keep the tier differences in place because NFC Suica/Transit IC ticketing works without a network connection, QR Code ticketing does not. And we all know that station network environments are the worst.

Eki-Net already issues QR Codes for picking up paper tickets, this is what Eki-Net QR Tickets will replace.

New Transit Gate Design
Last but not least we have QR reader equipped transit gates that JR East will start installing in stations starting December 2022. Like the paper to QR transition, installation will see a gradual replacement of older end-of-life combo Suica + paper transit gates with new Suica+QR+paper transit gates. We may also see installment of the earlier Suica + QR prototype gates that JR East tested in 2020.

One aspect of both designs is the QR reader is placed way in front of the Suica reader, which is placed as far back as possible. This peculiar design has an important function of preventing ‘Suica Express Transit’ card clash when a user is going though the gate displaying a QR Code. JR East doesn’t want an extraneous Suica card read/write to clash with a QR read that sets Suica to ‘start transit’ mode. I’m sure the gates will automatically turn off the blue Suica reader when it detects a QR Code, but keeping the readers far apart is a good thing. We don’t want any MTA OMNY-like launch nonsense.

Looking Ahead
This is only a start. JR East has only announced the broad outlines of their paper to QR transition, the real transition will kickoff when other JR Group companies announce their plans which they have not done so far. One thing is for sure, the trusty old JRN built mag-strip paper ticketing system is finally getting a reboot for the cloud based mobile ticketing age.

Google Pixel Watch Suica…with limits

Now that Google Pixel Watch Suica is here, the obvious questions are: is it global NFC or is it limited to JP models, is Suica the only JP payment service? EMV is there of course, PASMO joined Google Pay recently with clear signs that Wear OS support is also in the works. At the very least we can expect PASMO in a future Pixel Watch update, but so far there is no mention of iD, QUICPay and other Google Pay FeliCa payment services on Wear OS.

On the global NFC side, things turned out exactly as predicted (copied below from May 2022). Pixel 7 Mobile FeliCa support is the same old ‘cheap instead of deep‘ story: all models have the same NFC hardware with Mobile FeliCa loaded, but Google only fully activates it for JP models, in other words they continue to kneecap NFC on non-JP Pixel phones.

Pixel Watch lists FeliCa on the spec page for all models and regions, it is global NFC…but is kneecapped in the initial Wear OS version. The Mobile FeliCa Cloud (aka Mobile FeliCa Lite) powered backend is the same used by Garmin and Fitbit that delivers a geolocation locked subset of Mobile Suica services; you get the stored fare balance (SF) functions and little else. All worldwide models support Suica but it can only be added on registered devices physically located in Japan, that is to say FeliCa support is limited by location not the device model. While not ideal, it does provide some highly useful digital payment functionality for inbound visitors with those devices.

Instead of limiting Suica by geolocation that Garmin and (Google owned) Fitbit do, Google kneecapped Pixel Watch Suica for some unknown reason, limiting Suica to JP models as Pixel Watch help documentation makes clear. It looks like a major fuckup for an expensive smart device from a leading tech company that can and should work the same everywhere.

Fortunately Google promises a Wear OS update that removes the NFC kneecap allowing all Pixel Watch users to add Suica when in Japan, just like Garmin and Fitbit. We shall see if Google keeps their promise. Pixel Watch Suica has other limitations similar to Garmin and Fitbit: no Suica commuter plans, no Suica plastic card transfers, no Suica Green Car Seats, no Suica Day Passes, etc, but you can register Pixel Watch Suica for extra services: JRE POINT, Eki-Net, Touch and Go Shinkansen.

In short, that state of Google Pay on Pixel 7•Pixel Watch is not the Apple Pay-like overhaul for robust native global NFC across the entire Pixel family many were hoping for. If Google delivers on their promise to remove the Pixel Watch NFC kneecap, all those users can at least use Suica. It does raise the question I asked back in May, if all Pixel Watches do Suica, why not Pixel 7? Pixel 7 is perfectly capable but Google is keeping that NFC kneecap in place. And there is the glaring Google Pay gap between Pixel 7 JP models which support all contactless JP payments from Suica to iD to Edy, while Pixel Watch only supports one: Suica.

Meanwhile Apple Watch remains the only full featured global NFC Suica wearable because Apple took the time and effort to do Apple Pay right…what else is new?

I’ll update this post with Pixel FeliCa details as they become available.


Will Pixel Watch finally deliver global NFC Google Pay? (May 2022)
Ever since Apple made global NFC standard on all iPhone and Apple Watch models in 2017, global NFC has become a litmus test of ultimate Apple-like user friendliness. When inbound devices can add Suica, it’s not only cool, but also necessary to get around. Garmin and Fitbit wearables do the global NFC thing, but Android remains stubbornly ‘buy a Japanese smartphone to do the Suica FeliCa thing.’

In the global NFC sweepstakes then, every Google Pixel release cycle is a game of ‘will they or won’t they’ finally deliver global NFC. Actually Pixel is already global NFC with Mobile FeliCa ready to go, but Google disables it on all non-Japanese Pixel models.

Which brings us to Pixel Watch which got a sneak peek at Google I/O 2022. The buzz on Japanese Twitter was basically: I want one, but not if it does’t have Suica support. Fair enough, I bet a lot of people are thinking that and not only in Japan. After all, Hong Kong users would love having a Pixel Watch that supports Octopus.

The good news is that Suica appears to be coming to Google Pay for Wear OS. Various Suica string have appeared in recent Google Pay APKs. This is expected: it would certainly be very awkward if Pixel Watch doesn’t support Suica when Fitbit devices do.

But this begs a bigger question. Wouldn’t it be extremely awkward if Pixel 7 doesn’t support Suica out of the box when Pixel Watch does? I would say so. But then again one hopes The Android Ready SE Alliance is working to fix all that, and do away with the limitations of Android HCE nonsense once and for all.

iOS 16 Wallet: expanding the Apple Pay experience, aka Suica auto-charge for the rest of us

iOS 15 added big new features to Wallet, expanding digital keys from cars to include home, office and hotels and ID in Wallet driver licenses for the first time. There were smaller but important UI changes too. A new add card screen offered new categories making is easy to add transit cards regardless of the device region and quickly re-add previous Wallet items from iCloud. iOS 15 was all about Wallet to the extent that Apple now advertises it as a separate thing from Apple Pay with a separate web page, and even referred to Apple Pay as “one of the most important areas of Wallet” in the WWDC keynote. Very interesting.

iOS 16 moves the focus back to Apple Pay and making digital payments more useful, practical and universal. The WWDC22 Keynote announced Apple Pay Later, in-app ID card verification and key sharing. Apple Pay Later is one aspect of several new Apple Pay functions unveiled in the What’s new in Apple Pay and Wallet session.

Multi-merchant payments: In our online world we can never be sure how many sub-merchants are involved when we order something and how our card information is shared. In multi-merchant Apple Pay, multiple payment tokens are issued for each merchant in the same transaction, preserving user privacy, with the iOS 16 Apple Pay paysheet showing a breakdown of each sub-merchant charge. This feature works mostly on the backend, but showcases how smartly the Apple Pay Wallet team design features to ‘just work’ securely for merchants and customers.

Automatic Payments
My favorite iOS 16 feature as it addresses a lot of interesting use cases, much more than just Apple Pay Later installments which fall under:

Reoccurring payments, which include things like installments and subscriptions, basically any regularly scheduled payment. With the recent Starbucks Japan price increases, I decided to sign up for the new JR East Beck’s Coffee Shop subscription plan. Up to 3 cups a day for ¥2,800 a month. A pretty good deal for commuters like me. The Beck’s subscription service is subcontracted out to an interesting online business venture company called Favy that uses Sign in with Apple to create an account. Payment however is manual credit card entry with the onerous, ubiquitous 3D Secure sign-in. Pass issue and serving size selection (M=¥50, L=¥100 extra) is done in Safari. It works well enough, but canceling or getting payment details is a real Safari expedition. It would be a much better, and faster, customer experience doing it all in Apple Pay.

Automatic Reload: this is the real money feature for me because it plays on the classic snag of using Apple Pay Suica…recharge. All pre-paid cards are a catch-22. Japanese users love them because they like the “I know how much money I’m adding to my card” aspect of manual recharge, but there’s the inevitable, you know you forgot about it, bing-bong ‘please recharge’ transit gate alarm when Suica balance is short.

JR East offers Suica Auto-Charge (auto-reload) as a feature of their VIEW card. The auto-charge option works great with Apple Pay Suica but like all transit card auto-charge, it is tethered to the transit gate NFC system. This means the users gets instant, seamless auto-charge but only on the operator’s transit gates. Suica auto-charge does not work outside of the Suica and PASMO transit gates, not at store terminals, not in other transit card regions like JR West ICOCA. This limitation is a big customer complaint, I and many others would love Apple Pay Suica auto-charge to work everywhere.

Apple Pay automatic reload takes care of this problem very nicely. Suica would recharge anywhere because the card balance ‘trigger’ and reload process is done via Apple Pay instead of JR East transit gates and the Suica system. JR East could keep auto-charge exclusive to their VIEW cards as they do now or easily, selectively expand it. Either way they would greatly increase the usefulness of VIEW and Suica by supporting the new Apple Pay automatic reload feature. The possibilities are are pretty exciting.

Order tracking
Another very useful feature I think people will love using. The addition of QR/barcodes in the Apple Pay sheet is a first and will greatly shorten the order pickup~delivery process. The best use case of Apple Pay and bar codes that I can think of.

ID verification in apps
This is where ID in Wallet gets real. Wallet app has TSA airport checkpoint verification built-in but that’s not going to help all the government issuing agencies, not to mention software developers, around the world who want to implement digital ID verification to unlock various digital services.

JR East for example has centered their whole Super Suica MaaS Cloud initiative around ID PORT and the ability to match various region or age based services (discounts, special fares, etc.). In other words JR East and their sub-merchant or local government agency want to know where I live and how old I am. This is all provided on the Japanese government My Number digital identity card launching later this year on Android, and Apple Wallet later on. But I don’t want my personal details going everywhere. If the MaaS campaign app or website only needs to know that I live in Tokyo and am over 60, that’s the only info I want to give them. This is what the new PassKit ID request APIs in iOS 16 do: give apps only the information they need to perform a verification for a service and nothing more.

Key sharing
Nothing big here, but it does address one iOS 15 Wallet shortcoming for home, hotel keys which that could not be shared and expanded share options beyond mail and messages. I’m doubtful Apple includes office keys in the bargain but the fine print reads: available on participating car brands and access properties. We’ll find out when iOS 16 ships.

And then there’s Tap to Pay on iPhone. It’s really not an Apple Pay function to me because it turns iPhone into a very handy and portable NFC payment terminal, but it makes sense branding wise. Just say Apple Pay for making…and accepting payments. Anywhere the merchant has their payment provider POS app and a network connection, they are ready to go. This is big. Apple has lined up an impressive number payment providers in a very short time who are happy to leave all the hardware certification and secure element management to Apple and focus on software. I can practically feel the intense interest from Japan where local payment providers would love to leverage the global NFC capable iPhone for seamless EMV and FeliCa payment services. It could be an interesting Apple Pay year.

The Weekly

2022-05-14 Early Rainy Season

Will Pixel Watch finally deliver global NFC Google Pay?
Ever since Apple made global NFC standard on all iPhone and Apple Watch models in 2017, global NFC has become a litmus test of ultimate Apple-like user friendliness. When inbound devices can add Suica, it’s not only cool, but also necessary to get around. Garmin and Fitbit wearables do the global NFC thing, but Android remains stubbornly ‘buy a Japanese smartphone to do the Suica FeliCa thing.’

In the global NFC sweepstakes then, every Google Pixel release cycle is a game of ‘will they or won’t they’ finally deliver global NFC. Actually Pixel is already global NFC with Mobile FeliCa ready to go, but Google disables it on all non-Japanese Pixel models.

Which brings us to Pixel Watch which got a sneak peek at Google I/O 2022. The buzz on Japanese Twitter was basically: I want one, but not if it does’t have Suica support. Fair enough, I bet a lot of people are thinking that and not only in Japan. After all, Hong Kong users would love having a Pixel Watch that supports Octopus.

The good news is that Suica appears to be coming to Google Pay for Wear OS. Various Suica string have appeared in recent Google Pay APKs. This is expected: it would certainly be very awkward if Pixel Watch doesn’t support Suica when Fitbit devices do.

But this begs a bigger question. Wouldn’t it be extremely awkward if Pixel 7 doesn’t support Suica out of the box when Pixel Watch does? I would say so. But then again one hopes The Android Ready SE Alliance is working to fix all that, and do away with Android HCE nonsense once and for all.


Digital My Number on track for Android 2022 launch, Apple Wallet due in 2023
The Ministry of Internal Affairs and Communications (MIC) digital version of My Number Card (Individual Number Card) is on track to launch in 2022 (October-ish?). The latest MIC Work Group PDF document has a full outline of the digital My Number system and the various services the Japanese government plans to link with it. In late 2020 MIC said they were ‘in discussions’ with Apple to bring digital My Number to Wallet and this has not changed. Nikkei reporter Mayumi Hirosawa saw a chance to grab some eyeballs and published, The My Number iPhone Wall, a typical Nikkei ‘article’ of lazy, subjective, puerile observations angled as big bad Apple, but nothing new.

Meanwhile Yasuhiro Koyama’s online article on Keitai Watch is far more interesting and informative. MIC official Takashi Uekariya, the goto My Number digital guy, says the MIC and Apple are ‘working hard’ to bring digital My Number to Apple Pay Wallet, and that because Apple locks down new iOS features far in advance, timing wise it looks like iOS 17 in fall 2023 is the likely target for My Number on Apple Wallet. It would be nice though if Apple could surprise us later on in the iOS 16 release cycle, always good to raise the bar and deliver above expectations.

Looking at the larger picture, MIC documentation clearly states that My Number digital card requires a GlobalPlatform embedded Secure Element (GPSE) device, and that except for a small amount of SIM Free Android junk, most smartphones sold in Japan (both Apple and Android) are GPSE certified. An interesting sidelight is that ‘FeliCa chip’ Osaifu Keitai Android devices will support My Number NFC-B transactions. Going forward that means nobody in Japan will buy a device without a GPSE that doesn’t support My Number digital card and the associated banking services that will link to it. Kiss HCE goodbye.


The JR East paper ticket booklet replacement problem has a solution: Suica 2 in 1 transit points
It might seem like a great idea for JR East to migrate the legacy paper ticket bundle (the good old buy 10 and get one free) to Suica…but there’s this little problem of JRE POINT. Repeat Point Service has the same basic concept, 10 trips on the same route in the same month earn you a free trip in JRE POINT. Unfortunately, setting up a JRE POINT account is a pain in the ass, and getting the points back into Suica balance is a huge pain in the ass. For Mobile Suica there’s JRE POINT app + Suica app + Suica Pocket. For plastic Suica there’s JRE POINT app + a visit to the local station kiosk. It’s way beyond the ability of elderly transit users who just want to save on expenses.

Suica 2 in 1 Region Affiliate cards are a much better deal because they have transit points built in. No registration, no setup, just use the transit card and the system does everything for you. Automatically earned points are turned around and automatically used for paying fare. Simple, useful incentive: all one does is use the card for transit and receives a discount in return. This is the way it should be. JR East would be smart if they implemented a similar automatic transit point feature for Tokyo region Suica. JRE POINT is fine for larger more complex integration such shopping and Eki-Net ticket purchase, but integrated, invisible transit points for discounted regular transit would fill a big post-Covid need. I guarantee people would start riding the rails again after the long pandemic pause.

Tight pants and other Face ID Express Transit fuckups

Express Transit is the best and most natural way of using Apple Pay. It first came to iPhone with Mobile Suica in 2016, expanding incrementally until finally going wide with iOS 15 Wallet. Suica has been around so long in Tokyo that younger generations don’t know anything else, it’s ubiquitous. Used global NFC iPhones and Osaifu Keitai are ubiquitous too so there are a lot more people using Mobile Suica, and complaining about it.

Mobile Suica complaints aren’t a bad thing. All those bad Suica App reviews on the App store and complaints on Twitter mean that people use Mobile Suica enough to download Suica App, register an account, use it, then go online and complain. It’s a gold mine of information, invaluable feedback telling us what trips users up at transit gates, a user base with 15 years of mobile transit experience. Any transit operator looking to implement good mobile transit service would greatly benefit from studying strengths and weaknesses of Mobile Suica, the worlds largest, oldest and most widely used mobile transit card service. Unfortunately nobody bothers to do so.

Tight pants + face masks = Face ID fuckups
As always, most Apple Pay Suica problems boil down to Face ID issues that disable Express Transit. Mobile Suica support even has a dedicated help post it puts out regularly. Face/Touch ID and Express Transit are joined at the hip. When Face/Touch ID is disabled, Express Transit is also disabled, a passcode is required to turn them on again. From the iOS 15 user guide: you must always enter your passcode to unlock your iPhone under the following conditions:

  1. You turn on or restart your iPhone.
  2. You haven’t unlocked your iPhone for more than 48 hours.
  3. You haven’t unlocked your iPhone with the passcode in the last 6.5 days, and you haven’t unlocked it with Face ID or Touch ID in the last 4 hours.
  4. Your iPhone receives a remote lock command.
  5. There are five unsuccessful attempts to unlock your iPhone with Face ID or Touch ID.
  6. An attempt to use Emergency SOS is initiated.
  7. An attempt to view your Medical ID is initiated.

You might think a passcode unlock is always the same, however there are surprisingly different Express Transit results at the gate show in the following video clips.

  • The first video shows Express Transit in normal action when Face ID (or Touch ID) and Express Transit mode are on. This is exactly what Suica users expect at transit gates and store readers. When it doesn’t work like this every single time, they complain.
    The second video shows a passcode request after restarting iPhone (#1), not something that would happen in real world use but I wanted to show the different kinds of passcode requests.
  • The third video is the most common one: the Apple Pay screen appears with a passcode request (#5-five failed Face ID attempts when wearing a face mask), this is exacerbated by Face ID Raise to Wake which is why I recommend that Face ID users turn it off when wearing face masks. There is a similar but separate issue when a user inadvertently pushes the side buttons (#6-emergency SOS • iPhone shut down), this happens more than you might think because side buttons are easily pressed when iPhone is in a tight pants pocket, especially when iPhone is in a case which is pretty much everybody.
  • The last video shows manual Apple Pay card selection and authentication when an Express Transit is not set, this is also how Apple Pay works on open loop transit systems without Express Transit support such as Sydney’s Opal.

An interesting side note about Japanese transit gate reader design UI. The blue light NFC reader hit area not only makes a great big visual target, it tells us the gate is ‘ready and waiting’. Notice how the blue light goes off when the reader is busy with a card transaction, then blinks on again ready and waiting for the next card. Watch the above videos carefully and you’ll notice the blue reader light stays lit with every false read attempt. Only when the correct card is brought up does it blink off and complete the transaction. When there’s a real problem the blue light changes to red.

This is simple, clever and user friendly design as your eyes are naturally focused where your hand is but you don’t see the design anywhere else except the new OMNY system readers. Copying the Japanese gate reader UI design is a smart move by Cubic Transportation Systems and MTA but their LED screen NFC hit area combo design appears to be somewhat fragile. The green ‘GO’ might seem like a nice touch but I suspect it subliminally makes a use wait for it. More feedback isn’t always better. Every millisecond wasted at the transit gate is a bad design choice.


Fixing Face ID
iPhone users in America only became aware of Face ID shortcomings thanks to COVID face mask mandates. Yes Virginia, Face ID sucks with face masks and Express Transit users in New York and London came face to face with issue #5: five successful Face ID attempts disables Face ID and Express Transit. It got so bad that MTA pleaded with Apple to ‘fix Face ID’. Apple dribbled out some Face ID “fixes” that didn’t fix very much.

iOS 13.5 introduced a Face ID with face mask passcode popup tweak that didn’t make passcode entry any easier and certainly didn’t fix Face ID use with a face mask. People quickly forgot about it.

iOS 14.5 introduced Unlock iPhone with Apple Watch that was widely ballyhooed by tech bloggers but real world use was a different story:

I find it fails me too often on the daily commute and in stores, usually at the very moment I need to launch dPOINT or dPay apps at checkout. I also get the feeling that Apple Watch battery life takes a hit too… If it works for you that’s great, but the Unlock with Apple Watch end user experience will be all over the place.

Also telling was that online Face ID/Express Transit complaints continued to grow despite the iOS 14.5 feature. Unlock with Apple Watch is a one trick pony, it unlocks a Face ID iPhone when a mask is detected, nothing more, no Apple Pay, no Face ID fix.

iOS 15.4 introduced Face ID with a mask for iPhone 12 and later. This is the first true fix for using Face ID with face masks, finally doing all the work Face ID does from unlocking iPhone to authenticating Apple Pay and apps. It’s not perfect as it doesn’t fix Face ID for earlier iPhone X-XS-11 models, and there are trade offs as it reduces Face ID security for the convenience of keeping your face mask on. In my experience Face ID with a mask on iPhone 13 Pro is certainly an improvement but slower and less successful than using Face ID without a mask. Face ID with a mask is also somewhat quirky. It doesn’t like strong backlighting, some users report frequent ‘look down’ requests depending on the their type of face and glasses.

Now that Apple has a focused Face ID with face mask roadmap that restores the Face ID Apple Pay experience, we can ignore all that mushy ridiculous Touch ID + Face ID dual biometric iPhone talk. Expect Apple to focus on improving Face ID with a mask performance on legacy Face ID on iPhone 12 and 13 in future iOS updates and delivering phenomenally better Face ID technology in future iPhones.