#taptopay — Public Fediverse posts

My growing retired-transit-card collection

A year ago, this week’s work trip to the Bay Area would have meant breaking out the oldest computer that I was still using with any regularity at the time: the Clipper card that I bought in June of 2012 to pay for fares on BART, Muni and other transit agencies around San Francisco.

But this year, I could leave that NFC-enabled smart card in the little holder in which I store my other stored-value transit cards and instead tap my phone to pay with my business credit card for each ride–first a SamTrans bus from SFO to Millbrae, then Caltrain to San Jose for TechEx North America, then two days of commuting up and down the peninsula for Google I/O.

BART started accepting contactless payments last August, and now all the Bay Area transit services that accept Clipper cards also let you tap to pay with a phone, a smartwatch or a credit or debit card with an NFC chip.

Whether you call it “tap to pay,” “open payments” or “open loop,” letting people pay for a fare as if it were any other on-the-go purchase is a great advance for transit. Especially for out-of-towners, as I realized years ago when visiting Chicago and Portland and appreciating the early lead of their transit services in this key bit of CX.

A growing array of agencies across the U.S. have finally wised up to this after years of requiring people to buy proprietary stored-value cards, install agency-specific apps or make a throwback cash payment: Metro, NYC’s MTA, the T in Boston, NJ Transit buses and light rail, SEPTA around Philadelphia, MARTA in Atlanta, and the Seattle region’s Sound Transit, among many others.

L.A.’s Metro has been a high-profile laggard–a personally inconvenient one since my TAP card expired last year. But this week users have begun reporting success on Reddit and in Bluesky posts with using their phones and credit cards to cover train and bus fares now that Metro there seems to have begun a soft launch of what it calls “TAP Plus.”

As I’ve spent down the balance on transit cards I no longer need, the ones that I still need to use are now most entirely confined to agencies in other countries. Some examples: I love Barcelona’s Metro but I don’t love how it doesn’t support tap to pay; Doha’s driverless metro is a technological marvel but also requires its own colorful card; Vancouver’s Compass Card offers enough of a discount over tap-to-pay rates (because that city didn’t follow Toronto’s fare-neutral example) that I picked up one for last year’s Web Summit conference there and used it again for this year’s event.

But there is one awkward exception right in my neighborhood: Arlington Transit, which continues to require the SmarTrip card that WMATA rolled out in 1999. So while I can pay for Metro like it’s the 21st century, I still have to keep my well-worn SmarTrip card handy in case an ART bus rolls up before a Metro bus does.

Apple ha lanciato Tap to Pay su iPhone in Nuova Zelanda, consentendo agli esercenti di accettare pagamenti contactless direttamente con un iPhone XS o successivo. I clienti possono pagare con carte contactless, Apple Pay e altri wallet digitali. #Apple #TapToPay #NuovaZelanda

Three weekends ago, my phone did something weird when I tried using it to pay for a few farmers-market purchases: nothing. The Google Wallet app functioned like usual when I opened it and picked the credit card I use for everyday spending, but then tapping the phone to the NFC reader on a merchant’s credit-card terminal yielded no response.

Since all my cards have NFC built-in and since I had my wallet on me, I didn’t waste time trying to debug the problem and just fished out the physical card to complete the purchase. And then I spent a couple of weeks ignoring the problem while it failed to go away on its own.

Venting about this issue on a chat thread with other tech journalists surfaced a troubleshooting suggestion I should have thought to test on my own: see if other apps using the phone’s NFC radio work. I first remembered that I have one weird transit app that solely exists to top up Dublin’s stored-value Leap card, then was relieved to see the app detect the card I’d collected two summers ago when I tapped it to the back of the phone.

Likewise, Metro’s SmarTrip app responded to a tap of my own card. And then on Friday, the Epic Pass app on my phone (yes, I finally got that activated) functioned properly as a wireless, inside-a-ski-jacket lift ticket. So the NFC radio on this phone was clearly fine.

What else could it be? Google’s r/GooglePixel forum surfaced posts reporting similar problems, and one not only reassured me that I wasn’t uniquely snakebit but pointed to a specific remedy that I’ve since seen suggested elsewhere: deleting the cache of the system-level NFC Service app.

Following that required a deeper dive than usual into Android’s Settings app: Tap Apps, tap the “See all” link below the list of recently-opened apps, tap the vertical-ellipsis button at the top right and select “Show system,” then scroll down to select “Nfc Service” (yes, that abbreviation for “Near Field Communication” should be capitalized), then tap “Storage & cache,” then tap “Clear cache.”

“Trash cache” is an old tech-support trick that seems like it shouldn’t work anymore–shouldn’t apps be sufficiently self-aware to know when they’re ingesting corrupted temporary data?–and yet it seems to have worked in this case. Will the fix stick? I sure hope so, at least until the next time Google indulges in yet another mobile-payment-apps reorg.

https://robpegoraro.com/2024/02/23/this-months-smartphone-snafu-wayward-google-wallet-behavior/

#EpicPass #GooglePay #GoogleWallet #GPay #LeapTopUp #mobilePayments #NFC #Reddit #SmarTrip #tapToPay