WWDC21 Apple Pay Wish List: new Wallet app

It’s that time of year again, to ponder the mysteries of Apple Pay, Wallet, PassKit and Core NFC in the next major iOS release. I wasn’t planning a list this year because all the things covered last year: UWB Touchless CarKey, QR Code Payments, etc., are still lurking in PassKit calls and internal beta test builds and have yet to see the light of day. And then there is App Clips, a solution that finally leverages the versatility of NFC tags and iPhone NFC with reader mode was the big WWDC20 story, but it didn’t come into focus either. Too many COVID distractions.

No, no, the only thing that mattered to users and developers was this: when will Apple do something about the Face ID with face mask problem? The eagerly awaited iOS 14.5 Unlock with Apple Watch feature will almost certainly be the most popular feature of iOS 15 too. There are some interesting new PassKit tidbits in iOS 14.5: PKRadioTechnology type properties for NFC and bluetooth, the later for UWB Touchless use. This is the same pattern we saw at the end of the iOS 13 cycle with PassKit Secure Element Pass references replacing NFC Certificate Pass.

So what’s on the slab for all things WWDC21 iOS 15 Apple Pay? I have no idea. UWB Touchless and QR payment support lurking in the background might see the light of day, App Clips might get some refinements. Nothing really new. So I asked readers what they wanted for iOS 15 Apple Pay and the answer was clear: a Wallet app reboot. I didn’t think much about it until I saw the list of China T-Union add card Wallet options for mainland China.

The Apple Pay China Transit card list is long and getting longer

More Apple Pay Transit cards are on the way but there’s another problem, digital ID cards (passports, driver’s license, national identity cards, etc.). Apple Pay Student ID MIFARE cards landed back in iOS 12, but Apple has grander plans revealed in a NFC digital ID patent filing. The Japanese Ministry of Internal Affairs and Communications (MIC) has plans for a digital version of My Number Card (Individual Number Card) and is already in negotiations with Apple. Where and how do digital ID cards fit in the current Wallet model that only holds a maximum of 12 cards? Something has to give.

Wallet has a very simple rule: any card that loads a Java Card applet into the secure element has to reside in Wallet, the maximum number depends on how many Java Card applets it can hold at any one time. Any card or developer that wants to loads applets and use the secure element also has to have a PassKit NFC/Secure Element Certificate Pass. This is covered by NDA but a company called PassKit (not Apple) gives us an idea what Apple’s NFC/Secure Element Pass guidelines are:

Apple care a great deal about the user experience. Before granting NFC certificate access they will ensure that you have the necessary hardware, software and capabilities to develop or deploy an ecosystem that is going to deliver an experience consistent with their guidelines.

Yeah, the end to end user experience, the whole reason behind the success of Apple Pay. But the Apple Pay user experience has seriously declined in the Face ID with face mask era. The current Wallet with its card metaphor has reached a wall, stuffing digital ID and Code Payments into the mix along with non-secure element Wallet tickets, boarding passes and reward cards, all using same old card UI, will only break the user experience on top of the Face ID with face mask inflicted damage.

Even if Apple doesn’t add new functions to iOS 15 Apple Pay, they must lay groundwork for a new, flexible and far more useful next generation Wallet app, for adding, storing, configuring and most of all, using. Something anything to save us from the growing cacophony of payment services and apps chasing our money and slowing us down at checkout with finding, unlocking and finally paying. The whole point of Apple Pay Wallet was to free us from physical card clutter. After 7 years of Apple Pay and payment apps we have digital clutter that’s almost worse than the original problem that digital wallets and smartphones were supposed to free us from. Let’s get our eyeballs and attention spans back.

The Super Suica Reference

The new features that make up 2 in 1 Suica are called many things. JR East calls it ‘Next Generation Suica’ and ‘2 in 1 Region Affiliate Card’. Yanik Mangan came up with a great ‘All-in-one Suica’ moniker in his limitless possibilities podcast. I call it, and will continue to call it, Super Suica because I see wider Suica platform initiatives built off the new FeliCa OS features used for 2 in 1 • next generation Suica. It’s a looser, fuzzier platform evolution definition compared to Yanik’s tighter all-in-one card solution focused one.

That doesn’t mean that Super Suica or all-in-one Suica will ever happen they way we envision it, but at least we have some convenient handles to discuss and categorize ongoing developments until something official comes along.

This is a list of announcements, launches and posts related to Super Suica as a platform. Announcements are italic with links to JR Group PR releases, launches are bold, color classifications are as follows:

🟩= Suica cards and Transit IC region extensions
🟧= Mobile FeliCa, Mobile Suica + derivations (Mobile PASMO, Mobile ICOCA)
🟥= FeliCa Standard SD2• New FeliCa OS
🟦= Cloud Suica and cloud account services

DateCategory • Announcement** • Launch*Estimated Start
September 2018🟩🟥Suica 2 in 1 • FeliCa Standard SD2**2021
June 2019🟩🟥Suica 2 in 1 for Tochigi**
🟧Rakuten Pay Suica**
2021~2
2021
September 2019🟩🟥Cross Region Commuter Passes for ICOCA-TOICA-Suica**2021
October 2019🟧Mobile PASMO** (rebranded Mobile Suica)2021
December 2019🟥🟧UWB Touchless Mobile FeliCa**2022~3?
January 2020🟩🟥Suica 2 in 1 Iwate Green Pass (Iwate)**
🟧Mobile PASMO**
2021
March 2020🟧Mobile PASMO for Osaifu Keitai*
🟦Eki-Net Shinkansen eTicket service*
May 2020🟧Garmin Pay Suica*
🟧Rakuten Pay Suica*
September 2020🟥FeliCa Standard SD2 cards with new FeliCa OS features*
November 2020🟧wena 3 (smartwatch+band) Suica *
October 2020🟧Apple Pay PASMO*
🟧Mobile ICOCA**
🟩🟥Suica 2 in 1 Iwate**
🟩🟥Suica 2 in 1 Hachinohe**

2023
2022
2022
November 2020🟩🟥Suica 2 in 1 Aomori**
🟩🟥Suica 2 in 1 Akita**
2022
January 2021🟩Cross Region Commuter ICOCA-TOICA-Suica launch details** with TOICA and ICOCA region extensions (TOICA extensions explicitly for cross region pass support) March 2021
March 2021🟩🟥Cross Region Commuter Passes for ICOCA-TOICA-Suica*
🟩Cross region exit gates installed at Maibara and Atami stations*
🟩🟥Suica 2 in 1 totra and Iwate Green Pass*
🟧Fitbit Pay Suica launch
*
🟩🟥Suica 2 in 1 Yamagata announcement**
🟩🟥Suica 2 in 1 Gunma announcement (Noblé)**




2022
2022
April 2021🟦🟩Cloud Suica with Suica region extension announcement**
🟦 Eki-Net reboot: more cloud based attached services and JRE POINT integration
2023
2021

🟩🟥Next Generation Suica cards
A new card for integrating Transit IC and region cards in new ways focusing on Suica 2 in 1 Region Affiliate transit cards and FeliCa Standard SD2 • FeliCa OS as the core development. JR Cross Region Commuter Passes included as I suspect they also use SD2 Extended Overlap and represent a step towards cross region through transit for Transit IC.

🟧Mobile
The evolution of Mobile FeliCa to include UWB touchless and multiple secure element domains, Mobile Suica service expansion and re-branded assets for Mobile PASMO and Mobile ICOCA.

🟦Cloud
Cloud Suica: a cloud based fare transaction processing and MaaS Suica payment services without a reader, cloud account attached services.

Is Suica ‘all-in-one’ possible?

Now that Suica 2 in 1 Region Affiliate transit cards are out, it’s time to examine the question that Yanik Magnan posed in his limitless possibility podcast: is Suica all-in-one possible? He defines it as follows: “All-in-one in my case would mean all Transit IC and local area transit members sharing the same physical card as a common container for their data, I’m assuming (maybe incorrectly?) that Suica + PASMO on the same card would be possible through whatever totra is doing.”

In my initial Super Suica coverage I outlined all-in-one possibilities beyond the Suica 2 in 1 Region card program and called it ‘Super Suica’ to capture that idea. Unfortunately, and as Yanik points out, I forgot an important aspect: Suica and sister Transit IC cards all use the same FeliCa technology but have their own data formats. That was an oversight. Nevertheless I think we agree, so I’m retiring Super Suica in favor of Yanik’s Suica ‘all-in-one’ moniker. Here is a grab bag of various pieces that hopefully add up to an quick overview, with Suica all-in-one as a platform of technologies that others can build off of, instead of a specific transit card.

FeliCa Enhancements
Since November 2020 we’ve seen a number of FeliCa enhancements: (1) FeliCa Standard SD2, (2) Mobile FeliCa Multiple Secure Element Domains that support non-FeliCa protocols and, (3) Mobile FeliCa Ultra Wideband Touchless. The most important of these right now is SD2 because it’s a real shipping product with Extended Overlap Service and Value-Limited Purse Service. TagInfo scans of the newly released totra 2 in 1 Suica Region Affiliate transit card reveal Extended Overlap in action. The card itself shows 2 issue numbers on the back, one from JR East who own the SF (stored fare) purse and one for the region operator who own the overall card. That JR East owns the Suica 2 in 1 card SF and float is…interesting and offers a clue as to what’s going on behind the scenes.

FeliCa Standard SD2 powered totra Suica has 2 card numbers

Float Gloat
Who owns the SF purse float, how it works on the reader side and as a business model are the big issues. Here’s an example: I suspect SD2 Extended Overlap might also be used in the new Suica-TOICA-ICOCA cross region commuter passes as those cannot be issued on current plastic and require an upgrade trip to the nearest JR station. We won’t know for sure until we get a TagInfo scan of the new physical card but let’s pretend for a bit.

Say a TOICA user purchases a cross region commuter pass from Numazu (TOICA) to Odawara (Suica) for regular non-Shinkansen transit. In this case the cross region solution is easy and acceptable to all JR companies because each transit card issuer owns the SF purse, in this case JR Central. The same applies to JR East when issuing the same commute pass route for Suica. The same scenario would likely be acceptable to all Transit IC companies, sharing a common physical card as a common container for their data, but only if the SF purse ownership was clearly defined as it is in totra Suica so it works on the reader side: this is Suica SF, this is a ICOCA SF, etc., otherwise the reader doesn’t know which one to use.

In other words, let’s 2 in 1 and all-in-one for the shared resources like points, commuter passes and special discount fares for elderly and disabled users, but the SF purse is not shared for 2 in 1 or anything else. Common data format, yes. Common shared SF purse, no. At the end of the day you can’t have a Suica and a PASMO on the same card as the reader won’t know which one to use. We’ll see if Extended Overlap and Value-Limited Purse solves this wanna have cake and eat it too Transit IC dilemma. Sony is now shipping FeliCa Standard SD2 antenna module chips for the reader side of the equation so readers will be getting smarter and evolve too. That’s how I see it for Suica all-in-one, Transit IC and mobile, a gradual evolution.

Mobile hardware barriers
On the mobile front we have a smartphone hardware barrier: the Mobile PASMO Osaifu Keitai Type 1, Type 2, Type 3, mess landed on Mobile Suica with addition of multiple Mobile Suica cards on March 21. Only Osaifu Keitai Type 1 devices can handle multiple Suica and PASMO cards.

This has implications for Mobile FeliCa features such as the Japanese Government My Number Digital Card and UWB Touchless digital car keys. Mobile FeliCa 4.0 and later on Pixel devices indicate the ability to upgrade FeliCa JAVA Card applets and even Mobile FeliCa itself. Whether Android device makers will actually use this OTA ability is a mystery. To date the standard industry practice has been if you want new features, you buy a new device.

And then there is Apple. iPhone 7 JP models that support Suica do not support PASMO, UWB is only available on iPhone 11 and later, and so on. There is no guarantee that Apple will update, say iPhone 11 models, for UWB Touchless, Mobile FeliCa My Number Digital cards or even Suica 2 in 1, if and when the format comes to Mobile Suica.

We’ll see what FeliCa Dude has to say about the all-in-one subject, hopefully in a future Reddit post. It may take a while but worth the wait.

UPDATE
I’m sticking with Super Suica. Yanik’s All-in-one take is a great name focused on the 2 in 1 card architecture that fits all of Transit IC on a single card. My Super Suica take is a wider set of developing platform initiatives. Yanik’s feedback was valuable in forcing me to review my posts and define Super Suica as a platform, I thank him for it.

Japan Cashless 2021: the Wireless Android NFC Reader Suck Index

You too can have the whole transaction world in your hands with the Android based Square Terminal for just ¥46,980

Now that contactless is everywhere, wireless contactless readers have become very fashionable and popular. Nobody wants wires or checkout lines. All of these systems are built around an Android based reading device connected to the internet payment service via Bluetooth, WiFi or 4G with a main terminal, an iPad or a laptop running payment network software. Convenient though they may be, compared with hard wired NFC reader performance they all suck with different levels of suckiness:

  1. stera: this lovely little ‘NFC antenna under the screen’ piece of shit from SMBC, GMO and Visa Japan is so slow that checkout staff put their hand over the stera screen/reader to keep customers waiting until the device is ready to go. This is followed by the instruction ‘don’t move your device until the reader beeps.’ It’s a 2~4 second wait until it beeps. This is 2014 era ‘you’re holding it wrong’ garbage nonsense. I teased one store manager about the hard wired JREM FeliCa readers that were swapped out with stera, “Those were too fast,” he said. Too fast?!
  2. PAYGATE: Another payment provider associated with GMO, slightly faster than stera but still slow, PAYGATE does’t like Apple Pay Suica•PASMO Express Transit very much. Have of the time it ignores it altogether forcing customers into the 2016 era ‘manually bring up Apple Pay Suica’ authenticate and pay maneuver. Another ‘you’re holding/doing it wrong,’ when the fault is on the checkout system side. Passé and totally unnecessary.
  3. AirPay: It’s weird that the cheap AirPay hardware performs better than PAYGATE or stera, it’s even weirder that AirPay performs better than Rakuten Pay which uses the very same reader but is stera shitshow slow.
  4. Square Terminal has gotten lots of media attention in Japan. Too early to experience it in the field yet but I’m not hopeful. Square Terminal is Android based after all and the NCF antenna under the screen design is the worst performing reader design out there. As one Brazilian reader wrote: “I just don’t like the ones running Android because at least here the software is less reliable and I managed to crash a few one by just taping my phone.”

Yep, that observation matches my experience. Payment network providers need better Android readers, the current crop is too slow getting the payment transaction ready to tap. In this era of endless subcontractor layers in the development process, creating a fast reliable Android based NFC wireless reader might be a tall order, if not impossible. The all over the place wireless NFC reader experience certainly doesn’t boast well for open loop advocates.

UPDATE
I ran across another crappy reader experience (above) and retweeted it. A reader had some questions about it, answered here by an anonymous expert. It basically comes down to poorly executed reader polling or not following Sony polling recommendations for FeliCa cards. This is what is happening in the above retweet. It is also what is going on with PAYGATE Station readers, half of the time the proper code hasn’t loaded correctly although this issue seems to be fixed in new PAYGATE Station checkout installations. Which brings us to the point I was trying to make: these performance issues can be fixed with reader firmware updates or transaction system software updates, but never are.

Wildcard polling involves the reader making a request for system code 0xFFFF and expecting the card/device to list all the system codes that it supports. Wildcard polling won’t work on an Apple Pay device in Express Transit mode – instead, the system code must be explicitly polled for (0x0003 for CJRC, 0x8008 for Octopus). You can cause Suica/Octopus to be automatically selected by sending SENSF_REQ (Polling command, 06) for those services explicitly.

I have verified that doing so with Apple Pay will cause the emulated card to be switched out as appropriate – the IDm value will also change, since Apple Pay emulates each card separately, instead of with a common IDm as with Osaifu Keitai. If you read the Sony documentation, you will see that developers are cautioned to also poll for the specific service codes they want to access if there’s no response to a wildcard poll.

Perhaps your reader doesn’t do this, but it’s fairly big omission…it should be doing explicit polling. Simply polling for service code 0x0003 should wake up Suica if selected as an Express Transit candidate, even if you don’t send any other commands. I’ve verified this with an RC-S380 reader and NFCPay.

Sorry PRESTO but your open loop video is fake Express Transit (Updated)

UPDATE
March 16: The PRESTO UP Tickets and Fares page now lists EMVExpress Transit support, but no mention of any similar benefits using Google Pay. The Apple Pay Transit support page does not list Express Transit for Canada yet, but the last update was February 3. The PRESTO page also mentions an interesting iPhone issue: “Some iPhone models (8 and earlier), may experience an error message when tapped on a PRESTO device. If you tap with an older Apple device and see a message saying that multiple cards were detected, simply tap your device again and the PRESTO device should accept your tap.” Sounds like a pilot program for teething open loop use issues. No mention of a digital PRESTO card of course. I suspect that when it comes (much later), it will be a closed loop debit card like Apple Pay Ventra.

Apple did a similar Express Transit deal for NYC OMNY, which was basically a very long pilot program and gradual rollout. PRESTO UP is also a pilot program but has an advantage over OMNY in that the PRESTO contactless transit card has been in service since 2009. People are used to it, only the smartphone wallet aspect is new. Meanwhile OMNY is still nursing off the ancient mag-strip swiping MTA Metrocard without a replacement. It will be interesting to hear customer feedback regarding the PRESTO EMV Express Transit experience…for real.


The Metrolinx PRESTO UP service started an open loop contactless payment pilot program this past week. It’s the first step for open loop support across the entire PRESTO fare system. The coverage on MacRumors and elsewhere, and the PRESTOcard youtube video itself makes it look like PRESTO already supports Apple Pay Express Transit when it apparently does not. Apple is very picky when it comes to certifying which open loop transit systems support EMV Apple Pay Express Transit. There aren’t any in Canada. The U.S. has three: NYC OMNY, Chicago Ventra and Portland HOP.

Unfortunately the PRESTO video uses post-production tricks to fake Apple Pay Express Transit. There are three instances: the 1:14 PRESTO reader, the 1:30 onboard verification check, and the 2:16 PRESTO reader. Each of these require a Face ID without mask or passcode Apple Pay authorization. As a reader pointed out the post-production folks neglected to fix the Apple Pay passcode request screen to match the reader ‘Accepted’ screen. Metrolinx promoting PRESTO open loop rollout so people will use it is one thing, but deception isn’t doing users, or PRESTO, any favor.