In the spirit of bug fixing, Google has started a push of the latest version of Android Pay to users with a rollout of version 1.1 that began today. Of course, like all app updates whether big or small, just because it has started rolling out to users today doesn’t mean that every user will see the update before the day is over. Having said that, you can optionally choose to download the apk file and install it that way if you so choose which will make it faster for you to have a version of the app which may be free of bugs that were plaguing you previously.
With version 1.1 Google has made it easier for people to find out what banks actually are compatible with Android Pay at the moment, and for anyone who wasn’t already aware and are curious to see if their particular banking institution supports Android Pay, there is now a new option inside of the overflow menu where you can tap to see participating banks. There isn’t a large collection of banks that support Android Pay at the moment, but this could certainly become even more useful once more institutions allow use of the app with their credit and debit cards. How long that may take resides on partnerships between those banks and Google.
There is also now a fix for an issue that was causing some users to miss their loyalty cards after having set up Android Pay on any device after the first one they initially configured it for. Essentially what was happening is that users who initially set up Android Pay on one device and then installed it on other devices afterward, weren’t able to see their loyalty or membership cards on those other devices until after they had added in their payment cards. Not all users were having this issue with version 1.0, but loyalty cards were supposed to show up in the app regardless of whether there was a payment card associated with it or not. Lastly it appears that Google is now going to asking users whether or not they’d like to “stay in the loop” on special offers through email, with alerts asking users in-app at some point.