The iOS 13.4 update adds a few interesting UI tweaks to Wallet and Suica. On the performance front iOS 13.4 Apple Pay Suica is the same level of stability we’ve seen on every release since iOS 12.3. The UI for Suica commuter pass has changed slightly with more detail in a separate window-let just below Suica balance/recharge. The commute pass renew button is gone too, but I’m pretty sure it re-appears during the 2 week renew period. I’ll update when confirmed.
I missed a change in the beta: the JP Wallet blurb has been updated slightly too. The Suica mention has been replaced with a generic ‘Transit IC card’. This change is very interesting in light of the recent Mobile PASMO Android release. It could be a sign that Mobile PASMO will be coming to Apple Pay before iOS 14….whenever that is.
Update: some readers have questioned whether this is just a change to bring different region Wallet blurbs in line with each other. Apple Pay Wallet for Hong Kong, for example, added ‘Travel Cards” in iOS 13.0 even though Apple Pay Octopus has yet to appear. But region differences are still there: transit IC cards, travel cards, transit cards. Suica has massive brand recognition in Japan. Apple has leveraged the Suica brand at every opportunity and would not swap it for generic wording lightly, not without a very good reason: more transit IC cards. There is also timing. Mobile PASMO started service March 18, just as iOS 13.4 GM was going out to developers. If it was just a text change, Apple would have done this earlier with the iOS 13.0 debut.
What is Mobile PASMO? Mobile PASMO is an app service, identical to Mobile Suica, for Android v6 Osaifu Keitai devices or later. Users can recharge a virtual PASMO card on the device with a registered credit card, purchase or renew commute plans, view use history, restore the PASMO card from the cloud in case of a lost device, PASMO bus transit users can also earn ‘Bus Toku’ points. Mobile PASMO launched March 18. Details are listed on the Mobile PASMO site (Japanese only).
Is it compatible with Google Pay? (Updated) Not at this time. Users need to be careful: active Google Pay can block Mobile PASMO transactions. Bank cards are limited to Mobile PASMO app registered credit cards: American Express, JCB, Mastercard, Visa. Credit card registration is processed by PASMO and seems to be the weakest part of the system where users are experiencing the most trouble (the rest of the system appears to be licensed Mobile Suica IT assets). Only Japanese issue cards are accepted.
Can I use Mobile Suica and Mobile PASMO on the same device? (Updated) Only 6 recent Osaifu Keitai Type 1 devices support multiple transit card installs. On older Type 2 devices you can only install one and have to choose. As FeliCa Dude explains in his excellent Reddit post, “Mobile PASMO: the “me-too” that’s all about them, and not you” the Mobile FeliCa Android stack on older FeliCa chip devices isn’t like Apple Pay and does not support multiple transit cards or the ability to select one for Express Transit. Type 1 devices updated to Osaifu Ketai 8.2.1 can set one (and only one) ‘main card’ for Express Transit use, with Mobile Suica and Mobile PASMO on the same device. Here is a full device list of Type 1 (Mobile Suica and Mobile PASMO), Type 2 (Mobile Suica or Mobile PASMO), Type 3 (Mobile Suica).
I have a Mobile PASMO capable Type 2 device, which mobile transit service should I use? It all comes down to commuter pass use, if you live in the Suica/PASMO region and use a JR East line on any part of your commute, Mobile Suica gives you the most options. If you do not use a JR East line as part of your commute, Mobile PASMO is the natural choice.
Will Mobile PASMO be coming to Apple Pay?(Updated) iOS 13.4 has some indications that Mobile PASMO might be coming at some point. Mobile PASMO uses licensed Mobile Suica assets and technology, the backend is very similar with a different operator. Apple Pay Wallet does have the ability to host multiple transit cards and select one for Express Transit. In theory a user could have a Suica and a PASMO together in Wallet. We’ll have to wait and see if the PASMO group has enough cloud resources to plug into Apple Pay/Google Pay and how willing they are to deal with non-JP issue credit cards.
Isn’t next generation ‘2 cards in 1’ Suica supposed to fix this?(Updated) Mobile PASMO throws cold water on the one big happy mobile transit family concept of next generation Suica: sharing resources instead of “me too” fiefdoms. Even if the new card architecture fixes all the current shortcomings, which it is supposed to do, nothing can fix the selfish mindset of transit companies who refuse to cooperate. As FeliCa Dude points out, Mobile PASMO is a boondoggle, the result of JR East and PASMO Association failing to cooperate and mutually host commute plans. I suspect that auto-charge transit company premium branded credit cards are getting in the way. Japanese transit companies need to put aside old grudges and cooperate intelligently to get all transit players on mobile as fast as possible. Everybody loses out if they do not.
UPDATE: Japanese programmers digging into Mobile PASMO details find that PASMO licensed Mobile Suica IT assets for Mobile PASMO service. This makes a lot of sense and is an encouraging sign that Mobile Suica cloud resources can be licensed to host other transit IC cards for mobile (ICOCA, TOICA, manaca, etc.).
UPDATE 2: Junya Suzuki posted an article with more Mobile PASMO system details. One leading company in the PASMO Association (Tobu, Keio or Odakyu) licensed Mobile Suica assets and technology from JR East. Cut and paste IT. As said above, this is encouraging because other transit companies (JR West, JR Central et al) can license Mobile Suica assets and park it on whatever cloud service they want: AWS, Azure, NTT Data and so on. Mobile plumbing for connecting Apple Pay and Google Pay is already in place.
Update 3: the Mobile PASMO device link keeps dying, here is downloadable PDF copy as backup:
The chart below lists native transit cards on mobile digital wallets by service launch year, limited to reloadable virtual transit cards already in service or formally announced by wallet platform vendors (Apple/Google/Samsung/etc.) and/or transit operators. Best viewed in landscape mode.
Transit card payment mobile protocols are FeliCa, MIFARE and PBOC 2.0/3.0, the later is the Chinese variant of EMV which uses Type A NFC with the slowest grocery store checkout transaction speeds of the three protocols:
Each card organization has formed its own specifications based on the EMV specification based on its own business refinement and expansion, such as China UnionPay’s PBOC 2.0 specification…PBOC based on the EMV standard, combined with the needs of domestic banks, the People’s Bank of China promulgated the PBOC series of standards: 1 PBOC1.0: e-wallet / electronic passbook / magnetic stripe card function 2 PBOC 2.0: E-wallet extension application, debit/credit application, personalization guide, contactless IC card standard 3 PBOC 3.0: Cancel e-wallet and electronic passbook application, cancel downgrade transaction, multi-algorithm extension, multi-application extension, mobile payment standard
Compared to other contactless smartcards in use, the data transmission of <China T-Union> Yang Cheng Tong is criticized by commuters that it takes 1~2 seconds between the card and reader to complete the transaction, though the operator claims that the data communication only takes 0.5 seconds in its official site.
Some China transit cards used FeliCa and MIFARE protocols in the past but have been migrated to the PBOC 2.0/3.0 China T-union card spec for interoperable transit cards that work across the country, similar to what Japan has with Suica, ICOCA, PASMO, etc. Mobile FeliCa developed by Sony and NTT Docomo has been around the longest and works across multiple mobile hardware platforms from Symbian handsets, to Android, to iOS/watchOS. MIFARE and PBOC 2.0 have a shorter history on mobile. The key period is 2015~2016 which saw transit card debuts on Apple Pay, Samsung Pay and Huawei Pay. Initial Apple Pay support for Beijing and Shanghai transit cards was listed as beta on iOS 11.3. An NFC engineering source said the early Apple implementation was not the full PBOC 2.0 spec, apparently fixed in iOS 12.3 when the beta label was removed.
One of the biggest advantages of transit cards in digital wallets is the freedom of anywhere anytime recharge with credit/debit cards; transit users are no longer chained to station kiosks to recharge plastic smartcards or renew a pass. The more payment options supported on the recharge backend, the more convenient. These are great customer features, so why is it taking so long to get transit cards on mobile in America and Europe when there are many China T-Union transit cards already on mobile?
Many transit card fare systems outside of Asia are managed by Cubic Transportation Systems, including Oyster, Opal, Clipper, OMNY, Ventra and SmarTrip to name a few. Cubic and operators like Transport for London and Transport for NSW have focused primarily on Open Loop EMV card support as a mobile solution instead of native virtual transit cards.
Publicly run transit system resources are usually limited so using bank cards for open loop transit is seen as a way to reduce system costs. The downside is that banks get a cut from transit gate transactions and transit cards for mobile are slow in coming, if at all. Cubic’s very first virtual transit card effort, the long delayed Apple Pay Ventra, is all the evidence you need when open loop is a priority and transit cards are not. Despite the recently announced Google Pay and Cubic alliance, I think transit cards on mobile will continue to arrive in a slow trickle. Let’s face it, HOP is the only American transit card that has gone mobile so far, and it’s not managed by Cubic. It’s the same story in Australia with Melbourne myki Google Pay.
Putting aside the open loop fad for a moment, I think the large deployment of China T-Union cards on mobile comes down to one simple thing that has nothing to do with protocols or smartphone hardware: all China T-Union cards share a common recharge backend cloud provided by Union Pay. It’s the reason why China T-Union sports a similar logo, the Union from Union Pay, and can only be recharged with a Union Pay card. It’s all one package. From Apple Support:
Here’s what you need to create a new Beijing Transit or Shanghai Transit card in Wallet to use with your iPhone: An iPhone 6, iPhone 6 Plus, or later, set up with Face ID, Touch ID, or a passcode A China UnionPay debit card for Beijing, or a China UnionPay credit or debit card for Shanghai that you’ve added to Wallet
A common recharge backend cloud shared by all transit cards with the same card architecture makes hosting virtual cards much easier, the various transit operators don’t have to host everything directly or build a cloud backend from scratch, and there’s nothing to negotiate because Union Pay is the only payment network.
China T-Union in the cards for Hong Kong Octopus? China T-Union illustrates the power a national transit card standard backed with a shared cloud resource but it’s a straightjacket: Union Pay is the only payment network allowed. The real interesting development here is that QR Codes (AliPay/WeChat Pay) for transit, and everything else, are mainstream in China. There are many reasons for this outcome but on the transit gate QR Codes and PBOC-EMV transit cards are pretty much the same speed. There isn’t enough difference to care, and AliPay/WeChat Pay represent a choice outside the Union Pay straitjacket with all kinds of incentives to use QR.
Another interesting development is the pressure from QR Code players like Alipay for a piece of MTR transit gate action, and the Greater Bay Area transit card negoiations with Yangchengtong on the Hong Kong MTR/Octopus Card Limited mobile strategy roadmap. QR is mobile only of course, but a dual mode FeliCa/PBOC card approach for the Greater Bay Area is much cheaper and easier to implement on mobile than plastic.
Unfortunately in the face of pressure MTR/OCL, a world leading transit platform business model and innovator, has been surprisingly slow rolling out virtual Octopus cards on digital wallets to encourage the migration from plastic cards with new kinds of mobile services. It’s a troubling turn of events because OCL has had all the necessary transit on mobile infrastructure in place to move forward quickly for some time.
The recent Hong Kong protests followed now by the coronavirus crisis are certainly slowing things down. In the end however, growing mobile services is the best way forward for Octopus to remain a viable Hong Kong MTR business in these uncertain times. Because if it does not, Octopus risks becoming just another China T-Union card. Put it this way, if OCL doesn’t innovate and invest it its future as a world’s leading transit platform, it does not have one.
The recently announced Mobile PASMO has some serious limitations lucidly explained in FeliCa Dude’s ‘Mobile PASMO – something we shouldn’t need‘ reddit post. It shines a light on the unfortunate petty politics of Japanese business culture, a catch-22 that ends up killing the very opportunities Japanese companies work to create. Mimicchii is a good Japanese word for it: so obsessively stuck on pointless small details that one completely misses the big opportunity. The PASMO association knows they will loose out, eventually, but hang on to their one and only advantage, commute passes, in the hope they gain a better losers bargain in the end. But how much opportunity is lost by then?
As FeliCa Dude points out, Mobile PASMO is a pointless waste of money and system resources to replicate what Mobile Suica already does:
PASMO is inferior to Suica in many respects, the idea of deploying Mobile PASMO and removing the user’s ability to choose Mobile Suica is fairly short-sighted. Such a development likely cost many hours and much money, but is effectively a boondoggle and a monument to the stubborn failure of JR and the PASMO Association to sort out a way to issue commuter passes on each other’s cards.
Taken to an extreme each transit card player would build its own mobile service but this is impossible in an era of shrinking ridership and resources.
The next generation 2 cards in 1 Suica due in 2021 aims to fix the current state of affairs. Architecturally I expect the problems will be solved, but corporate politics are another matter. JR East will have to offer enough cost saving incentives and flexible extras for the other major transit card players to host their service assets on Mobile Suica: commute plans, Shinkansen eTickets and more. It’s certainly in everybody’s best interest to do so. Time to put aside the mimicchii politics and duplication. If Japanese transit companies can’t come together to build the future, everybody loses.
Mobile PASMO was announced for Osaifu Keitai compatible Android devices running Android 6 or later, the service due to start in late March. There was speculation the service would launch at some point when the Mobile PASMO name was registered in late 2017. Here are a few quick observations based on the sparse announcement details.
Service is limited to the Mobile PASMO Osaifu Keitai Android app with a limited credit/debit card backend. Think Suica App without Google Pay or Apple Pay integration. You can register a single card for recharge hosted by the Mobile PASMO backend but users cannot mix and match cards like you can with Apple and Google digital wallets and Mobile Suica.
This announcement is cutting things awfully close for a March debut of a major service with a squishy start date and no user device profile due until just before launch. Japanese companies usually announce ‘coming this spring’ services 3~4 months in advance. This suggests testing is not very far along and not all PASMO rail operators are integrated for Mobile PASMO commute passes at launch. Long story short: we won’t see Google Pay or Apple Pay integration for a while, local Japanese reports are confirming this already.
Suica and PASMO systems are already cross integrated for auto recharge and commute passes at the transit gate and station kiosk level, we also have the next generation Suica format coming one year from now in early 2021. Reducing support costs for commute pass purchase and renewals by moving them online are a key target for both systems, growing integration of Mobile Suica and Mobile PASMO is a given.
Summary and Update Mobile PASMO is a classic Osaifu Keitai app similar to 2011 era Mobile Suica before Apple Pay and Google Pay integration. That level of integration will require more backend cloud support and qualification but this won’t come easy for PASMO by itself: unlike Suica which is run by JR East, PASMO is an association of large and small private rail operators, only a few of whom have deep pockets and IT resources. The real question is how much JR East Mobile Suica and Mobile PASMO will cooperate to deploy Mobile Suica resources and deep expertise to integrate the many different PASMO players and expand services for all. FeliCa Dude sums it up best in his essential Reddit post: Mobile PASMO – something we shouldn’t need.