Security Code/CCV/CVV code never fills

Options
foxo
foxo
Community Member

Hi,

I've never managed to get 1password to fill in the 3 digit security code when entering a credit card.

I assumed this was because every site seems to use a different label for this field. So I tried creating multiple entries for this number, matching the most common versions used, however this still doesn't work.

So for example, when trying to fill in credit card details on the attached Google payment page, the security code doesn't get filled.

In the credit card entry in 1Password, I've put this (same) 3 digit code into the "Security Code", "CCV" and "CVC" fields. None of which are used.


1Password Version: 5.3 (530029)
Extension Version: 4.4.3.90
OS Version: 10.10.5
Sync Type: dropbox

Comments

  • littlebobbytables
    Options

    Hi @foxo,

    It seems you're likely using custom fields to store the card's security code but for 1Password to be able to fill it has to be stored in a very specific (and default) field. If you create a new Credit Card item you'll see the default fields, one of which is titled verification number. Now it isn't enough to merely create a new field with the same label, it has to be that specific field as we only look there for filling purposes.

    If you edit the item you should hopefully see this field and if you add your security code there I would hope 1Password will then fill. If it doesn't the easiest approach is probably to create a new Credit Card item and fill in the fields using the data from the original one. I would hope one of these helps resolve this so please let us know how you get along :smile:

  • foxo
    foxo
    Community Member
    Options

    That worked - thanks for the help!
    It seems I had a false impression on how 1Password works, assuming that it would match fields based on arbitrary name alone.

  • Vee_AG
    Vee_AG
    1Password Alumni
    Options

    Hi @foxo,

    On behalf of littlebobbytables, you're quite welcome! Glad he was able to clarify that for you. :)

This discussion has been closed.