Press "Enter" to skip to content

The new Google Pay repeats all the same mistakes of Google Allo

Aurich Lawson / Ars Technica

The new Google Pay app came out of beta this week, and it marks the first step in a major upheaval in the Google Pay service. Existing Google Pay users are about to go through a transition reminiscent of the recent move from Google Music to YouTube Music: Google is killing one perfectly fine service and replacing it with a worse, less functional service. The fun, confusing wrinkle here is that the new and old services are both called “Google Pay.”

Allow us to explain.

The old Google Pay service that has been around for years is dying. The app will be shut down in the US on April 5, and if you want to continue using New Google Pay, you’ll have to go find and download a totally new app. NFC tap-and-pay functionality won’t really change once you set up the new app, but the New Google Pay app won’t use your Google account for P2P payments anymore. You’ll be required to make a new account. You won’t be able to send any money to your new contacts until they download the new app and make a new account, too. On top of all that, the Google Pay website will be stripped of all payment functionality in the US on April 5, and New Google Pay won’t support doing anything from the web. You won’t be able to transfer money, view payment activity, or see your balance from a browser.

In addition to less convenient access and forcing users to remake their accounts, New Google Pay is also enticing users to switch with new fees for transfers to debit cards. Old Google Pay did this for free, but New Google Pay now has “a fee of 1.5% or $.31 (whichever is higher), when you transfer out money with a debit card.”

Google is currently sending out emails to existing users detailing all this. There’s also a support page link and a notice at the top of On the Play Store, Google has already started hiding the old Google Pay app from search results, renamed it “Google Pay (old app),” and updated the app home screen with a message to sign up for the new app.

New Google Pay’s Internet-hostile design

We’ve spent some time with the new Google Pay app now that it’s out of beta, and Google looks like it is repeating all the same mistakes it made with Google Allo, one of Google’s biggest messaging-app flops. Google Allo was the messaging app that was released in 2016, a few years after Google Hangouts. The service represented Google’s attempt to clone WhatsApp after losing an acquisition bidding war with Facebook two years earlier. Like New Google Pay, Allo debuted in India and was laser-targeted at the country before being forced on the rest of us for some reason. Allo was thoroughly rejected by consumers and was dead in the water after four months of availability. It was shut down after about two years.

Just came in:  Samsung in a hole again as photo remaster gives disturbing results

In Google land, targeting an app at India means building an Internet-hostile design that ignores existing Google infrastructure, data, and contacts, and building something powered entirely by the carriers’ SMS system. New Google Pay, like Allo, doesn’t use your Google account (at least, not for payments). Instead, you have to sign up for the new Google Pay using your carrier’s phone number. None of your existing Google Pay contacts will carry over, and they’ll all have to sign up for new accounts with their carrier phone numbers, too. Making payments entirely SMS-driven theoretically makes signing up for the service easier in India, but in the rest of the world—where people interested in a Google service generally have a Google account and multiple devices—it’s more inconvenient compared to rival services.

Just like with Google Allo, SMS-based authentication means there’s no desktop support at all. The Google Pay website is being stripped of all its useful functionality because a browser does not have a carrier SIM card and therefore can’t be authenticated by the SMS-reliant system. Google Allo eventually copied WhatsApp and came up with a clunky, QR-code-driven browser login process that forwarded your phone access to the browser (and didn’t work if your phone was off/dead/missing). Google Pay could eventually cook up something like that, but that seems like a heap of work for what should be (and used to be) a quick money transaction.

Enlarge / SMS-based apps like Google Pay only support one device at a time.
Ron Amadeo

The other SMS-based limitation of Google Pay is that you can only be logged in on one device at a time, just like Allo. This is less of an issue for a payment app, but the old version of Google Pay worked on smart watches, too. If Google ever wants to revive its wearables segment, this seems like a bad limitation.

Basically, everyone is being kicked off the old Google Pay service, and you’ll all have to join and reconnect on this new thing. Like with YouTube Music, this is a great chance for Google to lose users as they are forced to re-evaluate their app choices and set up something new. There’s a possibility that users move to a different, more stable, more respectful platform. This move also kills the synergy between NFC tap-and-pay Google Pay and Send-money-to-people Google Pay. The two services, both in a single app, now use completely different log-in methods: Google Pay NFC on the new app still uses your Google account and will carry over your credit cards.

Just came in:  Bing’s showing ‘AI-generated stories’ in some search results

SMS identity is not a completely unworkable solution, but it’s definitely not the future we should be pushing for, when regular account systems are free, more accessible, and much more stable. I know you technically don’t own anything on any company cloud service, but a phone number, which is tied to a bill and your ability to pay, feels a lot more temporary than something like an email address. I am sure there are people who have had the same phone number for many years, but that only happens if you constantly pay the bill, every single month, for years. You’re also trusting the notoriously bad billing and customer service departments of your local cell phone carrier to do the right thing and screw you out of your phone number for some dumb reason, which has definitely happened before. You might even have a moral argument that tying identity to your ability to pay a bill is wrong.

The other problem with SMS is that it’s considerably easier to get Internet service than it is cell service. In a Venn diagram of Internet access, cell phone service is a smaller circle inside a bigger “Internet” circle, which also has options for wired Internet from your local ISP. For instance, my parents live in a cottage in the woods and don’t get cell phone service, which has never been a big deal thanks to wired services. But they would have to leave the house to set up Google Pay. We’ll probably switch to something else.

It’s OK to treat different parts of the world differently

This upcoming “new Google Pay” app got its start in India, where Google first launched the service as “Google Tez” in 2017. India is Google’s second-favorite country after the US, not just because it’s the birthplace of Google CEO Sundar Pichai but because India is the world’s second-most populated country and, therefore, has great potential for user growth. The world’s most populated country, China, would be a great growth target, too, if not for all the difficulty involved in working with the Chinese government. Google has mostly stayed away from China and focused on India.

Tez was rushed out in India to plug into the country’s new Unified Payments Interface (UPI), a government-backed interoperability standard for money transfers that launched in 2016. Today, UPI does 2 billion transactions a month in India, and the New Google Pay/Tez handles something like 40 percent of those transactions.

Tez was renamed Google Pay (Tez) in 2018 and got a ground-up rewrite in 2020. It’s this app that is being pushed on users as the new Google Pay, and you can still see this history in the Play Store package name, “” “NBU” stands for “Next Billion Users,”—Google’s growth initiative for the developing world—and “paisa” is an Indian penny, a defunct coin worth 1/100 of a rupee.

Just came in:  Elon Musk reportedly tried and failed to take over OpenAI in 2018
Enlarge / Google wants unified apps across the entire world, but Facebook is fine with designing different apps for different places. Facebook WhatsApp and Messenger dominate this messaging world map.
We Are Social

Like with Allo, India (or maybe the developing world, at large) has so many different user concerns and feature requirements that it’s not clear why Google occasionally wants to push developing-world-style apps on the rest of the planet, especially when the app was originally built around India-only features like UPI. Certainly, you would want apps to be popular in a nationwide capacity, but there’s not a huge benefit from unifying an app across the entire world.

Facebook takes more of a split-world approach to its app design, which I think works better. If you look at Facebook Messenger and WhatsApp, Facebook builds one app, WhatsApp, with a focus on SMS and single devices, while Facebook Messenger does a better job supporting desktop websites, existing accounts, and multiple devices. If you think messaging apps are somehow not a good comparison point for payment apps, consider that in Facebook Land, these two apps are the same thing. WhatsApp and Facebook Messenger both have “send money” features.

If you look at the above messaging world map, Facebook dominates partly thanks to this strategy of having two different designs for different parts of the world. Google is pushing out New Google Pay in the US, but even hyper-popular, billion-user apps can’t make this one-device, SMS style work in the states.

More transitions to explain to your friends and family

For long-term Google users, the new Google Pay is yet another annoying transition they’ll have to explain to friends and family. This is an occurrence that’s getting more frequent and more annoying in recent years, thanks to similar Google shutdowns of Google Play Music, Cloud Print, Inbox, Works with Nest, the ongoing Hangouts situation, and many others. That’s to say nothing of the crazy history of this payment service, which used to be Google Wallet, then Android Pay, then Google Pay, and now it’s a totally different Google Pay. Just like we’ve been through a million times now, some people won’t think this is a big deal because their use case is supported on the new product, while for other people, the new Google Pay will be a much bigger deal, because their use cases will be ripped-out from under them and no longer supported.

The worst part of it all is that, like the move from Google Music to YouTube Music, there is no reward at the end of this transition. Google is blowing stuff up and making users switch apps and set things up again only because of internal politics and infrastructure concerns. There aren’t any great new features to sell people on—it’s just Google’s constantly shifting priorities reaching into your life to remind you, “This is what being a Google user is like now. You’d better keep up!” It gets exhausting.

There is one new feature in the new Google Pay. I swear I’m not making this up: new Google Pay is yet another Google messaging app! Once you add someone via their phone number, the three options are “Pay,” “Request,” and “Message.” The “Message” option will bring up a full messaging app with the usual back and forth replies, push notifications, and emoji support. You can even start a group chat!

Let’s block ads! (Why?)