I noticed a similar issue posted with united.com
https://bugs.chromium.org/p/chromium/issues/detail?id=582101

Original discussion about my issue at https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/3Y0dD9jBIeI

I am not sure what the time frame to expect for someone to review this, but while I wait it's causing alot of headaches with many incorrect orders coming through and being charged incorrectly. Is there any way to completely block the credit card from auto-completing on my form?
I tried autocomplete="off" but it is being ignored by chrome  (both if I add it to the field or the whole form).
From what I read online, it seems autocomplete only effects regular address type fields but not the credit card autofill.

Any help to prevent this issue would be appreciated!

The only thing that I was able to do to stop it is if I change the input name to something other than 'itemQty1'

I can confirm that after spending a lot of time trying to figure this out that this bug is still valid for 58.0.3029.110 (64-bit)

This issue occurs on macOS and Android as well. If it can't be fixed soon it would be great to have a workaround. E.g. which form elements and/or attributes to use to opt fields that are not related to the credit card out of the autofill process.

In my case the field name is quantityN (e.g.: quantity1, quantity2 etc for items in a shopping cart). The quantities are getting set to the cc expiration month. So a customer expecting to order 1 or 2 of a product is having their quantity adjusted to 12 in the worst case (e.g. an expiry month of December).

as a work around i've made fields readonly but include onfocus js that makes the field editable - works nicely..

Nice. I ended up checking for the :-webkit-autofill pseudo-class and if that was present I changed the value back to what had originally been in the field.

Having the same issue, too. Any way to escalate this?

Can confirm, changing the form name from itemQuantity1 to productCount1 fixed it for me.

Works now

I am seeing the same issue again, on 2018-Dec-11. We're getting customer reports starting sometime during the past 2 weeks of donation amounts messed up by CC autofill.  

Example (url below): donation form where if chrome autofills the cc info, the monthly donation amount changes to whatever the card expiration year is.  A person intending to donate $500 is now charged only $19 if their card expires in 2019.

https://www3.thedatabank.com/dpg/198/spdf.asp?formid=dontestautofill

The field named "amount6" is wrongly autofilled with the card expiration year -- but if in Developer Tools I change the field name from "amount6" to "donationamount6" it's OK - no autofill.  The name of the  field that is wrongly copied into the donation amount is "cardexpyr".  I don't for the life of me see how "amount6" == "cardexpyr" in Chrome's mind.

Changing the name of the Card Expiration Year field does not help.

Version 71.0.3578.80 (Official Build) (64-bit) (updated TODAY) Windows 8.1

Please help, this is freaking out several of our customers.

We also found that simply re-ordering the fields on the form could fix the issue.  I don't know what criteria Chrome bases its autofill decisions on, but from the outside it appears that CC autofill is trying to be too clever and getting itself in trouble.