[w3c/browser-payment-api] Why another API? (#203)

The goal, the idea, and the different data structures of this specification is looking really good.

However, I do not understand why this has to be a new browser API.
With browser crypto capabilities and cross-domain/cross-window communication I think it should be possible to create a "wallet" as an offline-capable web application.
I have been playing with the idea but hit some bumps in the communications layer (https://github.com/srcagency/browser-bus).

If this is something that has been already discussed, could someone link me there?

A related project: http://substack.net/offline_decentralized_single_sign_on_in_the_browser

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/203