A while ago Apple Pay just stopped working on my iPhone X. My phone simply hasn’t been detected by any NFC readers I’ve tried. At this point I finally have some spare income and would like to invest in fixing it. I don’t particularly care how involved it is, but I just can’t find any information on where the actual NFC antenna is and if it has the same lock that the face ID sensors do. I’m sorry if I’m just missing some fairly obvious information here. I would just like to be able to use Apple Pay again.
I’ll cut to the chase. My rough estimate is that 40 million iPhone X units were manufactured up to the April 2018 NFC defect fix Revision B iPhone X change over. How many of those 40 million are defective? Only Apple knows. My take is that almost all of them are defective over time, but iPhone X owners are not aware of the NFC defect until iPhone X NFC fails altogether.
Unless you like spending time and money repairing the notoriously difficult to repair iPhone X, I strongly urge you get a replacement from Apple if you can, or better yet upgrade to iPhone SE. The NFC just works and Touch ID is much better than Face ID when navigating the outside world wearing a face mask. You also get A13 Express Transit power reserve and background NFC tag reading that works great with iOS 14 App Clips. Altogether a much better Apple Pay package for our COVID face mask era.
All three fare systems are managed by Cubic Transportation Systems who also run the London Oyster and Sydney Opal systems. Cubic systems all use the same MIFARE smartcard technology but the interesting thing about SmarTrip and TAP is: (1) they are the first Cubic managed digital wallet transit cards, (2) neither system has implemented open loop fare payments for tap and go credit cards.
Ventra, Oyster and Opal all have open loop, and as of this writing Cubic has yet to deliver those transit cards on digital wallets. Why?
The SmarTrip/TAP Apple Pay launch gave us the answer that nobody wants to discuss: open loop support adds a layer of complexity and cost that stymies native digital transit card support. Complexity and higher cost means fewer choices, delays, and mediocre performance, simple as that.
Steve Jobs explained it best in his last public appearance. A great product or service comes down to focus and choices, either you can focus on making certain technologies work great on your platform versus just okay when you’re spreading yourself too thin. Ventra is spread too thin, that’s why Apple Pay Ventra and Google Pay Ventra are delayed more than a year after being announced.
Open Loop is sold as the cost effective future of transit ticketing but it’s had a surprisingly rocky time in the American market. The failure is pinned on transit companies but I think credit companies are to blame. The arguments for open loop are plastic era constructs that ignore how mobile digital wallet platforms and mobile apps have changed everything. For example the oft cited open loop benefit of plastic smartcard issue cost savings completely overlooks the cost savings of digital transit cards on smartphones.
It’s high time for the credit card industry to rewrite the open loop marketing script for the mobile era, but they don’t want to do that. Expect more of the same. In the meantime, let’s hope the SmarTrip and TAP Apple Pay rollout is a sign that Chicago will be getting Apple Pay Ventra soon.
Ruimin Yang’s detailed and thoughtful post, “Apple Pay monopoly, are we really comparing ‘Apples’ with ‘Apples?“, outlines the entire Apple Pay system architecture, how it compares to other digital wallet platforms, (Google Pay, Samsung Pay) and what ‘open vs closed’ means in the whole ‘Apple Pay is a monopoly’ debate. I highly recommend it if you have any interest in digital wallet payments.
As Yang explains, ‘open’ is not easily defined and the options are not easily implemented, especially when it comes to Apple’s highly customized and constantly evolving Apple Pay platform built around their A/S series chip Secure Enclave and Embedded Secure Element. Apple has spent a lot of time, money and effort in building the Apple Pay brand as the high benchmark standard for secure, private and easy to use digital wallet transactions and services. It is not your standard off the shelf NFC + Secure Element package.
It is telling that Germany, a country with one of lowest rates of credit card use and whose banks fought to keep Apple Pay out, is pushing for ‘open NFC’ the most. It sounds like an across the board move but it’s really aimed at Apple Pay.
This is European business politics in the age of digital wallet wars: mobile payments and digital wallets have disrupted everything and the traditional players, banks and card companies i.e. the real gatekeepers, are doing everything they can to keep the upper hand by using the open NFC argument to force their own branding on Apple’s platform in place of Apple Pay.
In the European tradition, regulation is invariably the go to strategy for keeping the status quo. I still think Junya Suzuki has it right: the EU would never demand the same thing of Samsung or Huawei that they are demanding from Apple. In other words, politics.
The first problem was the iPhone lineup. iPhone 8 didn’t fit because only A12 Bionic devices and later support NFC background tag reading. This was solved with the release of A13 Bionic powered iPhone SE and deletion of iPhone 8 from the lineup.
The second problem was the clunky ‘launch an app’ or ‘launch Safari’ to do anything. This has been a problem for NFC tag solution providers like SmartPlate. User interaction needs to reside on a task focused pop-up sheet while the screen is on. The new iOS 14 App Clips framework that works hand in hand with iOS 14 Core NFC to load just what is needed to take care of the NFC tag task at hand, is the right solution.
The pieces appear to fit very nicely now: the NFC background tag sheet pops-up ‘while the screen is on’, the right code snippets load in for a simple focused task, the user can Sign In with Apple ID if needed, and pay with Apple Pay. Simple, uncluttered action; no apps, no Safari launch. And we have background NFC tag reading on every current iPhone model.
There are a few flies in the ointment:
Face ID in the face mask era is a lousy unlock and Apple Pay user experience, App Clip powered NFC background tag reading is gonna rock on Touch ID iPhone SE even though it was designed for Face ID.
A network connection is required, Apple Pay transactions at the NFC reader work without a network connection but App Clips + Apple Pay transactions need a network connection for the obvious reasons of loading app clip content, and because of this…
A weak borderline WiFi connection can jam the entire process even with WiFi Assist turned on.
The NFC advantage over QR Codes here is that background tag reading automatically pulls up the App Clip sheet when the screen is on while QR Code users have to manually pull up the QR reader app and scan a code to join the fun.
The combination of App Clips, NFC tags and Apple Pay will be extremely disruptive in markets where NFC and QR payment players are very competitive. Places like Japan. PayPay and Line Pay lose their edge. Smart QR payment players can adapt and add NFC tag support in their payment apps. And they can bypass Apple Pay if they want to, though it won’t be as slick. Ultimately they are not wedded to QR codes, PayPay and Line Pay have always said they would add NFC if customers want it.
App Clips finally unlocks the power of background NFC tag reading and is the other big WWDC20 Apple Pay development in addition to CarKey and Apple Pay QR Code AliPay payments. App Clips puts NFC tags on equal footing with QR Codes for the first time with the added edge of the ‘when the screen is on’ background tag read sheet pop-ups. This will be huge.
As COVID restrictions are eased and the world slowly goes back to work, school and hopefully slightly more normal life, avoiding crowds will be key in keeping COVID from becoming resurgent in the months ahead.
For commuters in Japanese metro areas avoiding crowds is no easy matter. Fortunately the Japanese transit gate infrastructure is a great help. FeliCa based IC transit cards (Suica, PASMO, ICOCA, etc.) with fast transaction speeds combined with open gate flap design maximizes people flow: people walk through gates at normal pace. This is very important for Japanese stations that have to make do with large crowds in limited spaces and narrow gate areas.
It’s wrong however, to think that this only applies to Japan. The benefits of fast tap speed combined with intelligent transit gate design are relevant everywhere and very necessary in this day and age: fast gate tap speed is essential in keeping gate crowding at a minimum. It makes things safer not only for train operation, but also addresses crowd control health concerns in the COVID era.
A reader sent a link to a good discussion of NFC protocols and gate tap speeds that was apparently deleted when YouTube comments were turned off. I retyped the comment in the section below from a screenshot with some light editing for clarity. If I find the author I will link to the original. The videos have already appeared in other posts but it’s good have them in one place. A previous installment already covered QR transit code gate issues, this post will focus on NFC tap speeds.
While transit gates and NFC processors are found worldwide, what makes the Japanese gates different from the rest of the world is they don’t use global standard ISO 14443 (never mind Type A which uses Miller bit coding, the least efficient bit coding method) protocol which is common in many transit and bank cards issued worldwide.
The tap time with ISO 14443 Type A (née Philips) and B (née Motorola) varies greatly: from 200 to 500 milliseconds (ms) with 200 ms only achievable with Type B/Calypso. But it never reaches the short as 100 ms which is only achieved with Felica developed by Sony, also designated NFC-F and NFC Tag Type 3 by the NFC Forum and compatible with ISO 18092 which is commonly found in smartphones and NFC wearables since 2013. In this following video passengers maintain their walking pace but never overshoot and trigger a gate closure nor slow down not even a bit:
It may seem like a minor difference but due to the high volume of passengers per gate and to reduce gate maintenance requirements, tap times really matter.
Companies such as JR East have specified tap time of 200 ms but Suica is actually faster and this allows real life speed tolerances: some passengers tap faster than others due to walking pace, the higher speed tolerances are only possible with the 100 ms tap time of FeliCa. A comparison example of large crowds at gates in Malaysia and Japan below:
Open Loop NFC ticketing in its current form is based on EMVCo Contactless specifications adopted in contactless bank cards issued worldwide including China UnionPay QuickPass which is PBOC derived from the EMVCo Contactless spec. All of these use ISO 14443 Type A at 106 kbps only for 500 ms tap time, which is adopted in cities worldwide such as London, New York, Moscow and Rio de Janeiro where normal walking speed is never supported.
But as seen here, transit cards in Japan such as Suica, PASMO and ICOCA are supported for ultra hight speed and precise account verification and fare processing. Transit cards use offline Stored Fare (SF) which includes the amount of funds stored in the card’s IC smart chip data storage, NOT backend on a server like a bank card, and stored commuter passes. Here are walk flow comparisons for Tokyo and London, and MTA OMNY Open Loop performance:
As the videos make clear, tap speed is the most important part of the total package that makes a transit gate, from NFC sensor and antenna communication distance, to fare processing transaction software to physical barrier design. Be it an antiquated turnstile, a sliding panel, or a flap. A key reason for the ultra fast performance of JR East gates is Suica speed coupled with a larger antenna area plus the barrier-less transit gate design that doesn’t impede walk flow.
EMV is payment technology created for leisurely supermarket checkout, not whizzing through transit gates at rush hour. It doesn’t address the needs of transit and never will in its current format because it is tailored for, and controlled by credit card companies. One example is that EMVCo certification requires a small antenna communication distance, as in store reader communication distance. This is to prevent EMV skimming out in the wild, but the restriction doesn’t make sense for transit gates which operates in a controlled settings.
NFC Forum partners need create a single faster more reliable NFC standard encompassing NFC A-B-F and other wireless technologies, a new standard that improves and expands the NFC user experience on mobile devices for transit, digital identity keys and payments, while making it all future-proof.