A few months ago, tap-to-pay quietly stopped working on imported Xiaomi, vivo and OPPO phones. Google Wallet opened fine and the cards were still listed. The failure only showed up at the register. Every affected phone was built for the Chinese market.
So what actually happened?
The story starts with an update. In August, Google shipped Play Services 26.28. It is the background package Android uses for everything from location to payments. Within days, XDA Forums filled up. Owners of imported phones were comparing notes.
One developer, posting as MarvinFS, pulled the service logs and found a line that spelled it out.
The log read TapAndPay: deviceSupportsTokenization: CN SKU. Translation: the software had identified the phone as a unit built for the Chinese domestic market, and it switched off the card-payment service in response. No error. No warning. The wallet just went dark at the terminal.
The affected list grew fast once people knew what to look for. Vivo’s X200 Ultra, X300 Pro, X100 Ultra and both X Fold models appeared in reports, along with the OPPO Find N3 and Find X9 Pro, the Xiaomi 17 Ultra, the Xiaomi 13 Pro, and a pair of OnePlus models. Reports came in from Europe and Brazil as well as Asia, which suggests the trigger was where the phone was made, not where it was used.
Here is the part that stings. Those phones had passed Play Integrity, Google’s own certification check for a healthy, approved device. They had run tap to pay for months, some for years. Nothing about the hardware changed. One background update flipped the switch.
And Google never said a word about it. No statement, no changelog note, nothing to read.
Weeks later, most wallets started working again. The fix looked server-side, not anything users did. If you never touched a China-market phone, you probably missed the whole saga. That is exactly the point, though. A check you cannot see decided who got to pay.
Why does the payment layer break in ways that bands and batteries do not? Because it is not really on the phone. The bank tokenizes your card, the store terminal challenges the device, and a server at Google sits in the middle making a yes-or-no call. Bands are physics. Payments are policy.
And that is why this problem will not stay rare. More of a phone’s behavior moves to server-side decisions every year. Updates arrive whether you asked for them or not, and the server’s opinion outranks your settings. I would rather own hardware that fails in dumb, physical ways.
Is the global version actually worse, then? Mostly no. The same silicon ships in both, tuned slightly differently for each market. You give up a little battery tuning and some camera processing. You keep the parts that require someone’s permission to run.
Every checkout since I read those logs, I have thought about the beep differently. A declined tap used to mean a bank problem. Now it might mean your phone’s birthplace. Nobody signs up for that kind of mystery.
The invoice proves nothing. The box proves nothing. Only the firmware on the phone knows where it was born.
Where does that leave resellers who promise US-ready Chinese phones? I would read the phrase as marketing until proven otherwise. Ready means the bands work. It does not mean the wallet works, and the wallet is what you touch every day. Ask for the exact firmware build in writing, then check it against the maker’s own spec page.
There is a quiet upside worth noting, though. Server-side checks also mean server-side fixes. When Google backed off, nobody had to flash anything. The same pipe that can block you can unblock you. That is cold comfort during an outage, and it still beats a permanent hardware-level ban.
Can you do anything about it?
Three workarounds made the rounds. The simplest came from another XDA user: open the Play Store, dig into settings, and leave every beta program you are enrolled in, even the ones you never remember joining. Notebookcheck’s editor tried that on his own affected vivo and tap to pay came back within a minute.
The other two are heavier. Rolling Play Services back to an older version requires ADB commands from a computer, and it wipes every card out of the wallet, so you re-add them all. The third route is to promote a different wallet to default tap-to-pay duty and route around Google entirely. Curve is the one people picked, and it works, with a catch. Its support is slow, and users report accounts getting frozen for weeks over flagged transactions.
My read on the episode: the app and the card list were never the real check. Certification is. A phone can look perfectly set up and still fail at the moment that matters, because the decision lives in a server-side switch you cannot see and cannot argue with.
So before you import a phone built for another market, price the payment problem, not just the price gap. Tap to pay is a daily habit in most US cities now. Transit gates use it. So do vending machines, parking meters and half the food trucks in town.
Run the rough numbers before you dismiss that. Import savings on a flagship often land around 10 to 20 percent, call it one to two hundred dollars on a mid-teens phone. A week without a working wallet is an annoyance. A month of it eats the discount whole.
And there is a version of this that could repeat. Google never explained whether the block was a bug, a test, or a policy in progress. All three readings point the same way. The switch exists, and someone can flip it again.
What would I actually check before buying a Chinese phone for US use? Four things, in this order. Whether the listing says global ROM or China ROM, because the firmware decides more than the language. Whether tap to pay has been confirmed working by real owners of that exact variant, not assumed.
Then two more. Whether your carrier needs the phone on an IMEI whitelist. And whether the seller accepts returns from your country, because a return across an ocean is a refund you argue about for a month. I would rather pay 10 percent more to a seller who answers email.
If you are weighing an import right now, I keep the full compatibility checklist in the complete guide to running a Chinese phone in the US. Payments deserve a line of their own on that list now, next to bands and VoLTE.
The rest of the trade-offs are less dramatic. I covered why Chinese phones carry bigger batteries a while back, and that part works exactly as advertised. It is the invisible layers, payments and provisioning, that bite.
So my advice stands, with one edit. Buy the hardware for what it does well. Buy the global version for everything the servers decide.
