Instant issue for Apple Pay Edy, nanaco, WAON?

A fun mockup of Wallet add card options for Edy, nanaco, WAON that will probably never happen. If they come it will be digital issue via apps.

Now that VISA JP finally signed with Apple Pay, what about the last holdouts: Edy, nanaco and WAON? These have been on Google Pay for some time but like all things Google Pay Japan, it is courtesy of Osaifu Keitai rather than native Google support. Apple was smart to go for Suica first, then PASMO (which has yet to appear on Google Pay) but it’s time to complete the Apple Pay Japan lineup.

Google Pay Japan has 2 basic categories for adding cards: EMV bank payment cards (AMEX, JCB, mastercard, VISA) and Japanese eMoney cards (Suica, Edy, nanaco, WAON, iD, QUICPay). In other words, Google Pay arranges cards by NFC flavor. This is because many Android devices sold outside of Japan don’t include FeliCa even though they have the hardware to do so. Google Pixel 5 for example has Mobile FeliCa installed on every single device it sells, but only activates it for Japanese models. Perhaps this will change with Pixel 6, we will see.

Apple Pay doesn’t make a distinction between NFC flavors, just one global NFC. No EMV or FeliCa bank payment cards, just payment cards, period. Apple also encourages Japanese bank card issuers to use the NFC switching and dual mode features of iOS and watchOS Wallet for seamless use on any payment reader in Japan or abroad. The same thing applies to Wallet transit cards. Wallet can have multiple Express Transit cards and juggle between FeliCa (Suica, Octopus, PASMO) MIFARE (SmarTrip, Clipper, TAP) and PBOC (China T-Union cards).

So what is the Wallet category for non-transit stored value prepaid payment cards? I have no idea but for this exercise I’ll use eMoney (電子マネー). Apple Pay has everything in place to flip the switch since 2016, what’s the holdup? There’s a big problem using the Suica add card Wallet process for eMoney cards. This problem is on full display with Google Pay WAON: the user has to create an WAON account in Google Pay to add it. Worse, if the user deletes the WAON card they loose the Google Pay created WAON ID and card balance.

I don’t think Apple wants this ‘create an account’ nightmare scenario in Apple Pay, that’s what apps are for. Fortunately we have a growing collection of ‘instant issue’ apps for adding cards to Wallet and digital issue only is quickly becoming standard for Apple Pay Japan debit/prepaid cards: kyash, Minna no Ginko, Toyota Wallet, etc. The digital issue app model is perfect for Edy, nanaco and WAON who want to be collecting accounts instead of selling plastic prepaid cards. They already have iOS apps. Leave the account creation and management drudgery in the app so users curse the app instead of Apple Pay. Once done the user taps ‘Add to Wallet’ and presto, instant WAON all ready to go with direct Wallet recharge. Other bonuses: (1) instant issue apps eliminate ‘I wanna transfer my plastic card to Wallet’ overhead, (2) if anything goes wrong and the balance is lost, it’s the fault of the app, not Apple Pay. Keeping things simple and streamlined is key for a good Apple Pay user experience, one more Wallet reboot challenge for iOS 15.

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 VISA JP Apple Pay announcement and digital banking wars

MacRumors: Customers with Visa cards…will be able to add their card to their Wallet on iPhone and Apple Watch.

Me: I like MacRumors but the writer here has no idea what the story is or that users have been using these cards in Apple Pay all along for store purchases.

MacRumors: Hey! Could you elaborate on what you mean? Visa cards issued by those banks now have Apple Pay, correct?

Sure Sami, here’s the elaborate story. Do you know FeliCa? It’s the Sony created NFC standard that has been around a long time, long before EMV grafted NFC into contactless credit cards. When mobile payments launched in Japan back in 2004, Mobile FeliCa was the only technology that worked. So mobile payments for all major credit cards and Suica were built on Mobile FeliCa, the contactless payments infrastructure in Japan grew from that.

Fast forward to 2016. Phil Schiller announced FeliCa for iPhone 7 at the keynote and the launch of Apple Pay in Japan. VISA Japan didn’t sign an agreement with Apple but it didn’t matter much because VISA JP cards were available for Apple Pay thanks to previous Mobile FeliCa agreements covering the iD and QUICPay networks for store payments. The other card companies (Mastercard JP, JCB, American Express JP) signed with Apple.

It was a big success. But the Mobile FeliCa agreements only covered store purchases, they didn’t cover things like in-app purchases. Even though many Japanese users added their VISA cards to Apple Pay they couldn’t use them to recharge Suica cards because in app purchases were not supported.

Fast forward to 2020. VISA JP is a major sponsor of the Tokyo Olympics showering sponsorship money to promote ‘VISA Touch’ EMV contactless cards. They want customers to use VISA Touch at stores, not iD and QUICPay because the margins are nicer and EMV contactless is a world standard except for places like Japan (FeliCa) and China (PBOC). Most of the POS equipment in Japanese stores is multi-protocol ready so the customer NFC flavor is a moot point. For whatever reason, let’s say marketshare, VISA JP finally signed on with Apple Pay.

What changed for all those VISA JP cards already working in Apple Pay Wallet these past few years? A VISA logo, in-app payments, dual mode NFC and Payment card Express Transit:

Did you get that Sami? Hello, anybody there?

Digital Banking Wars
Seriously though, it’s sad when tech writers don’t understand the technology in the stories they write. All major Apple sites ran the same wrong story. It should have been: Visa JP Cards now fully support Apple Pay. I think journalists do everybody a great service when explaining complex stories and connecting the dots in easy to understand ways. Nobody cares, which is a shame because there were other major things going on behind the VISA JP Apple Pay announcement that even the Japanese tech media missed: the very same day, NTT Docomo and MUFG announced a joint digital banking venture.

Let’s take a closer look at that VISA JP Apple Pay announcement, specifically the issuer launch list: APLUS, Cedyna (SMBC Financial), SMBC, Docomo, MICARD, Saison, JACCS, Rakuten. Do you see MUFG? Nope. MUFG brand VISA cards will join at some point, probably, but VISA has put all their eggs in the SMBC basket, the companies are not on the friendliest of terms.

NTT Docomo and SMBC/VISA group feuded for years and called a stalemate. It was only a matter of time before NTT Docomo kicked SMBC to the curb, which they did yesterday with the MUFG joint announcement. Docomo and MUFG are going to leverage dPoint into an economic zone to rival Rakuten and SMBC/VISA V Point. It’s as simple as that. And here you thought that VISA JP announcement was only about Apple Pay. Think again, the economic zone mobile digital banking wars are just getting started.

One last bit: if you want to know the reason why it took so long for VISA JP to sign with Apple go to the SMBC V Point App page and look at the Apple Pay • Google Pay section. ApplePay is dual mode, Google Pay is EMV only. It was the power play we suspected all along: VISA wanted to kill FeliCa, Apple stuck to its NFC switching dual mode guns. For a detailed list of VISA JP cards and supported features go here.

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.