Mobile Suica foreign VISA card processing changes with the Apple Pay VISA JP agreement

Foreign issue VISA card holders using Apple Pay Suica beware, you might be in for a rude surprise when you get the monthly statement. A reader sent some very interesting information:

JR East started processing these Visa transactions differently on foreign cards. Previously, these were processed as ‘SUICA MOBILE PAYMENT’ and the merchant category was passenger railways (travel). Since around May 11 or 12, these are now processed as ‘MOBILE SUICA APPLE V’ and the merchant category is catalog merchants (shopping). This is an unfortunate change as the merchant category change from travel to shopping downgrades the points earning capability on several American cards (eg. from 3x points on the Chase Sapphire Reserve to 1x).

Chase Sapphire Reserve has been a popular choice for Apple Pay Suica recharge because of the 3x rewards. The VISA JP Apple Pay agreement has changed how foreign issue VISA brand card payments made with Apple Pay in Japan are processed obviously, but the merchant category change from railways/travel to catalog/online shopping is a mystery. JR East or VISA JP? On the surface JR East as they are the merchant but why this and why now? Another backend change: JR East is starting 3-D Secure credit card checks in iOS Suica App and Mobile Suica (Android) from May 26.

I do not know if Apple Pay PASMO is in the same boat but suspect so. Foreign issue VISA holders may want to consider using a different credit card for Suica recharge for the best reward points. There are too many reward point differences to make any definitive recommendation. The best long term strategy is to examine your spending patterns and select a JP issue card that fits your needs. Reward point empires to consider: JRE POINT (BIC CAMERA View), Rakuten POINT (Rakuten Card) and V POINT (SMBC Numberless Instant issue).

I will update this post as more information comes in, reader feedback is appreciated.

Update: Good news: a reader reports Apple Pay PASMO recharge still codes as travel for Chase Sapphire VISA 3x travel points. Reader and user comments:

I setup Pasmo in Apple Pay and ran a test transaction with my Chase Sapphire Reserve.  Good news, Pasmo is being processed differently and coding as passenger railways (travel).

I also noticed JRE’s category change for GooglePay Suica a few months ago.

With US credit cards, the Chase Sapphire Reserve (CSR) and the Chase Business Ink Preferred both had 3x points on Travel. If you had used them to charge your Suica via Apple Pay or Google Pay, the charge would show up as ‘travel’ or ‘jr east’. So you were effectively earning 3% cashback (technically more with the multiplier of 1.25 or 1.5 based on the card). The wonderful thing was that you could pay for almost everything in daily life with Google or Apple pay here in Japan. It does seem this has changed. I dropped my CSR a while ago – now it is time to let my Ink go too.

Is it possible to move Suica to a different iCloud account?

asking for a friend but is there a way to remove a PASMO from one iCloud account, and move it over to a different iCloud account? My friend is a bit of an idiot and noob with iPhones.

This is a tricky question and even if possible, why bother? Most people would just add a new Suica•PASMO to iPhone which is very easy to do. Up until the big Mobile Suica reset on March 21 it wasn’t possible to migrate the Suica card anywhere else except a different device with same iCloud account. However, it is now possible to move the same Mobile Suica card between Android and iOS. PASMO doesn’t allow this yet because Mobile PASMO hasn’t received the same backend upgrade. If we were assigning version numbers Mobile Suica would be v2.0, Mobile PASMO would be v1.5. In Mobile Suica 2.0 the card ID, the Mobile Suica account email used for system ID, is independent of Apple Pay and Google Pay systems. Let’s take a look at how it might work.

Here is the Mobile Suica transfer path going from iOS to Android.

  • Requirements: Mobile Suica account, ID registered email and PW, latest versions of Suica App (iOS) and Mobile Suica App (Android) installed on both devices.
  • Step 1: remove Suica from Wallet on iPhone (this parks the Suica card on the Mobile Suica cloud server)
  • Step 2: on the Android device launch Mobile Suica and sign in with the same ID and PW
  • Step 3: follow the screen prompts to add the Suica card from the server to the device

One of the interesting points about Android is that the receiving device must have a valid SIM inserted, otherwise Suica will not transfer. In theory here is how the process might work going between different iCloud account devices:

  • Requirements: Mobile Suica account, ID registered email and PW, Suica App 3.0.3 or later (iOS) installed on both devices.
  • Step 1: remove Suica from Wallet on iCloud A device, sign out of Suica App or delete the app, restart device
  • Step 2: on the iCloud B device launch launch Suica App, tap [機種変更] (Transfer from Android) and sign in with the same ID and PW
  • Step 3: Tap [+], and (if the theory is correct), you should see the Suica card with balance on the server, add to Wallet

Remember this may not work as it is not officially supported by JR East, for security reasons, and I have no way to test confirm if this works or not. Even in the worst case that is does not work you still have the Suica card attached to the iCloud account. And remember, it’s very easy to add Suica and PASMO to any iPhone 8 and later or Apple Watch Series 3 and later.

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**
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**
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**

November 2020🟩🟥Suica 2 in 1 Aomori**
🟩🟥Suica 2 in 1 Akita**
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é)**

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

🟩🟥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.

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 Suica: 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.

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.

Multiple Secure Element domains for Mobile FeliCa 4.1

FeliCa Dude posted a series of deeply interesting tweets relating to Mobile FeliCa 4.1 changes. He had earlier complained of Mobile PASMO lack of Pixel 5 support and it now appears that multiple Secure Element domain support in Mobile FeliCa 4.1 was a reason for that delay. This is an fascinating development but what is it there for?

On a Mobile FeliCa 4.1 Google Pixel device Google has it’s own secure element domain

I assume his tweeted profile is for a Pixel device, hence the FeliCa Networks secure element (SE) + Google SE references. In this context it appears that Google ‘owns’ the Mobile FeliCa SE and which applets load, in other works FeliCa Networks needs permission from Google to load applets on a Google device SE. Devices come pre-loaded as always so customers simply use it out of the box, but the implication is that FeliCa Networks and the SE domain ‘owner’ can load/delete Java Card applets and even update Mobile FeliCa over the air. Whether they actually use this functionality or not is another story.

FeliCa Dude thinks multiple secure element domains are also there to support Ministry of Internal Affairs and Communications (MIC) plans for a digital version of My Number Card (Individual Number Card) for smartphones using the Mobile FeliCa eSE, even though the current plastic card uses NFC-B. It’s strange but exciting to ponder the possibilities of a Mobile FeliCa 4.1 secure element that supports non-FeliCa protocols.

One of the big changes of Mobile FeliCa 4.0 was that it introduced loading a FeliCa applet on any approved secure element. This change frees Android device manufacturers from having to purchase FeliCa chips from the FeliCa Networks supply chain. It basically gives Android devices the same custom secure element arrangement Apple has had since the iPhone 7 Apple Japan Pay launch in 2016.

I asked FeliCa Dude if the Mobile FeliCa 4.1 development is also related to next generation FeliCa feature support used for Suica 2 in1 cards coming this month, in particular the new Extended Overlap Service. He says this is unlikely but I hope we discover other pleasant surprises as intrepid explorers dig into Mobile FeliCa 4.1 details.

MIC digital My Number Card proposal for smartphones