US carrier Verizon Wireless will not be supporting Google’s m-commerce app Google Wallet when it launches the first Android 4.0 device. Verizon is rumoured to be launching the Samsung Galaxy Nexus in the US market later this week, but Google has confirmed that the carrier has asked it not to include the mobile app in the handset.

Dawinderpal Sahota

December 7, 2011

1 Min Read
Verizon Wireless won’t put Google Wallet in Galaxy Nexus
Verizon'a Samsung Galaxy Nexus will not support Google Wallet

US carrier Verizon Wireless will not be supporting Google’s m-commerce app Google Wallet when it launches the first Android 4.0 device on its network.

Verizon is rumoured to be launching the Samsung Galaxy Nexus in the US market later this week, but Google has confirmed that the carrier has asked it not to include the app in the handset.

Verizon was keen to stress that it is not “blocking” the application – contrary to what reports in the US have stated – as the operator “does not block applications”. Rather, it said that it is just not making it available until it can offer “the best security and user experience”.

“Google Wallet is different from other widely-available m-commerce services,” said Jeffrey Nelson, a spokesperson for Verizon.

“Google Wallet does not simply access the operating system and basic hardware of our phones like thousands of other applications. Instead, in order to work as architected by Google, Google Wallet needs to be integrated into a new, secure and proprietary hardware element.”

One reason for Verizon’s stance could be its own m-commerce interests. Verizon and rivals AT&T and T-Mobile USA are part of a consortium called ISIS, which is planning to launch its own payment system in the US soon.

Earlier this year, Google launched its Nexus S handset which also incorporated Google Wallet, however the app was supported on Sprint’s devices but not on T-Mobile/AT&T’s. The service on Sprint’s Nexus S appeared to work without any problems.

Meanwhile, Verizon claims that it is continuing ongoing discussions with Google on the issue.

You May Also Like