Google Pixel NFC Bug Sends Tap to Pay Back to Plastic

A Google Pixel NFC bug is breaking tap to pay on phones from the Pixel 8 through the Pixel 11, including handsets already on Android 17 with current patches. Restarting brings the radio back. It often goes quiet again later the same day, at a checkout or a fare gate.

In the same month, Google Play services v26.35 taught Wallet to copy a physical transit card over NFC so the plastic could stay home. The phones now asked to carry that fare are the ones dropping the field.

A Red Screen at the Checkout

Owners began flagging the miss in the week of September 21, 2026. The phone is unlocked, Wallet is set as the default, and the reader still gets nothing, or it throws a red error after several taps. Digital passes in the same stack fail in the same window. Then a reboot makes the next tap work, which is why people keep thinking they imagined it.

The pattern is on-and-off, not a dead chip that never wakes. That is messier in a grocery line than a hard failure, because the first tap looks like user error. By the third try, the queue is watching. Closing Wallet does not bring the field back for long. The restart does, until later the same day, when the broadcast stops again.

Google was asked for comment on September 28, 2026. It has not published a cause, a tracking number, or a fix note on the Pixel contactless-pay pages.

Google Just Taught Commuters to Retire Plastic

On September 8, 2026, Play Services v26.35 added a Wallet path that reads a physical transit card with an NFC tap. The point of that path is to stop typing card numbers and to stop carrying the plastic. Guides for the feature walk through Add to Wallet, then Transit Pass, then hold the card to the phone if the agency supports the transfer.

WHAT THE NFC IMPORT COPIES

• Stored value: The remaining balance on the physical card moves into Wallet with the tap, not as a number you retype.
• Time-based passes: An active monthly or similar commuter pass tied to that card comes across in the same read.
• Chip metadata: The data a gate or validator needs so the phone or a paired watch can tap in place of the original card.

Those three items are why the new import is more than a bookmark. After the move, later taps are meant to come from the device. Feature guides also warn that the original card can stop working once the transfer completes, which is the usual rule when a fare chip is cloned onto a phone. Share that card with a partner or a child and there is no second copy. The phone is the copy.

That is the bind for anyone who already ran the import in September. A checkout miss is annoying. A fare gate miss, with the plastic already retired, is a blocked commute. Wallet’s new pitch was that you could leave the card at home. The reliable advice, until Google names a fix, is to keep it.

Four Pixel Generations, One Software Pattern

Google moved the NFC hardware on the Pixel 11 series to the top of the phone in August, and it said the change was for easier payments and for Tap to Share. On August 12, 2026, Tap to Share also began rolling to Pixel 6 and newer. The launch line put the new tag and the new gesture in the same breath.

Sharing with others is just as easy: Alongside an updated NFC tag at the top of the phone, Tap to Share makes it even easier for you to instantly swap contact cards or share large files with any nearby Android device with a quick tap.

Google, Pixel 11 launch

Owners who still press the camera bar into a reader, the way Pixel 10 did, will miss. Google publishes the labeled NFC sensor diagram for each Pixel, and the Pixel 11 drawing puts the sweet spot on the upper back, near the top edge. Tilt the top onto the pad and a healthy phone reads. That is a technique problem, and it is real.

It is not this week’s bug. The same dropout is showing up on Pixel 8, Pixel 9, and Pixel 10 phones, which never received the top-edge antenna. A reboot would not reattach a coil you tapped in the wrong place. Hardware diagnostics on at least one affected Pixel also passed NFC while payments still failed, which is the signature of a stack that has stopped broadcasting, not a cracked antenna.

The failure is also uneven, which is why a friend can tap beside you and look unconvinced. One reviewer in early September could not tap at all on a Pixel 11 Pro XL while a Pixel 11 Pro Fold on the same desk still paid. FeliCa and Suica are still a question mark; at least one Pixel 11 Pro in Japan was still completing taps on September 29, 2026, including Suica, while another owner wondered whether a failed Rakuten Edy read belonged in the same bucket. Samsung Wallet continuing to work on some Android phones is a reminder this may sit in Google’s pay stack, not in a dead NFC controller. None of those splits is a verdict from Google. They are why a fleet-wide hardware recall is the wrong first guess.

Which Builds Still Lose the Chip?

The most detailed software snapshot in the current wave comes from a Pixel 11 Pro XL owner who was already current and still losing taps. Other threads in the same week describe the same on-and-off pattern on older lines and on a Pixel 10a, with current patches in place.

WHICH PIXELS ARE IN THE REPORTS

Play Services 26.34.36 (260400-981326859) is not the v26.35 train that added the transit import. Treat them as different builds. The Pro XL snapshot also sat on the August 2026 Google Play system update. That still does not pin a module. It only shows that “install your updates” is not the cure, because the people filing these reports already did.

July’s Wallet Outage Already Had a Server Fix

Pixel tap to pay has already broken once under Android 17 in a way Google could patch without a full system image. On July 29, 2026, Wallet on some Pixel 9 and Pixel 10 phones began showing a “Phone doesn’t meet security requirements” error, even when Play Integrity checks passed. Cards vanished. New ones would not enroll. Clearing Play Services data and factory resets did not fix it. Google then deployed a server-side fix and told people to restart and wait up to 24 hours.

That outage and this one do not share a screen. July locked Wallet behind a security check. September lets Wallet open and then fails the tap. The useful overlap is narrower: both landed on current Pixel software, both needed Google to move, and both made a reboot look like a fix while the real work happened somewhere else. A public tracker entry from the current wave at least shows the pay stack is already under a ticket.

THE NFC CALENDAR INSIDE PIXEL AND WALLET

1. July 29, 2026: Google ships a server-side fix for an Android 17 Wallet error that blocked tap to pay on some Pixel 9 and Pixel 10 phones and tells owners to restart and wait up to 24 hours.
2. August 12, 2026: Tap to Share begins rolling to Pixel 6 and newer, using NFC to start a share.
3. August 13, 2026: Google confirms the Pixel 11 series carries an updated NFC tag at the top of the phone for payments and Tap to Share.
4. September 8, 2026: Play Services v26.35 adds NFC import of physical transit card passes and balances into Google Wallet.
5. Week of September 21, 2026: Owners on Pixel 8, Pixel 9, Pixel 10, and Pixel 11 lines report on-and-off contactless pay and passes.
6. September 22, 2026: A September 22 tap-to-pay ticket on Google’s public tracker lists Play Services 26.34.36 (260400-981326859) on an Android 17 beta Pixel and describes payments as unusable.
7. September 28, 2026: The multi-generation dropout is written up more widely. Google is asked for comment and does not issue a public note.

The September 22 ticket is a software-requirement complaint on a beta build, not a signed confession that 26.34.36 killed the field on every Pixel 8. It is still the same Play Services version string the Pro XL owner posted, in the same week the Reddit threads filled up. That is as close as the public record gets to a fingerprint.

A Restart Fades Later the Same Day

Until Google posts a patch, the working playbook is ugly and short. It is also the only one owners have that actually restores a tap.

WHAT OWNERS HAVE ALREADY TRIED

• Full restart: Restores NFC for a stretch, then the chip stops broadcasting again later the same day.
• Force-close Wallet: Does not hold as a fix; the miss returns without a reboot.
• Latest system and Play patches: Already present on the detailed Pro XL report and on other current-patch threads, so they are not protective.
• Hardware NFC test: Can pass while tap to pay still fails, which is why a repair shop visit is a weak first step.
• Keep the plastic: A physical payment card and, if you have not already transferred it, the original transit card still clear a reader when the phone does not.

Google’s own help still describes how a Pixel is supposed to tap and pay: NFC on, Wallet set as the default, a screen lock in place, and a card that has finished setup. Those pages also warn that a wallet-style case packed with other NFC cards can keep the sensor busy and block a real tap. If a reboot restores payments for hours, a noisy case is not your problem. The radio came back. Then it left again.

WHAT WE KNOW

• The span: Reports cover the Pixel 8, Pixel 9, Pixel 10, and Pixel 11 lines, not one factory batch.
• The workaround: A restart restores taps for a while and then fails later the same day.
• The software state: Affected phones include fully updated Android 17 builds and current Play Services.

WHAT IS UNCONFIRMED

• The module: No public note names Play Services, the August Play system update, or Android 17 as the trigger.
• The count: There is no official tally of how many Pixels are dropping NFC.
• Japan e-money: FeliCa, Suica, and similar taps are not cleanly in or out of the bug.
• A silent patch: Google has not said whether another server-side fix, like July’s, is already rolling.

If you have not transferred a transit card, do not do it while taps are this flaky. If you already did, treat the phone as the only copy of that fare and keep a backup ride payment you can still hold in your hand.

Google Has Not Named a Cause

The contactless help pages still read like a setup guide, not an incident note. There is no banner about a known NFC dropout, and no system-services line that admits a pay-stack regression. The public tracker has pay and NFC tickets from the same stretch of September, including the September 22 entry that already carries 26.34.36 (260400-981326859). Assigned is not fixed.

July showed Google can repair Wallet from its side and ask for a restart plus a wait. This dropout may get the same treatment. It may need a Play Services package. It may need a Play system update. Owners cannot tell from the phone, because the only control that changes the outcome is the power button, and only for a few hours of clock time before the field dies again.

Until a named fix lands, the card Google spent September teaching people to put away is still the tap that works at the end of the line.