Play Services 26.28 and Tap-to-Pay: Why Some Android Phones Lose NFC Payments

When tap-to-pay stops working, the instinct is to blame the radio. A report that circulated on r/Android points somewhere else: after a Play Services 26.28.xx update, owners of phones running Chinese-market firmware found that NFC still read tags and transit cards, but payment apps would not complete a transaction. A radio that reads a tag is a working radio, which leaves the layer above it - the device check a bank app performs before it authorises a payment.

That distinction decides what is worth trying. If the hardware is fine, then clearing caches, reinstalling the bank app and factory resetting are all attempts to fix the wrong layer, and some of them cost you more than they return.

Reading the symptom correctly

The table is ordered by how cheap the test is, not by how likely the cause is. Confirming the radio takes ten seconds with a transit card and eliminates half the possibilities before you touch a single setting.

Confirming it in six steps

1. Step 1 Prove the radio works

   Hold the phone to a transit card, a hotel key or a plain NFC tag. If something reads, the antenna and controller are doing their job and the problem is above them.

2. Step 2 Check Play Protect certification

   In the Play Store, open Settings, then About, and read the certification line. An uncertified device can install apps and still fail the checks that payment apps rely on, which matches the symptom exactly.

3. Step 3 Check the default payment app

   In the phone's NFC settings, confirm which app is set to handle tap-to-pay. An update can leave the setting pointing at an app you no longer use, and the terminal then fails without an error that explains why.

4. Step 4 Clear the payment app's cache, not its data

   Cache is disposable. Data holds your card token, and clearing it means re-verifying the card with the bank, which is a slow way to learn that the cache was never the problem.

5. Step 5 Rule out modifications

   Root, an unlocked bootloader, a custom ROM or a sideloaded system image can all fail an integrity check on their own. If any of those apply, no amount of app reinstalling will change the outcome.

6. Step 6 Return to stock firmware for your exact model

   If the phone was converted from another region or runs a modified system, restoring the certified build for that model is the only local fix with a real chance. Back up first: this step erases the device.

What does not help, and why

• Clearing Play Services data: it signs accounts out, resets settings, and cannot change a decision made on a server.
• Sideloading a "certified" fingerprint or a props module: it may pass one check while breaking banking apps, over-the-air updates and the warranty.
• Flashing another region's firmware: on some Samsung devices it trips Knox permanently, and on any device it can void the warranty.
• Factory resetting first: it only helps when a modification is the cause, and step 5 rules that in or out in a few minutes.
• Waiting for the next Play Services build: possible, but there is no published schedule that tells you how long to wait.

Did Google actually ban Chinese phones?

What the report describes is a device check failing on certain firmware builds, with owners reasonably reading that as a ban. NFC still reading a tag is the evidence that the hardware is not the issue. Whether the change was a deliberate policy or a side effect of a certification update is not something the thread settles, and both explanations deserve to be treated as open.

Will a factory reset bring tap-to-pay back?

Only if a modification on the device was failing the check. A reset cannot change a decision made on a server, which is why it belongs after the cheap tests rather than before them.

Can I still pay contactlessly in the meantime?

Your physical card still works, and most banks offer their own in-app or QR payment route. A paired wearable may also be unaffected, because the payment token lives on the watch rather than on the phone.