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

@tjconcept,

We distinguish the wallet part (which we will also work on and are calling "payment apps") from the role of the browser to display the user's available payment methods (which payment apps will support).

paymentRequest() only addresses the basic function of the browser as mediator, and what's different from existing APIs is that the browser will display native chrome, which should make the experience faster and well-integrated (and secure, etc.).

Ian

---
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#issuecomment-220779578