After Stripe switched to iframes for payment forms, I am very happy to see this. Trying to wrestle a iframe credit card field to have same fonts and error handling as other fields in a form is a really annoying workaround considering how nice the plaintext tokenizers in the past were... Knowing that credit card fields might not be in our forms at all feels very cool
Payment Request API
61–70 of 128 posts
Re: Payment Request API
#62Earlier quoted context omitted.
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?
For certain decisions that seems like a false choice. For example, no amount of contribution would have stopped Netflix et al from pushing through EME as a web standard.
As bad as DRM is, EME is a good step towards killing Flash. And because of that, Netflix needs a replacement, and the studios aren’t just going to remove DRM requirements because Netflix says they won’t support DRM. I’m almost certain that if Netflix tried to remove DRM, the studios would balk and pull their content.
Re: Payment Request API
#63So 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?
Isn't kerberos supposed to do that?
Re: Payment Request API
#64Earlier quoted context omitted.
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.
I've seen both. When I wrote the post all the docs from the gateways I had access to called then iin with a historical note on bin. I done have access to those docs anymore though.
I've seen both. When I wrote the post all the docs from the gateways I had access to called it the iin with a historical note on bin. I don't have access to those docs anymore, though.
Edit: I really need to check when posting from my phone
Re: Payment Request API
#65Earlier quoted context omitted.
To enable micropayments for content such as news.
True micropayments integrated in browser would be amazing. Imagine instead of ads or subscriptions, you could pay a few pennies for an article. It would revolutionize online content, in a good way. Nobody would be willing to pay for clickbait type stuff, but I think people would be willing to pay for quality content and journalism.
True micropayments integrated in browser would be amazing.
You might want to check out Brave, a Chromium-based browser with micropayments built-in: https://brave.com/publishers/.
Re: Payment Request API
#66We might finally see HTTP error code 402 in action, then. https://tools.ietf.org/html/rfc2616#section-10.4.3
Re: Payment Request API
#67So 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...
And it's great! Also coming is the ability to share login credentials across domains.
Re: Payment Request API
#68Earlier quoted context omitted.
To enable micropayments for content such as news.
I fear this too. First they try to make HTTP impossible to use (nag pop up) to limit the websites, then they try to introduce pay-per-view model and subscription model. Welcome back to the pre-1999 AOL/MicrosoftNetwork/Compuserve/BTX/Minitel/etc - closed networks where pay-per-page-view was prevailing - then the free open WWW won, supported by advertising. The good thing, it only takes other websites that provide the…
Quality content costs money. How do you propose paying journalists to investigate and write? It's either ads, payments of some sort (micro or subscription) or state-sponsored media. My original comment was not out of fear, quite the opposite.
Re: Payment Request API
#69After Stripe switched to iframes for payment forms, I am very happy to see this. Trying to wrestle a iframe credit card field to have same fonts and error handling as other fields in a form is a really annoying workaround considering how nice the plaintext tokenizers in the past were... Knowing that credit card fields might not be in our forms at all feels very cool
Stripe offers a UI widget but you can still just design and code the form inputs yourself.