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

@adamroach,

> Representing a browser vendor, this is something that worries me also. It is a major reason that I see the Payment Request API as fundamentally inseparable from the Payment App API. The result of this WG's effort really needs to be a level playing field for payment providers, and the best way to ensure that is to have a uniform and nondiscriminatory way for payment apps to register and interact.

Yes -- and I think ensuring that we have a minimal API for merchants to call to get their payment request message to the user's Payment App of choice is important. This is another reason I prefer providing low-level, scope-limited, composable, reusable APIs and components.

I'm fine with browsers offering their own composition of these things in a special browser UI that covers the 80% case, but I do think merchants should be able to construct their own UI offerings as well -- whilst still getting appropriate access to Payment Apps and whatever other helpful features the user agent can assist with.

---
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-220846691