News for hackers. Stuff that matters.
Re:Payment Request API by Etheryte on Monday March 02, 2020 @09:15AM (#22464592)
> User agents (e.g., browsers) facilitate the payment flow between merchant and user.

I'm very torn on how to feel about this. On one hand, it would be better than the current bonanza where every online shop has their own home-rolled thing for credit cards, on the other, I don't like the idea of having my CC info stacked on top of the already massive trove of data Google is gathering about me.

Re:Payment Request API by ancarda on Monday March 02, 2020 @09:17AM (#22464604)
Why not switch to a different browser then, such as Firefox?

Worth saying today Chrome already supports storing credit card details for auto-fill.

Re:Payment Request API by Jaruzel on Monday March 02, 2020 @09:28AM (#22464676)
There is absolutely no way I would let Google (or any other browser provider for that matter) have a copy of my Credit Card Details.
Re:Payment Request API by ancarda on Monday March 02, 2020 @09:33AM (#22464709)
Nobody is forcing you to do that. Your browser is very likely going to have a "Don't remember" option.

You're free to keep your credit card details in your password manager or type it out every time.

Re:Payment Request API by testuser66 on Monday March 02, 2020 @11:03AM (#22465514)
You do realise that storing them (be it Google, LastPass, or any other hopefully trusty manager) is safer than carrying them around on you, right?
Re:Payment Request API by polyglotnetwork on Monday March 02, 2020 @11:20AM (#22465727)
The parent is concerned about privacy, not security.
Re:Payment Request API by djsumdog on Monday March 02, 2020 @09:28AM (#22464682)
Really? I remember over a decade ago credit card information was being stored in inputbox history in Firefox and they added patches to prevent from storing cc info. Of course that was a side-effect/bug of the autocomplete fields and I'm sure in Chrome it was a planned addition, but still...
Re:Payment Request API by ThePhysicist on Monday March 02, 2020 @09:35AM (#22464730)
That’s more a failure of the form creator as password fields were never persisted to the history. If you don’t tell the browser that the input is for sensitive data it won’t protect it of course.
Re:Payment Request API by tiborsaas on Monday March 02, 2020 @09:22AM (#22464639)
Chrome can already manage CC data. If it recognizes a CC form, then it will prompt a dialog where you enter your CVV code and it will fill the form for you.
Re:Payment Request API by rco8786 on Monday March 02, 2020 @09:24AM (#22464650)
It’s opt-in though. This would effectively make it mandatory no?
Re:Payment Request API by pjc50 on Monday March 02, 2020 @09:31AM (#22464699)
No? It won't obliterate other forms of payment processing in the medium term. And I'd be very surprised if a "gpay is now mandatory for online shopping" monopoly was left to develop.
Re:Payment Request API by CSMastermind on Monday March 02, 2020 @12:42PM (#22466691)
> every online shop has their own home-rolled thing for credit cards

Who is out there hand-rolling credit card auth?

Use Stripe, Paypal, Amazon, or something similar folks, PCI compliance is a nightmare.

Re:Payment Request API by SquareWheel on Monday March 02, 2020 @03:12PM (#22468394)
> Who is out there hand-rolling credit card auth?

It's extremely common, and few of them get PCI compliance right. In my experience they usually just feed a website form directly into email.

This is your mom and pops, local bed and breakfast, small specialty store type websites. They hire someone to just make it work.

Re:Payment Request API by danShumway on Monday March 02, 2020 @09:54AM (#22464887)
More to the point, aren't both Mozilla and Google looking to deprecate user agents? Why are new features being built on top of them?
Re:Payment Request API by nix0n on Monday March 02, 2020 @10:11AM (#22465008)
They're deprecating the "User Agent String", but they are still considered "User Agents".
Re:Payment Request API by danShumway on Monday March 02, 2020 @10:49AM (#22465362)
Ah, I mis-conflated. Thanks for the correction.