News for hackers. Stuff that matters.

A comment on Payment Request API. Parent comment

Re:Payment Request API by rictic on Monday March 02, 2020 @03:31PM (#22468596)
Worth questioning why you want to store payment info. One common reason is for a faster subsequent checkout experience.

If this API gives a fast checkout experience without storing data, then you've potentially got the benefit of storing payment info without the exposure of storing sensitive data.

(disclosure: I work at google on the web, but not on anything payments related)

[ Parent | on HN ]
Re:Payment Request API by strictnein on Tuesday March 03, 2020 @02:30PM (#22477901)
Imagine the multiple ways a customer interacts with a large retailer. It won't always be through a specific browser tied to a Google/etc account. They'll likely order things through their work computer, home computer, phone browser, retail app, etc. The common account between those all will likely be the retail store's account, not a Google/etc account.

At a certain scale, any reduction of friction results in $xx million in increased sales.

[ Parent | on HN ]
Re:Payment Request API by rene_kapusta on Monday March 02, 2020 @03:54PM (#22468872)
Regarding storing sensitive data at the client -- how good / bad / secure is it to store data in the IndexedDB store (as this is the only option for web apps used in the PR modal)?
[ Parent | on HN ]