By Stephen Schenck | June 29, 2012 5:07 PM
Google Wallet is in a tough spot. Google hasn’t been able to get most carriers in the US interested in letting their users access the service, and where it has been available, it doesn’t look like things will remain that way for much longer. Clearly, something needs to change if Google wants to see a continued role in the mobile payments game. At Google I/O this week, the company announced some new APIs to better integrate Wallet with websites, but will the changes be enough to get more people using Wallet, and could that prove sufficient to start turning the tide for the service?
Save to Wallet is Google’s API for letting users interact with their Wallet accounts through third-party websites. One way Save to Wallet will work is by letting sites that sell prepaid value cards enable users to directly add them to their Google Wallet accounts, straight from the merchant’s site. That’s a nice convenience, but we’re more interested in the API’s ability to let you save offers to your Wallet. That way, when you’re browsing the web on your home or work PC, and you see some deal that sounds tempting, you’ll be able to click on an icon and send the details of that offer right to Wallet on your phone. With the right promotion, we imagine that could go a long way towards drumming-up interest in using Wallet.
Problem is, we’ve still got the carriers to deal with, and it would take some very vocal complaints from a large number of users to get them to even consider changing their ways. With Isis, and now Sprint’s rumored system, they’re all heavily invested in monetizing mobile payments, and won’t be likely to give up the shares they’re expecting without a fight. On the other hand, if Google keeps selling unlocked phones, like it’s gotten back in to, that could stand to become less of an issue for the company. Focusing on non-US markets could also help build the Wallet user base, but we fear Google’s still got its work cut out for it.
Via: Android Central