5 ms·
The problem it solves is reducing friction on checkout. One of the problems it creates is increasing the attack vector on an account holder by storing sensitiv
by AdieuToLogic 9y ago
The problem it solves is reducing friction on checkout.
One of the problems it creates is increasing the attack vector on an account holder by storing sensitive transaction information locally.
- marksomnian 9y agoNot necessarily, depending on the method. For example, Apple/Android Pay is stored securely. Raw credit card data may be stored encrypted by the browser and decrypted at runtime or with the OS keychain, although I'm not sure if this is done now or not.
- AdieuToLogic 9y agoFor example, Apple/Android Pay is stored securely. See this comment[0] for a more detailed description of Apple Pay (and I'm pretty sure Android Pay). In short, account holder information is not stored on client devices. Instead, a server-generated encrypted token usually is. 0 - https://news.ycombinator.com/item?id=15276574 https://news.ycombinator.com/item?id=15276574
- kalleboo 9y agoDon't all browsers and password managers already support credit card auto-fill? So it changes nothing from the status quo.