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

@tjconcept writes:
> Yes, that's something which frightens me. Soon we'll have browsers fighting with payment methods, using devices as leverage and cutting deals with banks.

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.

The generic broker functionality you describe sounds interesting from a theoretical perspective, but it also sounds a bit like an ocean boiling exercise. That is, unless what you have in mind is simply "remove cross-origin protections." I assume that's not what you have in mind *per se*, but I encourage you to think really hard about whether what you're thinking about eventually has the same result.

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