Final frontiers: How Suica 2.0 will solve the IC fare region barrier problem and much more

The Suica cross region problem, no thru transit going from the Suica area to the TOICA area for example, is a well known and criticized shortcoming of the Transit IC system. There has been some recent progress with cross region thru transit commuter passes but barriers remain for regular Suica use, a headache for both local residents and longer distance travelers. Despite all the fancy technology, the cheapest cross region thru transit fare choice is paper tickets.

The entire Suica/PASMO service region is huge but covers less than half of the entire JR East rail network

A lesser known Suica barrier remains on the JR East network: Suica service region gaps. Currently there are 3 Suica regions: Tokyo, Sendai and Niigata. There are also some curious gaps between them illustrated below:

Fortunately this is all about to change for the better.

Filling the Suica gaps
In 2019 JR East CEO Yuji Fukusawa said the company planned to have 100% Suica deployment by March 2022 but that didn’t happen. Why? Transit use killing COVID, the resulting red ink and redeployed resources are a big reason of course, but system development snags certainly contributed to the missed deadline. There was also a shift from a narrow focus of a lower cost Suica system to a wider focus of Suica 2 in 1, Cloud Suica and a cloud based central fare processing system. JR East’s Suica vision is evolving to a wider, transit service platform encompassing a range of technologies, with FeliCa as one component of a larger whole and flexible new system.

In October 2022 JR Central announced that TOICA is expanding to all JR Central lines and stations. The pressure is now on JR East to complete their delayed Suica rollout to all stations first. But there is something else: it’s an open secret that JR East hosts the TOICA system. JR Central would not make such a big TOICA commitment publicly unless JR East had a new system in place to facilitate the expansion. This new system, which I call Suica 2.0, starts operation on May 27 in the Tohoku region.

The launch brings Suica to 45 stations in the Akita, Aomori and Morioka regions but only 9 of these are fully automatic transit gate installations similar to what you find in Tokyo area stations (the same new QR equipped gates shown in the press announcement are installed in Yoyogi station). The rest, 36 in all, are Suica 2.0 validators. Performance is an obvious concern. Suica users are accustomed to the fastest transit gate fare processing speeds on the planet. Will Suica 2.0 performance satisfy an Suica 1.0 experienced customer base with high expectations? To understand how Suica 1.0 fare gates achieve speedy performance apart from FeliCa technology, we need to examine why Suica regions exist and how they relate to transit gate performance.


Suica stands for “Super Urban Intelligent CArd” (but there is also ‘IC’ in the name for integrated chip) and was designed for heavily used urban transit as a smart card recreation of visually inspected paper commuter passes. JNR (pre JR East) researchers wanted to eliminate the time it took urban commuters to pull their magnetic commuter pass out of a wallet or case and feed it into the ticket gate slot. This clogged up major station gates at rush hour. The researchers also wanted a centrally processed card system but the networks and processing power of that time could not deal with the rush hour traffic volume. So the Suica architecture was built around locally transit gate processed stored fare (SF) balance from the card. Instead of centrally processed payments, fares are processed at the station level and synced with the central server, said to be about 6 times a day.

Transit gates have very little memory, most of it dedicated to their main task of local processing Suica fare at the exit point. Low overhead is a necessity. They can’t hold massive fare tables, hot card lists, dead card lists and so on. Only the bare minimum information required to do the local processing job is periodically synced with the central server. Limiting fare processing to specific heavy use regions is a necessary strategy in keeping the local fare processing overhead low and speedy. This is why a Tokyo Suica/PASMO region transit exit gate only processes the fare from a Suica or PASMO (or any Transit IC card) that started the journey in the same region. It’s also the reason why Transit IC cards are generally limited to 200 km point to point trips in their respective local regions, though there are some interesting loopholes.

It’s the same situation writ large with different transit IC card regions. Border stations like Atami (Suica and TOICA) have 2 sets of exit gates: one for travelers from the Suica region, one for travelers from the TOICA region. Suica/TOICA cross region thru transit is limited to special cross region commuter passes and those are limited to specific cross region stations, again to keep the local processing overhead low.

It’s important to note however that IC coverage extensions to border stations with 2 sets of different gates and cross region commuter passes, are very recent 2021 developments. This is the JR Group companies laying the foundation to remove IC transit barriers in the near future. Because Suica 2.0 can process any and all Transit IC fare configurations, transit gate memory limits for local processing are no longer a concern. The barriers will come down when gate hardware•firmware is updated and Suica 2.0 cloud servers are in place.


Suica 1.0 local processing vs Suica 2.0 cloud processing
But transit gate performance is a concern. Does this mean that with all Suica fare processing migrating to the cloud users can kiss the good old speedy Suica gate experience goodbye? JR East says no. In fact they say Suica will get even faster with central server processing. Really? Recent comments from JR East suggest a 10ms network overhead. Suica 1.0 is rated at 200ms for fare processing though in reality the performance feels faster thanks to the large NFC RF hit area of Suica gate readers.

Conceptually, Suica 2.0 is simply going back to what the creators of Suica originally envisioned: centralized fare processing. Specifically the Suica fare processing hockey puck is moving from the station level to centralized cloud servers. The Suica card itself is exactly the same as it is now, the transit gates still handle all mutual authentication read~write functions. Hopefully Suica 2.0 performance will be just like it is now:

The original aims of Cloud Suica with lower costs and flexibility are still there, the JR East Suica 2.0 press release builds on those with emphasis on a distributed server processing system for both Suica service expansion (more stations and no region barriers) and service functions (all kinds of cloud linked services). Let’s examine the new kinds of services JR East is promising to deliver with Suica 2.0.

① Barrier Free Suica transit with no more region gaps. A main goal of Suica 2.0 and bigger than it might seem. Eki-Net Shinkansen eTickets are already ‘barrier free’ with Suica, through clever use of Shinkansen transit gates, but Ticketless Limited Express trains are stuck with Suica barriers such as the Tokyo to Sendai Hitachi and Tokiwa Limited Express trains. Suica users have long complained that service gaps forces them to travel with paper tickets, or they are forced to pay in cash at the exit gate because they tapped in with Suica in Tokyo and forgot the Suica barriers. This problem, and many more barrier Suica gap issues will be eliminated.

② Automated Fare Discounts Part 1: Commute Plan Lite. This is similar to the recently launched Off-Peak Commuter Passes, think of it as short term ‘commute plan lite’ with tons of options. You buy a discounted fare option for certain routes, use times or frequency and it’s automatically linked with your Suica. And unlike the current Suica App method, the items are added in the cloud, not written and stored on the card itself.

③ Automated Fare Discounts Part 2: Fare Discount Gift Coupons. In a similar vein, fare discount reward coupons for store purchases with Suica can be automatically gifted with a tap at the payment terminal. Kinda like the old free parking ticket with store purchase gimmick only far more useful.

④ Linked MaaS services. JR East has been experimenting with MaaS programs like RingoPass but linking MaaS services with Suica 1.0 is a real pain. Suica 2.0 should make bundling much easier, it’s also an opportunity to clean up the current mess of apps.

Reality check and missing pieces
Glossy JR East press releases are one thing but reading between the lines of the Suica Service Roadmap there are hints of missing pieces. Suica 2.0 is all about eliminating physical transit barriers but in the mobile app era there are lots of software barriers that need to be addressed too. Right now JR East online services are hosted in a bunch of apps that don’t fit together very well. It’s a maze of walled gardens: lots of service apps each with different accounts and login, making them work together is a real pain. The real problem is there is no one app to see and manage all the services and tickets attached or linked to your Suica.

A few things need to happen to make Suica 2.0 truly useful.

  • My JR East ID 2.0
  • Cloud savvy Suica App with plug-in services
    • The current version of Suica App lives a double life: one half pulls things off the Mobile Suica cloud, one half does local housekeeping attaching Commute Plans, Green Car Seat Tickets and recharges to Suica card. Meanwhile Shinkansen eTickets, MaaS and other online services live in different apps with different accounts IDs. Wouldn’t it be nice to have all these services living in one cloud savvy Suica App that shows and manages everything attached to your Suica? Absolutely yes please.
  • Local Processing Fail-Safe?
    • We all know that cloud and mobile services fail. Stuff happens. Safe railroad operation requires fail-safe design. Japanese IT journalists like to pooh-pooh FeliCa and Suica reliability, heaping praise on how ‘fail-safe’ the Transit for London open loop Oyster system is. But London transit doesn’t have to deal with major earthquakes, tsunami, typhoons, torrential rain and flooding, train communication cable arsonists, communication cable damaging trackside fire disasters, not to mention sarin gas and cable cutting terrorists. Japanese tend to take safety and security for granted but these infrastructure risks are very real. They have all happened. Suica 2.0 will be a highly centralized system, the higher the centralization, the higher the associated risks when it fails.

      Does Suica 2.0 have a fail-safe backup? Here’s a possible, and from emerging details, likely scenario. We all know programmers don’t like using a new API for mission-critical programs unless they have to. They like to stick with what they already have for compatibility with a smooth gradual transition strategy to the new API. Same for Suica 2.0. Automatic Suica transit gates could be upgraded with both the Suica 1.0 ‘Suica Region local processing API’ and the new Suica 2.0 ‘Region-Free central processing API’. If something goes wrong with the Suica 2.0 central servers, the exit gates switch to reliable local processing Suica 1.0 API mode to keep passengers moving with station level fare processing or perhaps regional level fare processing depending on the JR East distributed server setup. Long story short, If this backup is not in place we can expect this to happen.

Suica 2.0 rollout and the QR Eki-Net Connection
We’ll find out how well Suica 2.0 works on May 27…hopefully it will be a happy marriage of ‘truth in the card’ Suica Stored Fare balance + central fare processing. The important point is that all Transit IC card barriers will eventually go away when Suica 2.0 is deployed across the entire JR East system. People can travel anywhere on the transit IC network not having to think about barrier nonsense, just like paper tickets. Sounds great but when does it happen?

JR East says the Suica region barriers will drop by 2026, at the latest, when Suica 2.0 is rolled out across the entire JR East network. Suica 2.0 starts in Tohoku May 27, Tokyo gets the Suica 2.0 update this summer (2023), Sendai is next, followed by Niigata. At the same time all Suica gaps will be filled, all stations currently without Suica will be wired. We will find out if Suica 2.0 is really faster than Suica 1.0 but the 3 year rollout, roughly 1 year per current Suica region, certainly looks like a lot of system optimization work is padded into the schedule.

An interesting point here is that QR Eki-Net service starts in the very same Suica 2.0 Tohoku launch region which means that QR Eki-Net uses the same Suica 2.0 fare validation system. Suica 2.0 does QR too. When Suica 2.0 goes wide, so does QR. It’s one package with 2 parts as shown in the Suica Service Roadmap: the Suica 2.0 Platform and a ‘new’ (and unnamed) Ticketing system, which might be the venerable (and earthquake hardened) JR Group MARS system updated for the mobile transit era.

And when does seamless cross region IC transit for Suica, TOICA, et al. happen? Hopefully the JR Group is coordinating so that the Suica 2.0 rollout is mirrored by the other JR Group companies. The JR Central TOICA announcement certainly suggests so. Slight differences are already apparent: JR East prefers cloud connected Suica 2.0 validators at unmanned stations. JR Central and JR West prefer the bus style approach of having on board enter and exit validators for rural lines with unmanned stations. Either way is fine, just get it done as quickly as possible. Let the Transit IC barriers drop away into the past where they belong. Because with Suica 2.0 in place and barriers gone, the way is also cleared for fare capping, automated discounts, specialty ticketing and lots of new cloud based transit services.


This post was originally published 2023-02-27 and was reposted with the latest information from JR East on 2023-04-04.

Related post: Thoughts on Suica 2.0

iPhone NFC misinformation alive and well on reddit

Once in a while I get a surge of traffic from reddit and like to see which post was linked and the attached discussion. This was very hard to do before reddit added comment searches and even so it takes a few days before a new entry shows up in search results. The latest one was about iPhone X and NFC.

Question: What’s the difference between X and XS ? Which is better ? My second question: Recently I bought an X Japanese Version. Is it different from regular X ??

Answer 1: X to XS is Just a small minor cpu upgrade and minor antenna fixes making the iPhone bottom speaker/microphone holes assymetrical, if you bought a X from Japan and are planning to use it for commuting using apple pay there, make sure to check the production date, pre2018 iPhone X has a suica gate problems that got fixed with the Rev B iPhone X. iPhone X suica problem

Answer 2: Also, all Japanese iPhones have a different NFC reader, so they won’t work with non Japanese tap and pay terminals and other NFC points, eg on public transit and similar

Yikes, all the good and bad of reddit in one post. The question is a good one but the good natured answers are equally helpful and utterly misleading.

Answer 1 is a little off in that bad iPhone X NFC was not a Suica problem, NFC was unreliable across the board regardless of type (A-B-F) or protocol (EMV, FeliCa, etc.), with iPhone X NFC crapping out completely later on (after AppleCare expired naturally). The Rev B thing was just my made up name for units manufactured after April 2018 with reliable NFC. And even though most people have moved on to newer iPhone models with much superior NFC performance, the big bad iPhone X NFC problem continues to haunt users. For me, with 3 replacements and a lot of headaches, iPhone X was the worst iPhone ever. iPhone X users deserved a NFC repair program but never got one because at the time Apple Pay Express Transit was only available in Japan. Apple at its Tim Cookian worst.

Answer 2 is completely wrong. The poster has no idea what they are talking about. All iPhone models have the same NFC hardware. It doesn’t matter what country the iPhone was purchased in, it all just works in every Apple Pay supported region for all NFC flavors. That’s the beauty of Apple’s global NFC hardware strategy that began with iPhone 8 along with NFC switching savvy Apple Pay Wallet that Android has yet to match…not even Google Pixel.

How much does Smart Navigo HCE suck?

It’s interesting parsing app reviews that say ‘this app sucks’. How does it suck and why? As I’ve said before, the overwhelming negative App Store reviews for Suica App are not about the app but about poor network connectivity kills a connectivity critical service app. The poor connectivity is due to a variety of factors: carrier auto-connect and free WiFi or overloaded mobile connections messing with Mobile Suica recharge and other online functions. People assume the WiFi and cellular icons at the top of the phone screen indicate a healthy internet connection, which they decidedly do not.

Most users see Suica App as the software that controls everything Mobile Suica AND iPhone NFC hardware. It does not of course but people dump all blame on Suica App anyway. Fortunately most of what Mobile Suica does is done without an internet connection. The only time it needs one is recharge time with a credit card in Apple Pay Wallet app or Suica App.

Yet all that complaining over online Mobile Suica app services however, tells us something important about mobile internet connections in station areas, on trains and subways: they suck. Despite ubiquitous 4G LTE~5G cellular and WiFi coverage, reliable internet is notoriously fickle in those famously busy Japanese train stations. This is the real reason behind all those ‘this app sucks’ Suica App reviews. Interestingly enough, this is the same performance gripe with the mobile myki system in Victoria. Like Mobile Suica this became a problem because mobile internet connections weren’t up to the job of delivering reliable, trouble free ‘anytime, anywhere’ recharge/top-up, which people tend to do in transit.

Which brings us to Smart Navigo, the Île-de-France Mobilités (IDFM) Paris region transit card for mobile that is going wide on Android smartphones this year. IDFM has spent a lot of time and expense working with Calypso Networks Association (CNA), the transaction tech used for Navigo, to implement the less secure network dependent Calypso HCE ‘cloud’ secure element approach as the default mobile transit tech for Android devices in 2022.

It is very unusual that IDFM chose HCE as their go to mobile strategy on Android when the more secure hardware embedded secure element (eSE) is standard on all smartphone NFC devices these days, and does the job without internet connections. HCE is very different from eSE in that both NFC smartphone and the reader need a connection to talk with a server. HCE was also conceived for leisurely supermarket checkout, not the challenging transit enviroment. How does Calypso HCE compare to the network-less eSE experience? CNA says:

For security reasons, transactions using the personalization key or the load key are not possible through the NFC interface, and must be done with a secure connection to a server.

Only the Calypso debit key is stored in the HCE application for validation on entrance and control during travel, coupled with a mechanism of renewal of the Calypso Serial Number (CSN) to mitigate the risk of fraud : a part of the CSN contains date and time of validity of the debit key which shall be checked by the terminals.

Thales says: poor mobile network coverage can make HCE services inaccessible. In short no internet connection, no mobile transit service. Let’s compare the basic mobile transit card features of Mobile Suica with Calypso HCE:

IDFM up against the Android wall of manufacturer indifference
It’s too bad IDFM didn’t study Mobile Suica shortcomings, they could have learned a few things. Most certainly they understand HCE shortcomings but chose it anyway. Why? They probably had no choice: it’s highly unlikely IDFM could get Android manufactures to retroactively update eSE for Calypso on countless different Android models. HCE was the only way to rollout Smart Navigo quickly. The Android platform reputation for keeping devices up to date with the latest software is notoriously bad.

If IDFM can convince Android manufacturers, Huawei, Google etc., to pre-load new device eSEs with Calypso, they could have a 2 tier approach: (1) full spec eSE Smart Navigo for Google Pay Pixel, Huawei Pay and so on, (2) limited spec HCE Smart Navigo for regular, i.e. cheap crappy, Android.

Right out of the gate Smart Navigo HCE won’t support power reserve NFC transactions even on Android devices that support it for regular eSE NFC. In total, there are 6 core Smart Navigo features that are internet connection dependent vs 1 Mobile Suica feature. 6 more things to complain about when they don’t work…in other words the Smart Navigo HCE suck index is 6 times greater than Mobile Suica. If Suica App is anything to go by, there are going to be a lot of bad Google Play reviews for the HCE version of the Île-de-France Mobilités App.

iPhone and Apple Watch users can be thankful that Apple Pay Navigo will use eSE (as Samsung Pay Navigo already does), and avoid this mess when the service launches in 2023, matching the Mobile Suica experience, feature for feature.


2022-10-17 UPDATE

Navigo HCE does not support Express Mode, Android users have to wake-unlock-tap to validate. This is the price of using HCE instead of a secure element.

IDFM launched Smart Navigo HCE that does not support an Express Transit mode. Android users have to wake-unlock-tap to validate…the price of using HCE instead of an embedded secure element (eSE). That IDFM and Calypso went with HCE, despite the downsides and the fact that modern NFC capable smartphones all have eSE as standard, is very interesting and speaks volumes about the state of Android NFC and licensing fee headaches. Assume that Mobile Calypso don’t come pre-installed on smartphone eSEs, unlike EMV, then imagine the nightmare of: (1) dealing with all the Android manufacturers to retroactively update their devices so they are compatible with eSE Navigo (such as currently found on compatible Samsung Pay devices), and (2) getting Google Pay on board. Going the HCE route likely avoided a lengthy messy delay getting Navigo on mobile for the Android masses which is by far the majority in France.

This is exactly the mess that Apple Pay takes care of behind the scenes so users don’t see or deal with any of it. That’s the value of having a gatekeeper, better UI and security encourages users to use NFC payments and Apple Pay use far exceeds any other digital wallet…this is the benefit that Apple Pay delivers to developers. Too bad it’s going away for EU users that the EU is forcing Apple to give up their NFC gatekeeping role, which is very sucky indeed.

Bad Suica App reviews, real or urban legend?

Suica App user reviews are relentlessly bad, rip after rip of ‘this software sucks’. Never a good thing to say. Here’s the thing however, when you dig into the reviews most of them have little to do Suica App. It’s also really weird that many reviewers/users seem to think they need Suica App for using Suica at the transit gate. They don’t.

Why are people even using Suica App anyway? You don’t need it to add Suica to iPhone, you don’t need it to recharge Suica. All these things can be done in Wallet app. And now that people are working remotely, there is much less demand for purchasing commuter passes, the biggest reason for using Suica App in the first place. But there is one good reason for using Suica App: setting up Auto-Charge. Set that and you’ll never have to use Suica App.

There’s an important difference to know about Auto-Charge vs. regular recharge in Suica app and Wallet app: auto-charge is locally processed via the transit gate Suica NFC reader. It’s instantaneous and doesn’t care about your iPhone network connection.

Wallet and Suica app recharge are processed via the iPhone (or Apple Watch) network connection. Apple Pay talks with iCloud and Mobile Suica, the transaction is processed online and relayed back to Apple Pay, the recharge amount is added to Suica card. Many network hoops.

There is a message the Mobile Suica twitter account puts out regularly: make sure your smartphone has a robust network connection and don’t use free WiFi when recharging Suica or using Suica App. A bad WiFi connection fools Suica App users into thinking their iPhone is connected to the internet when it is not. This is a particular problem with carrier Wi-Fi SIM auto-connect that bypasses a solid 4G/5G connection and automatically connects to an extremely unstable or overloaded carrier WiFi instead. WiFi on trains and in stations is never reliable and should be turned off when using recharging Suica in Wallet or using Suica App.

Which brings us to an interesting Suica App user review titled “It’s a real urban legend” which explains all the crap talk about Mobile Suica boils down to people trying to recharge at rush hour in transit gate areas with a crapped out carrier or free WiFi connection…the perfect Suica App killer situation. The reviewer recommends “recharge in a calm place at calm time,” to which I heartily agree. Or better yet, ditch network recharge altogether and use Suica NFC Auto-Charge. It will never fail you.

The Suica 2 in 1 mobile dilemma: promoting targeted region services on a wide mobile platform

Suica 2 in 1 Region Affiliate Transit Cards have a problem: it would be great to have these cards available on mobile wallet platforms (Osaifu Keitai, Apple Pay, etc.) however, the whole point of region cards is to promote region affiliate transit companies and service benefits for the people who live there. There are region affiliate transit points and services for everybody, discounts and point rebates for elderly and disabled users, commute plans and so on, subsidized by prefectural and local city governments.

Hence despite the Suica logo on them, region affiliate cards are not available from JR East. They are only available from region affiliate bus offices. But it’s a pain getting them, commute plan renewal requires another trip to the bus office and cash recharge is the only option. Suica 2 in 1 would be infinitely more useful and user friendly on mobile. Region affiliate users are certainly happy to have a card that covers all of their transit needs but it doesn’t bring them into the Mobile Suica era.

But mobile is a two edged sword. On one hand you want the convenience of Mobile Suica, on the other hand region cards need to promote subsidized services for a particular location, keeping them local on a wide mobile platform and restricting access for special services with certain eligibility requirements (local disabled and elderly residents) is a challenge. How does one promote targeted regional services on widely available mobile platforms like Mobile Suica on Apple Pay?

The Suica App mobile fix
Hmmm, this sounds like a similar problem with student commuter passes. JR East and customers want to do away with the drudgery of going to the local JR East station ticket window to confirm student ID validity, nevertheless, student ID validity must be confirmed before a student commuter pass can be purchased. Mobile Suica has supported student commuter passes but students have to go to a local JR East office to validate and activate it.

Mobile Suica will address this problem on February 13 with a system update and new version of Suica App (v3.1.0) that adds support for in-app purchasing and renewing student commute plans. Another Mobile Suica update on March 12 will add Tokyo region day pass purchase support. Think of these as selective local services on a widely available mobile platform. Let’s see how this approach can be applied to Suica 2 in 1 Region Affiliate cards.

1) Region affiliate mobile issue
When I made my Apple Wallet transit card wish list mockup, I thought it might be nice to have all the new Suica 2 in 1 cards available directly in Wallet app along with Mobile ICOCA (coming in 2023).

In reality, it’s not a good idea to make region affiliate transit cards available to every Wallet app user. Transit cards are easier to add in iOS 15 Wallet app than ever before, but not delete and get a refund. Too many choices confuse users who may be new to Apple Pay. What if a user wanted to add a regular Suica but added totra Suica or nolbé Suica by mistake?

Apple Pay WAON deals with this problem in a smart way: regular WAON can be added directly in Wallet app, regional WAON cards are added to Wallet with WAON app. The beauty of issuing specialty WAON cards in the app is they have region specific goodies attached: a portion of the region WAON card transaction goes to a local government development fund.

This approach is a perfect fit for region affiliate Suica cards on mobile with local perks, bonus local transit points and so on when issuing cards on mobile.

2) Suica 2 in 1 commuter pass purchases and limited eligibility card issue
There are a few more hurdles to clear before Suica 2 in 1 can join the mobile era: region affiliate commute plan purchase and renewal, limited eligibility card issue (for elder and disabled users).

Let’s say you are a totra commuter who rides a region affiliate bus and a JR East train. In this case you need 2 separate commute plans on your Suica 2 in 1 totra card, one for the region affiliate bus, one for JR East. The commuters plans must be purchased separately: the region affliliate commuter pass is bought at the bus office, the JR East section is then purchased added at a JR East station ticket office. It’s a complex hassle. JR East stations are all cashless but only a few region affiliate bus offices take credit cards…and so it goes. How nice it would be to do this with an app and pay with Apple Pay.

Mobile Suica already hosts this kind of complex commute plan configuration but not in Suica App. Mobile PASMO and PASMO App are hosted on the JR East system, basically rebranded Mobile Suica, and easily configure complex bus + train commute plans from multiple transit operators for mobile purchase.

This leaves limited eligibility card issue. The February 13 Mobile Suica update adds student commuter pass pre-registration and ID verification uploading via the Mobile Suica member website. The student reservers a pass entering school information, commute route and uploads a picture of their school ID. Approved student commuter pass reservations are then purchased in Suica App. This ID verification method can be used for issuing elder and disabled Suica 2 in 1 cards. It’s still a manual authentication process that digital My Number cards will, hopefully, transform into a simple automatic one with instant verification of necessary personal information.

One of the really interesting things about Suica 2 in 1 is that the next generation format is the very first Suica card that supports disability fares. Up until now disability fare users have been limited to paper passes inspected at manned transit gates.

JR East plans to drastically reduce the number of manned transit gate areas. Before this happens, mobile support for all Suica cards of every kind, especially the new Suica 2 in 1 features, must be in place. The pieces of the solution are there, it only a matter of JR East integrating them into a Mobile Suica system and Suica App update.

One Suica App to rule them all
If we are promoting region affiliate Suica cards does it make sense to do it all in Suica App or have individually branded local apps for totra, nolbé, cherica, et al? One main goal of Suica 2 in 1 is cost reduction and infrastructure sharing. Despite all the different names and card artwork these are Suica cards with all the Suica benefits and JR East managing the Suica infrastructure for region affiliates.

I’d argue it doesn’t make sense nor does it fit with cost reduction goals to do a bunch of re-skinned local Suica Apps when JR East is making a bunch of replicas. Better to focus efforts on making Suica App a streamlined easy to use app with all the necessary tools for managing mobile region affiliate cards. And because physical cards remain an important part of the Suica platform strategy, Suica App must also add a physical card iPhone recharge feature similar to what Octopus App and Navigo App offer.

All in all I expect that 2023, which will see the launch of the highly anticipated JR West Mobile ICOCA service, will be a big year for Mobile Suica and Suica App too.