Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Payment Request API

w3.org

Post reply on HN
Print view View original

21–30 of 128 posts

Re: Payment Request API

#21

Post by jimktrains2 »

z1mm32m4n wrote: post #13
litzer wrote: post #5

For anyone else like me who was overwhelmed by all the information and just looking for summaries: "In one sentence, how does it work? Payment Request API enables a user to complete a transaction more easily by reusing information stored in the browser or third party payment apps." https://github.com/w3c/payment-request-info/wiki/FAQ

This also opens up the door to more secure payments. The "basic card" handler is one where the browser might just store your raw card number. But you can imagine that your bank might implement a payment handler that requires you to enter a 2fa code before using your card. When it comes down to it, a credit card number is kind of serving double as a username and password for online payments right now. This new API has…

Just a clarification, a credit card number is an iin, pan, and checksum.

http://jimkeener.com/posts/everyday-numbers-1

Re: Payment Request API

#22

Post by throwaway284534 »

swiley wrote: post #19
StavrosK wrote: post #18

So there's now a protocol for the browser to transparently share payment data with websites but we still can't get something to let the browser transparently log us in to websites?

The w3c seems to be run by people who make money on the web, not people who use the web.

The W3C is run by the same peers who frequent this and other tech forums. You can help by contributing to the organization, or you could hope for some internet points with snarky remarks. Which do you want to be remembered for?

Re: Payment Request API

#23

Post by ben_jones »

throwaway284534 wrote: post #22
swiley wrote: post #19

Earlier quoted context omitted.

The w3c seems to be run by people who make money on the web, not people who use the web.

The W3C is run by the same peers who frequent this and other tech forums. You can help by contributing to the organization, or you could hope for some internet points with snarky remarks. Which do you want to be remembered for?

While he could've worded it better he did provide valid criticism. I'm sure he is not the only person here who has profiteering concerns for the various bodies who govern the internet.

Re: Payment Request API

#25

Post by ChrisMorrisOrg »

Not sure if this is still the case, but Marcos from Mozilla did a talk on this at CampJS earlier this year. Apparently Chrome will send data about the items purchased to Google, even if you’re using a payment provider completely unrelated to Google.

Unlike Chrome, Firefox will apparently not send data about what you purchase back to Mozilla.

Edit: https://twitter.com/chrismorrisorg/status/896352427426799618

Re: Payment Request API

#26

Post by pfg »

StavrosK wrote: post #18

So there's now a protocol for the browser to transparently share payment data with websites but we still can't get something to let the browser transparently log us in to websites?

The W3C is working on this in the Web Authentication (webauthn) working group.

Re: Payment Request API

#27

Post by noway421 »

StavrosK wrote: post #18

So there's now a protocol for the browser to transparently share payment data with websites but we still can't get something to let the browser transparently log us in to websites?

This became a thing lately: https://developers.google.com/web/updates/2016/04/credential...

Re: Payment Request API

#28

Post by swiley »

throwaway284534 wrote: post #22
swiley wrote: post #19

Earlier quoted context omitted.

The w3c seems to be run by people who make money on the web, not people who use the web.

The W3C is run by the same peers who frequent this and other tech forums. You can help by contributing to the organization, or you could hope for some internet points with snarky remarks. Which do you want to be remembered for?

Alright "run" wasn't the right word, "heavily influenced by" is probably better.

They just seem to continuously standardize things that are very user hostile and only serve content distributors.

Re: Payment Request API

#29

Post by microcolonel »

ChrisMorrisOrg wrote: post #25

Not sure if this is still the case, but Marcos from Mozilla did a talk on this at CampJS earlier this year. Apparently Chrome will send data about the items purchased to Google, even if you’re using a payment provider completely unrelated to Google. Unlike Chrome, Firefox will apparently not send data about what you purchase back to Mozilla. Edit: https://twitter.com/chrismorrisorg/status/896352427426799618

Is there a source for this? That seems like a pretty outrageous thing for a browser to do.

Re: Payment Request API

#30

Post by lsaferite »

jimktrains2 wrote: post #21
z1mm32m4n wrote: post #13

Earlier quoted context omitted.

This also opens up the door to more secure payments. The "basic card" handler is one where the browser might just store your raw card number. But you can imagine that your bank might implement a payment handler that requires you to enter a 2fa code before using your card. When it comes down to it, a credit card number is kind of serving double as a username and password for online payments right now. This new API has…

Just a clarification, a credit card number is an iin, pan, and checksum. http://jimkeener.com/posts/everyday-numbers-1

Interesting that the post says the term BIN (vs. IIN) isn't commonly used anymore, but it's practically the only thing I've heard them called in the last 10+ years of ecomm dev.
Post reply on HN