- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Fri, 11 Apr 2014 10:22:30 -0400
- To: public-webpayments@w3.org
On 04/11/2014 01:14 AM, Anders Rundgren wrote: > On 2014-04-11 01:44, Pindar Wong wrote: >> and 'running code' ;) > > ... in browsers supporting some new and for the purpose (payments) > necessary features. No, browser implementation should never be a requirement for the Web Payments work. We can build a solid Web payment system today without any browser upgrades. The solutions that this community creates shouldn't depend on browser manufacturers implementing particular features. More on this in a later email, but tying success to the implementation of particular features in a browser is a losing proposition. That said, if new security or interaction mechanisms (like TrustedUI, U2F, WebCrypto) become available natively in the browsers, then the whole payment ecosystem improves. We shouldn't put browser manufacturers in the critical path. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: The Worlds First Web Payments Workshop http://www.w3.org/2013/10/payments/
Received on Friday, 11 April 2014 14:22:53 UTC