wallet can be based not on server side but also on secure element as client side. that has issues for key ownership (who own my key or wallet?) same origin policy (is my wallet restricted specific web site only?) On Tue, Oct 28, 2014 at 10:09 AM, Anders Rundgren < anders.rundgren.net@gmail.com> wrote: > On 2014-10-28 17:40, Mountie Lee wrote: > >> Hi. >> >> I have a doubt about payment wallet as w3c standard. >> >> if wallet is implemented inside of browser, >> will it cause the wallet locked into specific browser? >> >> if user initiated wallet in firefox, is the content of wallet viewable in >> chrome? >> > > Good question! > > It the wallet is server-based I guess it could be browser-independent. > > A wallet inside of the browser is another possibility. I leave that > to Mozilla who I believe is plotting with such schemes. > > FWIW, I have suggested "decomposing" the wallet into OS-based credentials > that would be viewable through signed JavaScript modules which should be > browser-independent. > > I doubt that the W3C actually will take on wallet standardization, there > are simply too many ways of doing it... > > Anders > > >> >> >> -- >> Mountie Lee >> >> PayGate >> CTO, CISSP >> Tel : +82 2 2140 2700 >> E-Mail : mountie@paygate.net <mailto:mountie@paygate.net> >> >> > -- Mountie Lee PayGate CTO, CISSP Tel : +82 2 2140 2700 E-Mail : mountie@paygate.net
Received on Tuesday, 28 October 2014 17:48:31 UTC