Helping 1Password adopt to site's specific non-standard forms by sending the data about the site
We are not living in perfect world so many services which are accepting cards are using strange and/or nonstandard fields for card payments.
I understand that reporting this to AgileBits and implementing is rather complicated so there should be new functionality "learn service". When user will find payment service which is not properly maintained by 1Password should have possibility to inform 1P that it should fill, for example, valid year last 2 digits in this field, or first 4 digits of number in that field. Such option should prepare a kind of metadata which then can be reported to AgileBits and easily implemented in future updates.
Other possibility is that if after filling page with card details user will edit the data then 1Password should ask "should I remember changes for this web page?" - when user will visit this page again 1Password will know how to fill form.
Comments
-
Hi @PLMan,
It is something we're considering for the future, not just for credit card but for Logins and Identities as well. We just need to focus on improving our extension's filling code, so that it can adapt to any metadata that can be used, including checkbox, dates, and so on.
Other possibility is that if after filling page with card details user will edit the data then 1Password should ask "should I remember changes for this web page?" - when user will visit this page again 1Password will know how to fill form.
Technically if you check out on that site A LOT, you can already ask 1Password to save the form details via the Save a new Login manually method. Just make sure you name it appropriately, so that you know it's for credit card page, not for the Login page. So, if we're talking about Amazon, you'd do something like Amazon Login and Amazon Checkout.
0 -
The problem is that usually such pages has dynamic urls so saving new login will not work well.
0 -
I will when I will buy something using such services.
0
