New issue
Advanced search Search tips

Issue 849063 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Credit cards associated with Google pay does not show up; cannot be selected in form autofill

Project Member Reported by js...@chromium.org, Jun 3 2018

Issue description

I have 3 credit cards stored in Chrome's autofill cc section. 

Two of them do not have 'Google pay' label next to the cc number, while the 3rd one has 'Google pay' label next to the cc number. The 3rd one is my primary card, which is why I use it in Google pay. 

However, on the web (mobile or desktop), the 3rd card stopped being available for autofill (started a couple of weeks ago). 


 

Comment 1 by se...@chromium.org, Jun 19 2018

Cc: se...@chromium.org
Is it only not suggested to you when you fill, or is it also missing in the settings page?

Thanks!
Google Pixelbook - Chrome 67 stable

I've having the same issue on pixelbook and android. All of my credit cards are linked through google pay, and none of them show up in chrome autofill. I'm using this page for testing https://browsingtest.appspot.com/autofill_smoke_test.html

Profile autofill still works as expected.

I think others are reporting issues here too: https://productforums.google.com/forum/#!topic/chrome/ouxQAsb-Vgo
Are you using a custom passphrase for Sync? 

You can see that by navigating to chrome://settings/syncSetup

At the bottom of the page you should see an option to use a custom passphrase
Cc: dlkumar@google.com
Yes, I am using a custom passphrase.
Ah yes, unfortunately this is a bug that affects users with a custom passphrase in M67. The fix has already been made and will be included the next release, M68.

Thanks!
Latest version of Chrome still has this bug
* Chrome Desktop
The website linked above works but PaymentRequest doesn't: https://googlechrome.github.io/samples/paymentrequest/credit-cards/
To make matters worse I can't even add it manually since browser complains that the number is already in use.
Owner: jsaul@google.com
jsaul@ Do you have time to investigate or can you re-assign?
Cc: jsaul@google.com
Owner: rouslan@google.com
So it sounds like this bug encompasses two issues.  I *think* that the initial report and the followup +1 by laroucheyouth were due to the problem that was fixed in M68 (#comment6).  The last posts in the productforums link posted in #c2 also seem to imply the M68 fix worked, and #comment9 also mentions the website problem is fixed.

The new issue is the PaymentRequest site pointed out in #comment9.  I'm seeing the same behavior--despite having a Visa card on my device, and though the JS snippet on the page says Visa is allowed, PaymentRequest isn't displaying it, and it also won't let me add it, either.

Rouslan, do you know why this is second issue is happening with PaymentRequest?

In the meantime, mwisnicki@, you might be able to work around this by manually adding your credit card again to your device via chrome://settings/payments.  Sorry for the trouble!
Owner: rouslan@chromium.org
Status: WontFix (was: Untriaged)
Payment Request does not show cards from Google Payments account by design as of Chrome 70. The guidance for merchants that want to get those cards is to use the Google Pay JS library, which uses the Payment Request and Payment Handler API and provides encrypted versions of cards, which is more secure than the plain-text cards that are returned on https://googlechrome.github.io/samples/paymentrequest/credit-cards/. 

Since the Payment Request behavior is by design and the autofill issue was solved in M68, I'm closing this as WontFix.
FYI: Rouslan and I chatted, and I strongly feel it's a bad user experience that PaymentRequest won't let you manually type in a CC number that matches an existing server card.  We've created https://bugs.chromium.org/p/chromium/issues/detail?id=905396 to follow up on this issue, so feel free to follow along there if you're interested in the PaymentRequest fix.

Sign in to add a comment