Why Google is bending to Verizon over Google Wallet
Google has complied, so far, with Verizon Wireless's request to withhold the Google Wallet mobile payments service from the new Galaxy Nexus phone. — Why? — Because Verizon is a very important partner for Google …
Context & Ripple Effects
The relationship at stake goes back years: Verizon embraced Google's Android in late 2007 after the two were first reported in talks, and by August 2010 the pair had reportedly struck a deal on web traffic rules — making Verizon arguably Google's most important US carrier partner. On December 5, Computerworld confirmed the concrete symptom: the Verizon Galaxy Nexus ships without Google Wallet support, though it will still receive Google updates.
SplatF's December 8 analysis supplies the why: Verizon asked Google to withhold Wallet from the device and Google has complied so far, because the carrier relationship is worth more to Google than forcing the payments service onto this one phone. The episode turns an abstract question — who controls which Android features ship on which network — into a visible concession.
First-order effects
- Buyers of the Verizon Galaxy Nexus get the flagship Android phone without Google Wallet, so Google's NFC payments service loses its highest-profile launch vehicle on the largest US carrier.
- Google concedes feature-level control on its own platform: Wallet's availability is now demonstrably subject to carrier veto rather than guaranteed by Android.
Second-order effects
- Other carriers now have a template for extracting the same concession, meaning Google must negotiate Wallet's rollout phone-by-phone and network-by-network instead of shipping it universally through Android.
- Any rival mobile-payments effort aligned with the carriers gains protected distribution space on devices where Wallet is withheld, shifting the competitive fight from software quality to preload access.
Third-order effects
- If the pattern holds, US mobile payments adoption fragments along carrier lines rather than consolidating around a single Google-led standard, slowing the shift away from cards.
- More broadly, the episode shows that owning an open-source OS does not guarantee control of what reaches users — distribution gatekeepers can still veto individual services, a structural tension between Google's platform ambitions and its dependence on carrier partnerships.
The trend: Carrier gatekeeper power over Android is resurging, letting distribution partners veto individual Google services even as Google pushes its own apps onto every handset.