This is why Android Pay is asking you for a 'Google Payments PIN' when making purchases

When Android Pay finally arrived to replace the withering-on-the-vine Google Wallet, everyone rushed to get their cards into the app. Those who had a "supported" card from a bank that was in partnership with Google for the launch had a solid experience — tap your phone, and you paid. Anyone who added an unsupported card faced a new hurdle, having to both use a secure lock screen and enter a "Google Payments PIN" code at the time of payment. One extra tap and interaction with the screen, making Android Pay surprisingly less useful.

That's confusing, and Google's (lack of) explanation on the topic isn't helping the situation. We're going to explain what's going on here, why you're being asked to use a PIN code for payments and ultimately what you can do to avoid that.

The Google Payments PIN

Android Pay is technically only supposed to allow use of "supported" cards from a select handful of banks, and that's done for good reason. When working in partnership with banks and card issuers Android Pay can be more secure, letting your phone talk directly to the bank for transactions, and more useful, with data for things like reward points and detailed transaction histories. And when you have a card from one of these supported banks (check the latest list from Google here) in Android Pay, it's amazingly seamless to make payments. Just unlock your phone, tap the terminal and you just paid.

Confusingly, though, Android Pay actually lets you add unsupported cards to the app as well.

This is a hold over from the old days of Google Wallet, which had an entirely different system that worked without the cooperation of the banks. With Google Wallet, every time you made a transaction it actually made that purchase with a virtual prepaid debit card from "Bancorp Bank" and then that same amount was subsequently charged to your own bank. It was clunky, less secure and downright confusing to everyone involved — and the most annoying user-facing part of this system is the need for an extra PIN code to make a payment.

As Google Wallet hands the reigns over to Android Pay in this transition of mobile payments, this legacy system of using an unsupported card is actually still baked into Android Pay — though Google isn't exactly promoting it as such. This is partially due to the fact that you can bring previously-used debit and credit cards from Google Wallet into Android Pay, and partially because Android Pay just doesn't support that many banks yet — just 10 at the time of writing.

Whether the ability to add an unsupported card should be there or not, it still is and it leads to a rough experience. When you use an unsupported card in this way with Android Pay, it necessitates having a "Google Payments PIN" number as part of the transaction — unlock your phone, tap the terminal, enter a PIN, tap the terminal again. That's not a great experience, and it gives a terrible view of Android Pay to those who only have unsupported cards in the app.

How to avoid needing a separate Payments PIN

This is pretty simple, actually. If you want the absolute best Android Pay experience, which includes not having to enter a PIN, you just have to use a supported card and bank in Android Pay. Google lists all of its supported partners, but you can always tell whether your card is supported by opening up the Android Pay app, tapping the card in question to see its details and looking for the "Change Google Payments PIN" option. If the option is there, the card isn't fully supported. No option? You're good to go.

Most importantly for this whole situation, Google is only allowing you to add unsupported cards to Android Pay for a limited time. Google's own support pages explain it simply — "For a limited time, you'll be able to use some cards with Android Pay that your bank doesn't yet support in the app." We don't know how long that'll be, but we have to say it'd be best to rip this band-aid off early and get it over with. Using Android Pay with a supported card is a great experience, and everyone should experience it that way.

If you don't have a supported card right now (or more importantly, when Google flips the switch to turn off unsupported cards), the best thing you can do is encourage your bank to add Android Pay support. Google seems to be aggressively working with banks of all sizes to get support rolled out, but it's a slow process — and if banks see a swell of customers wanting Android Pay support it can help grease the wheels.

In the meantime, you can choose to use your unsupported card with the additional PIN, or hold out for full support. Either way, at least you know where to place the blame when you have to make a few extra motions to make an NFC payment with Android Pay.

Andrew Martonik

Andrew was an Executive Editor, U.S. at Android Central between 2012 and 2020.

  • Great, thank you for the article! I have a PayPal debit card and was asked for my PIN, which was rather annoying. Hopefully Paypal will partner with Google soon for their business accounts, or all for that matter. I haven't tried my US Bank card, which is supported, yet. Maybe soon. Cheers! Posted via the Android Central App
  • Wouldn't count on PayPal and Google getting together on this considering how much they compete with each other for in-store, online and person-to-person transfers... but who knows! Apple Pay supports several hundred banks right now and it doesn't support PayPal either... so that may be an indication of whether or not this will happen for Android Pay as well.
  • I use a supported Wells Fargo card and I've found that when I have to enter my PIN, it's usually because the cashier doesn't see a pretty picture to press on their terminal screen. I wish everything could be self check-out. I also found a grocery store that doesn't allow it's cashiers to touch any money. There is a money counting machine and a terminal for payments, including NFC. It stops employee theft and stupidity. Galaxy Note 4 {Sprint 5.1.1}
    3-day Power with a 9600mAh Extended Battery.
  • I have 2 cards that ARE supported,but it's acting like they aren't. Do i need to remove them and re-add them since they had the virtual numbers from wallet?
  • Worth a shot to start fresh. Did you confirm with your bank that they're supported? Google does say that not all card/bank combos are supported fully.
  • I am using an AMEX which is clearly supported. But it also acts like an unsupported card with 2 swipe unlocks and 2 taps required? I even got a welcome to Android pay and amex email when I enrolled the card. Posted via the Android Central App
  • Well extra phone unlocks and taps are different from needing a Google Payments PIN as described here. My first couple questions would be what phone are you using, and are you using Smart Lock or some kind of third-party lock screen? These seem to be causing issues for folks versus those who just use a standard pin/pattern/fingerprint and no other funny things that may have an impact on the security on the phone.
  • Andrew, I have a Project Fi Nexus 6. I do use smart unlock with my Moto360v2. My normal security is swipe. So with the phone unlocked on my home screen or with the Android Pay app open it requires 2 additional swipes and a second tap after the first one fails....very strange that it requires 2 swipes? Posted via the Android Central App
  • How are you using Android Pay with a non-secure lock screen? During the setup process it should be requiring you to use either a PIN or pattern lock screen in order to have the app active and with cards in the wallet. Android Pay explicitly requires device security (or at least its supposed to, barring any bugs).
  • I think he means that when smart lock actually works he just swipes up the lock screen, then when he taps to play he is prompted with two unlock patterns/pins and am additional tap to pay. I have this same janky experience, much slower then using a old fashioned credit hard. Even worse than Google Wallet... I wonder how this comparing to apple pay or Samsung pay. A video comparing the experience would be cool. Posted via the Android Central App
  • Sorry...I use a pattern and I called it swipes. Posted via the Android Central App
  • With my moto 360 (2015) on my wrist, and my LG G4 unlocked, I tapped phone to register and phone demanded my unlock pattern. Then another tap, then it went through. I don't like being forced to use a lock screen, and even with my trusted watch on my wrist, it requires a swipe to unlock every 30 minutes. Totally annoying. I'm not going to pin-unlock my phone a hundred times a day just so I can avoid taking my wallet out of my pocket once / day. SO DUMB!! (BTW, I'm using a supported Wells Fargo Visa)
  • Navy federal is supported. Capital one is not. Posted via my S6 on the Android Central App
  • Very informative article, and oddly just before I sent a query to Google about inconsistency. At least I know why it asks for a pin, sometimes. Most of the time it takes one tap and I'm done. Then randomly it will force the triple tap, triple PIN. Like a few days ago when I was trapped at work with the cafeteria and coffee shop both closed, and me with no cash for the vending machines. Fortunately they had just enabled tap to pay on all the machines. One tap, got my sandwich. One tap, got my drink. One tap, no wait, put in my screen unlock even though it already was, and tap again. And put in the android pay pin. And tap again. and put in the card pin. And tap again.
    It seems just random...
  • Yup, it's stuff like this that's incredibly annoying to deal with. I just think the vast range of card readers out there, plus some software wonk, is causing problems. It's already confusing enough when it's working properly, then you have bugs and just an inherent level of inconsistency just with the variety of new payment terminals out there.
  • Agreed. They should add an extra step in the instructions: "Hope it works this time and does not embarrass you"
  • Will we ever get the ability to tap an ATM and get cash out? That would be awesome. Plus no more stranger danger.
  • ATMs would have to be updated with tap & pay terminals ... would be great, but I don't see that tech being updated widely any time soon. And I'm not sure how much Google & other NFC-based payment providers are actually trying to push that either.
  • True. Banks *just last year* were forced off Windows XP (!!) at their terminals. Tap to withdraw cash may never happen!
  • Agreed. The ATM terminals are expensive pieces of equipment. Innovation at ATM's will be at a pedestrian pace.
  • This is more likely to be a future function of your banking app I would think. Posted via the Android Central App
  • I'm wondering how long the actual Google Wallet branded MasterCard is going to be around. I use it a lot as a cash proxy and it works within Android Pay.
  • It's still a big tentpole feature of the new Google Wallet experience. I see no indication that it's going away. if they were going to drop it, this transition to new Android Pay and Google Wallet apps would've been the time — but they kept it around.
  • You'd think then they'd support it as aa branded card from one of the supported banks. It requires the PIN!
  • Well it isn't really meant to be used inside Android Pay... Google's really trying to separate Google Wallet from Android Pay, and the links will be completely severed once Android Pay takes over online payments from GW as well. It makes sense to me to have these be separate.
  • See, that's the weird thing. You **couldn't** add your Google Wallet Mastercard to the old Google Wallet app! But they are allowing you to do so now. It even shows the Google Wallet logo on the rendered virtual card in your wallet. Why go through all that trouble to add it in if you're going to yank it out later?
  • I don't know, just like I don't understand why Google would bother keeping all of this random unsupported card stuff around, either. I think they should've killed all of it when they went to Android Pay... but here we are.
  • The only unsupported cards that can be used, are ones that you had in Wallet at the time you changed over to Pay. It is a grandfathering thing, so that people using Wallet can still use Pay. There aren't enough banks yet.
  • Not true. I had Chase Visa cards in the old Google Wallet and they were not grandfathered in even though I was told they would be. Here is the response from the Google representative via email after I spoke to him. "I understand your frustration, all I can tell you is card issuers are moving over to a supported platform everyday and it shouldn't be too long before the majority of Banks are supported, especially major banks." Not very comforting since I was using a perfectly good app with all my cards and Chase has no ideal when and if it will ever allow Android Pay. Some were grandfathered in and some were not. No explanation as to why, just that that is how it happened. They were very apologetic on the phone but no solution other than call Chase and wait.
  • Both my Chase Freedom and Chase Sapphire work just fine in Pay, because I had them in Wallet at the time of changeover to Pay.
  • That's weird. My Chase (Amazon logoed) Visa came over just fine.
  • Same here. My Chase Amazon made the journey just fine. Chase denied the first AP transaction due to security concerns at their end, but since they cleared the security block its worked just fine.
  • Not true. I had Chase Visa cards in the old Google Wallet and they were not grandfathered in even though I was told they would be. Here is the response from the Google representative via email after I spoke to him. "I understand your frustration, all I can tell you is card issuers are moving over to a supported platform everyday and it shouldn't be too long before the majority of Banks are supported, especially major banks." Not very comforting since I was using a perfectly good app with all my cards and Chase has no ideal when and if it will ever allow Android Pay. Some were grandfathered in and some were not. No explanation as to why, just that that is how it happened. They were very apologetic on the phone but no solution other than call Chase and wait.
  • Don't know how I double posted but since I can't delete it I just wanted to make sure that I don't sound like I'm calling @tim242 a liar. The Google rep did state that some cards ported over correctly and some did not. If yours did not then your are out of luck. I also had 2 Chase Freedom cards that I was using and they both did not port over.
  • Good news. After reading some posts of people re-installing Google Pay and having cards work that previously didn't work, I decided to attempt it again. Cleared cache, deleted data. and uninstalled the app just to be safe and sure enough my Chase Freedom cards now work. Chase is still not on board with Google Pay and these cards were previously in the old Wallet app so you can't install new cards that were not in the old Wallet app. So for those of you that were having the same problem as me. It may be worth giving it another try. Good luck.
  • I'm not sure I'm understanding the PIN issue... I have a Chase card (Unsupported) in my Android Pay. I have used it many times and never once has it asked for a PIN. It just works like Google Wallet used to work.
  • Same here with my bank debit card. Is this because Google hasn't "flipped" the switch yet? Posted via the Android Central App
  • same here but different bank
  • But you are required to sign the terminal as if you swiped a card, no? Posted via the Android Central App
  • I love the Google Wallet card, as well, and found it strange they hadn't cut a deal with that bank first thing. I suppose when all cards will be mandated to have the chip, we'll see if the GW card gets updated or dropped. Posted via the Android Central App
  • That'd certainly be a point where Google would show if it plans to use the Google Wallet Card going forward. It survived the app redesign and the separation of Android Pay from Google Wallet, so at least right now it seems the physical Google Wallet Card is sticking around.
  • Thank you so much for your help. It was driving me nuts entering the PIN, although in my experience, its been having to enter it three or four times to actually unlock it. Once sounds like a dream in comparison. Posted via the Android Central App
  • Thanks for the explanation....I bailed during the first week. Not much near me supports Pay and it simply wasn't worth the hassle of having a secure lockscreen all the time. But at least I know why this particular feature was being wonky.
  • What about for us people that have rooted phones? *sigh*
  • You shouldn't expect a secure payment system to work when you're rooted.
  • Google Wallet seemed secure enough. Posted via the Android Central App
  • How is a system that had no cooperation of the banks, obscured the transaction details from the merchant and used a third-party bank called "Bancorp Bank" to make the purchases more secure than what we have now? The new system is far more secure, and not letting you use it on a rooted phone is part of that security.
  • Never going to work with galaxy note 3, huh? Posted via the Android Central App
  • I am deciding between Android Pay and Samsung Pay. Does anyone know if Samsung Pay will work with terminals that read the "new" chip in the US? If it doesn't, I don't see the advantage of Samsung Pay if terminals that read a security chip is where we're headed. Posted via the Android Central App
  • Samsung Pay works with NFC readers (as Android Pay does) or any reader that takes a standard card swipe. Of course the U.S. is starting to accept the new "chip" cards, but every one of those terminals also still accepts swipe. The big thing to remember here is that the terminals just have to support the new chip system, they don't have to be chip-only. And at this point with how low actual chip card adoption on the consumer side is, that'd be a horrible choice for a merchant to make (just about as bad as being NFC-only or cash only at this point). And it's going to be years (yes, maybe even decades) before the swiping starts to be deprecated. So don't worry about those swiping-style terminals going away any time soon.
  • OK, thanks. I was picturing a terminal that you could only insert a card. I didn't realize they still have a swipe option. My advantages for Android Pay were if I switched phones in the future, online purchase support coming, and they already have my credit card information. The big advantage I saw for Samsung Pay was broader use. I will probably try Samsung Pay. Posted via the Android Central App
  • If you swipe a card with a chip at the new terminals, it requires you to insert the card. This will probably cause problems with Samsung Pay.
  • Have documentation on this? Not only have I not experienced this at retailers, I also haven't seen anything that indicates this will be required. Posted via the Android Central App
  • Walmart has had the new terminals for a while. When I swipe a card that has a chip, it beeps loudly and tells me that my card must be inserted into the chip reader. I would assume that the same thing would happen with an MST transaction. I have not seen anything from Samsung that addresses this, so I won't know until Verizon enables it, and Samsung adds support for one of my many cards.
  • Actually I was going to ask this very question to you, but tim242 beat me to it. It seems to me that it would be counter-intuitive to require chip-readers for merchants, yet still allow chipped cards to be swiped. I was thinking as well that chipped cards may be required to be inserted, and only legacy non-chipped cards may be swiped. So Samsung's MST tech could potentially become useless at these terminals if they do not also support NFC (see my next point). However, it's likely that many of these new terminals probably have NFC capabilities so Samsung Pay would still work, but I have seen many (like at Walmart) that do not appear to support NFC but do have the new chip reader, which is mronic in my opinion. It is also possible that Samsung has worked out an agreement with banks that if the consumer is using Samsung Pay, it is inherently more secure because it requires a PIN or fingerprint, so they should allow a swipe transaction (MST), if NFC is unavailable. This may be why Samsung Pay has so few banks on-board at launch, because they are convincing the banks of this feature.
  • This was a major issue for LoopPay (which Samsung Pay) but does not occur with Samsung Pay because Samsung Pay is not cloning the card - they are using tokenised data (which doesn't have the use chip service code) being obtained from the banks. Thus, the flag telling the terminal to ask for the card to be inserted isn't there.
  • Hurdle is the word you want to use there, not hurtle.
  • That's correct! Though you could argue you're hurtling toward a new hurdle...
  • Thanks for another great explanatory article! Google's "explanation" of things like this is so weak, I'm really glad we have someone like you to blaze the trail for us. I didn't understand how Wallet was being replaced by TWO apps until you explained it, either. But I'm not even sure Google is working consistently with the banks. When I called Wells Fargo to activate my debit card that had worked great under Wallet, the rep on the WF end didn't know what I was talking about. She'd never heard of Wallet or Android Pay. I have to give her credit for putting me on hold for 10 minutes until she did get the information on how to do it, it has worked fine since then. They really need to explain things better....
  • Thanks for this! I bought some pants at Macy's in Manhattan. I was excited to give Android Pay a shot since I've used wallet since the start. When I was asked to reenter my pin. I was a little embarrassed and confused. Thanks for answering my concerns!
  • I have an unsupported card and it never asks me for a pin. Posted via the Android Central App
  • My phone asks for my unlock pattern even though I'm using smart lock. Posted via the Android Central App
  • That's different than requiring a Google Payments PIN — that's a security measure. We're trying to nail down the circumstances of when you'll be required to enter your normal lock screen during payment, but lots of folks currently using Android Pay along with a trusted device for Smart Lock are having varying success — sometimes a lock screen entry is required at time of payment, sometimes it isn't.
  • After lots of back and forth with the techs at Google, they informed me that Smart Lock is the culprit. I was told that Smart Lock is not compatible or supported and that it needed to be disabled in order for Android Pay to work. I'm very disappointed in their handling of the matter. The techs acted like they had never heard of the issue - like I was the first to report the difficulty. Like many others, I find these additional requirements and restrictions a total nuisance. But even if I were ready to go along with it, the fact that they haven't documented this incompatibility with Smart Lock and leave the debugging to regular users to figure out for themselves is unacceptable. When a regular layperson stumbles on the issue by chance and they become frustrated, many will simply stop using it. If Google wants a successful rollout, they have got to realize that most regular people are not beta testers. They don't want to solve three riddles to cross the bridge. I'm not an Apple fan - I'm a proud Droid Turbo owner - but this is where that company has a leg up on Android products. They know people just want a thing to work. It's embarrassing to me, as an Android advocate to see Google bungle this.
  • I got this reply from google wallet support: "Hi, Michael. Thank you for your patience. We are informed by our technical team that they are updating the app, based on several feedback for that matter. Rest assured that the app update will provide new feature based on customer's request and feedbacks. If you have any more questions, please reply to this email or let my team call you. We're happy to help! Thanks, Eric
    The Google Support Team"
  • My Discover card is supposedly supported, but it is NOT supported when I add it to the Pay app. Even after removing the card and re-adding it, I still see the option for the PIN with bankcorp. Customer service with Discover says it should be supported. This kind of confusion leads to a negative customer experience and makes me think twice before attempting to use this app. However, I have no problems with my AMEX, but would prefer my Discover. Posted via the Android Central App
  • I contacted Google's Android Pay department about this very issue. After 10 phone calls, they just keep reading from a script. They also blamed Discover.
  • I looked on Discover's site and they say that it works the same as Google Wallet did, where the charge goes through a MasterCard virtual card and then Google charges Discover. Here's the info from the Discover Card FAQ: I made a payment in-store using my Discover card via Android Pay. Why does my receipt say I used a MasterCard?
    For Discover card, Android Pay currently uses a virtual MasterCard to pay the merchant in-store. This virtual card is linked to your Discover card. When you use Android Pay, Google actually pays the merchant with the virtual MasterCard, and then charges your selected card – that’s why the transaction on your receipt looks like a MasterCard transaction but is processed like any other Discover transaction you’d make.
  • "It was clunky, less secure and downright confusing to everyone involved" Um no it wasn't, it worked great for me for years. I could add any card and put in a pin to open the app, and then tap and pay. It was simple and painless. NOW I have to set a pin lock for my lockscreen, and it doesn't support LG's knock code as valid security. Also it allowed the debit card from my credit union but not my credit card from the same institution. Who knows why. Overall I'm very disappointed with Android Pay and see it as an inferior product to the old Google Wallet app. Really wish I hadn't updated it.
  • It pains me to know that you would want your financials accessible by knock knock. That is just dumb.
  • knock code is not simple knock on
  • I have a Nexus 6 (unmodified) with regular lollipop smart lock, and loaded with a debit card from a supported bank. The debit card was "imported" to Android Pay during the conversion from Google Wallet. When I use Android Pay at a supported grocery store, I unlock the device with my unlock code, tap it, am required to put in my unlock code again on an Android Pay screen, tap it again, put in my unlock code a second time on the Android Pay screen, AND THEN UNBELIEVABLY, I have to enter my debit card ATM PIN into the store terminal. What a pain. In the Android Pay App, I don't have the verbiage to change the PIN, indicating the debit card is supported (as a said, my debit card is from a bank on the list). Posted via the Android Central App
  • If you select credit you won't have to enter your cards PIN. Posted via the Android Central App
  • Nice explanation as far as the PIN and unsupported cards, though I really wish Google would sort out the unlock sequence when using Android Pay. I used Pay for the first 2 times today and even with my GWatch disconnected (so smart lock off) I still had to enter my pattern 4 times (when it was connected I had to input it 9 times). I wish they would just have us input the pattern when we open the app so I'm not holding up the line when trying to pay instead of having us unlock it at the register. Posted via the Android Central App
  • I can guarantee that having to enter your pattern 4 or 9 times is NOT the "working as intended" way of using Android Pay. There's something wrong there. I have never once had to enter my lock screen more than 1 time to make a payment (in fact I don't have to enter it at all if I've unlocked before tapping).
  • I wish that was my case but I always have to enter my passcode at least twice even when the phone is already unlocked.
  • My Chase card was imported from Wallet and so far it has worked like wallet. I unlock the phone tap and go. I have tweeted Chase support to chide them along as they are the only large bank not supported. I have a B of A card but never use it. I might add it if they kill my chase card but I prefer the Chase debit card so I don't have to deal with a bill from B of A Edit Just got this from Chase so hopefully soon.
    From Chase: We plan to support Android pay in the future. Please follow us for Updates.
  • Unsupported cards are only allowed if you had it in Wallet when you changed over to Pay. If you try to add an unsupported card that wasn't in your Wallet, you cannot add it. Although Discover is supposedly supported, it says it is not when trying to add it to Pay. If you had it in Wallet, it prompts you to accept the Bancorp agreement for the virtual card. After many conversations with Google via phone and email, still no answer as to why. They are clueless.
  • sadly smart unlock has been clucky in my experience. no one wants to jump through multiple hoops to have a secure, but convenient payment process--but I actually did like the fact that no matter the lock-screen status of my phone i knew that a pin was required for gwallet to make a purchase. my first care setup is unsupported, so will behave the same i guess. but if/when i setup my supported cards i will now wonder when the phone will be ready (maybe more often than i realize) to make a purchase. this is because i've been playing with all the smart unlock methods, which i don't want to eliminate for the typical non-payment phone usage.
  • My PayPal card is unsupported, but I've never been asked for a pin. But my s6 edge has a fingerprint scanner.
  • When are gas stations going to finally offer tap to pay at the pump.
  • Probably never.... they always warn against using a mobile phone while pumping fuel, saying it's a fire hazard (even though it isn't).
  • The tech should be there. Gas stations promoted contact-less devices that would provide quick payment at the pump. It didn't get much traction, but the pumps probably have contactless readers in there Not sure sure if it was NFC or RFID though..
  • I wish the Android Pay app worked properly with trusted Bluetooth devices. My phone stays unlocked when it's connected to my watch so the app should too. As long as the screen is on and the main lock screen is swiped away, I shouldn't have to enter my unlock pattern after tapping the terminal the first time.
  • Basically, it works great if everything just happens to line up perfectly. But for the other 75% of us it's a giant cluster..... and basically not worth using. I was using Google wallet for a long time. Unlock screen, tap, BING, receipt. Maybe upgrade to a Note 5 and use fingerprint ID. Posted via the AC app with my antique G3
  • "It's complicated"
    Think I'm gonna be reading a lot more articles and comments about this before I invest in android pay, as a UK resident Google wallet wasn't viable and poorly informed by Google,
    also I can't help thinking that any public financial transaction needs solid simple security like fingerprint scan... Posted via the Android Central App
  • Chip based credit cards don't have fingerprint scan, Why would phones need to have it? The extra security that fingerprint scanning affords is welcomed, but not essential IMHO.
  • How do we use a card that isn't the default card in Android Pay? Posted via the Android Central App
  • Once the card is added, you just open the app, tap the card you want to use, then tap "Set as default card." Posted via the Android Central App
  • Should be an option to use once. Annoying to keep changing cards to default card when I want to use a different one. Posted via the Android Central App
  • So wtf, how lazy can people be? Having to tap my phone then enter a PIN and the tap it again. Has doing something as simple as this gotten too be too much for people, it's pure stupid to think it is a problem. Lazy asses. Posted via the Android Central App
  • It is not a issue with laziness. The problem is with consistency and lack of communication from Google. Why do some cards immediately work and some take two or three tries? And sometimes the wheel starts spinning and nothing happens at all. I promise the person that knows the least about mobile payments is the clerk behind the counter so it's up to us to know how the app works. Since Google didn't bother educating us, AC did. So re-read the article, simmer down and just say thanks.
  • Maybe you're right. I'm being lazy because I don't want to pin-unlock my phone a hundred times a day just so I can buy something once/day at a store using my phone instead of a physical credit card. Hmm.
  • Ever noticed you can alter the timeout on the screen lock? Ever notice that if you don't lock your phone, if an undesirable person gets hold of your phone and therefore access to your personal email, the ID thief can initiate a password reset for your bank account, gain access to your funds and take you for a sweet ride. Not locking your phone in this day and age is akin to running around with your identity pants down. Don't blame Android Pay. Its a good practice. If you don't want to lock your phone fine, uninstall AP and you don't have to.
  • Good one
  • Discover is listed as a supported credit card on android pay's website. But in my android pay app I still have to use a google payments pin. I used my discover card before with Google Wallet. Is anyone else experiencing this?
  • Same here.
  • Google Wallet was SO much better! You could see your transactions within the app which for whatever reason Google took out of Android Pay!
  • I dont guess that there is any hope of being able to have this without a lockscreen. I'd much rather have a PIN at the app than a PIN for the whole device.
  • I tried to add an unsupported card today, it wouldn't let me add it. They might have already flipped the switch.
  • I don't use a secured lock screen. If I lose my phone I will log into Android Device Manager and set one. I used Google Wallet when I could, which wasn't very often. I have no intentions of using Android Pay if it requires a lock screen. I tried using smart lock with my Moto 360 and locations. It works but after four hours of inactivity the lock screen does turn on. Which means every morning I have to unlock my phone. This is not acceptable to me. At the 2014 I/O event Sundar said phones are checked 100 billion times per day. If only 10% use Android Pay and start using a secure lock screen how many human hours a day are spent putting in a PIN, password, or drawing a shape?
  • my LG G4 with Moto 360 (2015) prompts me EVERY 30 MINUTES (can't set longer). It's crazy stupid !! I"m going back to using my credit card the old fashioned way.
  • If your phone is inactive for over 30 minutes, then it is mathematically impossible for the phone to lock you out more than 48 times per day, but since you leave your phone inactive for over 30 minutes, you can't be using it that much anyway!! If you truly use your phone a lot, it will never lock you out!!
  • I understand you can lock your phone if lost remotely. WIpe it clean even. However the damage maybe done before you realize your phone is missing. All an identity thief needs is 2 minutes access to your personal email to ascertain who you bank with, visit the banks website, perform a password reset, respond to any emails or text codes on your phone and they then throw your phone in the trash. They then repeat the process with Facebook to get information like your Mother Maiden name. You lock your phone but money is already being spent.
  • Has anyone been having trouble with AP? I tried to use this wanted me to update card info, but when I said network error...and won't let me in! I have messaged Google but with no reply as of now......
  • Anyone know if they are going to give us the option to add an app PIN regardless? I LIKE having that extra layer of security and having an app specific PIN would also let me go back to my third party lock screen. Also, oddly enough, I have not been asked to enter a PIN at all, even with unsupported cards. I don't find the extra pin annoying at all. I am perfectly happy to open the app and unlock it before tapping. Google Wallet worked great for me and I am frustrated that they took something that worked and screwed it up. Typical tech company.
  • My Wells Fargo Debit card was working in G.Wallet for the longest time and A.Pay. Then I got a new WF card with the chip. It would request a pin each time I tried to use it. After I entered the pin my phone ( OnePlue One 5.1.1 ) would stop responding. I am having to force reboot the phone there after. I've removed then reinstall G.Pay with no better result. Finally I reset the entire phone and now my WF Debit card no longer requires a pin when making a purchaser. Now I get a msg saying the card is not supported. WTF.
  • UPDATE: My last restore caused an issue where no debit card I had would work in A.Pay. 'Card Not Supported' message would appear. 2nd times the charm it appears. Did another restore of my OPO this time I also chose to delete all my personal stuff (, videos, ect.). Now A.Pay works with my Wells Fargo Debit card. Hurrah.
  • Updated to Pay from Wallet and it kept the two "unsupported" cards I was using. One is a debit card. Neither require a PIN when using Pay after the screen has been unlocked. If I select use as credit on the terminal, a PIN isn't required there, either. I do hope Google fixes the smart lock issue. It should be a seamless process to use Pay if your phone is already unlocked by a trusted device, such as my 360. Using smart lock and Pay together is a buggy hassle. Posted via the Android Central App
  • Given that banks in Australia aren't willing to adopt Apple Pay, I don't see Android Pay going anywhere here in Australia either.
  • Let's be glad we don't have all of our info in Samsung's system o.O! I wouldn't believe a thing they say trying to minimize the damage either.
  • I ordered the Nexus 6p. When I loaded my cards into Android pay I had to contact my bank to complete the authorization. When my new phone arrives I guess I will need the scan the cards again. Will I have to go through my bank again to complete the authorization or does everything carry over to the new phone? Posted via Android Central App
  • I was surprised at first when asked for a PIN at the payment terminal, but now I have grown accustomed to it I believe it adds an extra level of security. The US has decided to go with Chip and Sign Credit Cards rather than the more secure chip and PIN. Using a Google Wallet card in Android pay makes your card behave just like a chip and PIN card. I'd hate to see this go away after the Google Wallet cards cease to function. I would like to see the option in Android pay to turn on a PIN requirement for added security. For those happy with the simpler tap and pay without a PIN, fine, go ahead, just give me the option to turn on a PIN. The PIN should be prompted for on the merchant terminal, not the phone. This is how it works currently at Office Depot and works very well IMHO.
  • I'm fed-up. I uninstalled / disabled android pay and google wallet. It was draining my battery with uncontrolled GPS searching for loyalty cards-near-me.
  • Google is to blame for another half baked beta implementation. I really wish apple wasn't the only other option because even though I hate apple Google is so bad and android such a rotten overall experience that I am thinking iPhone
  • Chase is not on the list. The #1 issuer of credit cards in the USA. Wtf Google you suck!
  • I've used it fine for a few weeks and then has stopped working, demanding the PIN - the card is a MBNA card so on the list of supported banks. Really frustrating/embarrassing when it first failed.
  • On Google Play they responded: Hi Matt, you can find information on PIN requirements here: If you still need help, we're happy to assist: