rick3162@ Thanks for the issue.

Tested this issue on Windows 10 on the reported version 68.0.3440.106 and the latest Canary 70.0.3535.0 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and signed into Chrome.
2. Navigated to https://dump-truck.appspot.com/usecase-address_then_cc/cc.html and clicked on "Fill with default values" button and then the "Submit" button.
3. In chrome://settings/autofill, can observe that the credit card details are saved.
Attached is the screen cast for reference.

Request you to retry the issue without any apps/extensions on the profile and update the thread with the observations.

Thanks..

Deleted: 877789.mp4 1.9 MB

	877789.mp4 1.9 MB View Download

First of all, thanks for replying.

Unofortunately, even after disabling all apps extensions, the issue occurs.
Please see attached screencast.

As I wrote in my OP, If I disable Sync and repeat the steps, then the issue is immediately fixed.

BUT, if I re-enable Sync (with the apps/extensions remaining disabled) and then just keep repeating the steps,
then the issue will surely start constantly reoccuring a few minutes later (it just happened to me after 5 mins, i.e. after repeating the steps ~10 times).

--------------------------------------------------------------------------------------------------------------


I think the issue might be caused because the synced data of my profile might be corrupted for some reason??
I'm saying that because I have already tried removing my Sync profile: the issue becomes fixed. 
But when I sign again with the same Google Account, the issue reoccurrs.

Or, there's some bug in Sync, i.e. some kind of user confirmation that the browser wrongly expects when prompting to save the card, while Sync is enabled??


Please note that, as I've wrote in my OP, the text: "By continuing you agree to the Google Payments Terms of Service and Privacy Notice" is only displayed in the cases where the card is not getting saved.
In the rest cases, i.e. when the card IS getting saved, there's only a "Learn more" link, instead.
(please see the two new attached screenshots).

Deleted: Video_2018-08-28_191729.wmv 4.2 MB

Video_2018-08-28_191729.wmv 4.2 MB Download

Deleted: Save Card prompt (Sync on) -- issue.jpg 33.1 KB

	Save Card prompt (Sync on) -- issue.jpg 33.1 KB View Download

Deleted: Save Card prompt (Sync off) -- no issue.jpg 12.5 KB

	Save Card prompt (Sync off) -- no issue.jpg 12.5 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Unfortunately the issue still occurs with today's Chrome update to 69.0.3497.81.

Hi Rick3162, I think I can clarify this issue.  It's actually working as intended; sorry for the confusion.

You're right that the dialogs are different; the one that explicitly mentions Google Payments will save your card to Google, which then also makes it available on all of your other Chrome devices via Chrome Sync.  However, this carries the requirement that the card must be *valid*.  The "5454 5454 5454 5454" card you get from the [Fill with default values] button is just a testing card that would always be declined and fail to save, because it's not real.  If you were to enter actual credit card details in that form, it should save properly.

Then, when you turned off Chrome Sync, the dialog switched to only saving the card to *that* specific Chrome device.  Because it no longer interacts with Google Payments, you can save invalid cards if you really want to, and that's why it succeeds (but it would be useless in an actual checkout flow, as it's not a real card).

Marking as WontFix following my previous #c8.  I'm still happy to discuss the issue here if you'd like, I just don't want testing teams to get bogged down with it since it's working as intended (cannot save fake credit cards to Google Payments).

Thanks!

Thanks for all the information, jsaul.

After your replies, I've waited till the day I had to make online payments again, and it's today, two transactions using the same debit card:

unfortunately the debit card I used was NOT stored (although the payments completed successfully) :

1. 
while being at https://www.wind.gr (having login to my 'F2G' account), press "ONLINE TOP-UP" and then you'll get redirected to https://etopup.wind.gr/etopup for the payment.

2. 
while being at https://myaccount.nova.gr/ (having login to my 'Nova' telephony account), press "PAY BILL" and then you'll get redirected to 
https://paycenter.piraeusbank.gr/ for the payment.


In both cases I pressed "Save" at the prompts(which were explicitly mentioning Google Payments), but the debit card was not stored.


Please see the 5 new attached screenshots.



PS. I deleted and re-posted this comment because of a typo I had (credit card -> debit card), sorry about that.

Deleted: Form 1.jpg 151 KB

	Form 1.jpg 151 KB View Download

Deleted: Form 2.jpg 188 KB

	Form 2.jpg 188 KB View Download

Deleted: Save Card prompt 1.jpg 104 KB

	Save Card prompt 1.jpg 104 KB View Download

Deleted: Save Card prompt 2.jpg 91.1 KB

	Save Card prompt 2.jpg 91.1 KB View Download

Deleted: The debit card is not saved.jpg 35.0 KB

	The debit card is not saved.jpg 35.0 KB View Download

Also, in order to better clarify my new comment:

Chrome version is now 69.0.3497.100 x64 (in win10).

Also, in my new comment I have used in both cases a (valid) DEBIT card, not a credit card.
Specifically, it's an: Alpha Bank Enter Visa [1].

I haven't used a (valid) CREDIT card in any of my comments.


[1] https://www.alpha.gr/en/retail/cards/debit-cards/alpha-bank-enter-visa

Maybe this feature, Chrome to save payment methods, 
only works for CREDIT cards, and not debit cards ?

Because I can't think of a different reason why my valid debit card is not saved.

I've just made another online purchase in https://www.wind.gr (redirected to https://etopup.wind.gr/etopup) using the same debit card,
and although it completed ok, 
the card was not saved.

Thanks for the updates, rick3162.  Debit cards should be fine as well, I just tested one myself to make sure.

If you clicked [Save] but the card still wasn't saved, it was likely either a problem authing the card with your issuer/bank, or perhaps Google Payments cannot save that particular type of card for some reason.  Unfortunately I can't know the true reason without investigating further.

If you'd like, I can try to look up your logs and find the reason the save failed, but I would need your explicit permission to do so, as well as which account you used when you tried to save the card.  However, if it's anything other than the examples I gave above, I wouldn't be able to tell you the cause for security reasons.

> If you'd like, I can try to look up your logs and find the reason the save failed, but I would need your explicit permission to do so, as well as which account you used when you tried to save the card

Yes, please look up my logs, I gladly allow you to do so.
The account I used when I tried to save the card, in all cases I described,
was the same as the email that appears on top of my comments: 
rick3162 at gmail dot com 

Thanks, rick3162.  I tried looking up your logs in Google Payments, but I don't actually see any save requests!  This can mean one of two things:

1) It's possible the account wasn't actually rick3162 at gmail dot com.  Is it possible you have multiple accounts logged in and a different one was active at the time?
2) Alternatively, it's possible Chrome didn't send a save request to Payments, even though the [Save] button was clicked.  I'm not sure what would cause this, though.  Hey Sébastien, do you have any ideas on how this could happen, or how we could confirm it either way?

Re-opening this bug and changing some labels in the meantime for further investigation.

> 1) It's possible the account wasn't actually rick3162 at gmail dot com.  Is it possible you have multiple accounts logged in and a different one was active at the time?

No, I have only this account, rick3162 at gmail dot com, to which I have logged in in Chrome browser, and that was active all the time, as seen in the two screenshots I attach.

Deleted: Settings screenshot.jpg 70.6 KB

	Settings screenshot.jpg 70.6 KB View Download

Deleted: The popup that appears when I press the 'K' toolbar button - Manage people.jpg 28.2 KB

	The popup that appears when I press the 'K' toolbar button - Manage people.jpg 28.2 KB View Download

Thanks, that really helps.  Seems like the save calls were somehow dropped between Chrome and Google Payments, then.  I checked both sandbox and production environments and didn't see anything for either one.  Let me reach out to our team and see if anyone has any ideas of why this happened.