Re: [w3c/webpayments-method-identifiers] Resolve whether browsers need to police payment app claims of supported methods (#11)

> I'm more interested in real-world examples, as those are the problems I'm interested in prioritizing at this point and what should inform our design.

Every payment processor has relationships with their merchants that allow those merchants to accept payments using the payment method defined by that processor. In the real world this means AliPay, AndroidPay, Apple Pay, PayPal, WorldPay etc.

These processors MAY (and I think we can assume WILL in most cases) define a "proprietary" payment method. (In fact Alipay have already defined the payment method spec for theirs).

We should assume that these processors will also want to allow their merchants to publish payment apps that can process payment using these and other payment methods.

Therefor it follows that a proprietary payment method will want to have a way to link multiple payment apps from different origins to their payment method.

-- 
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/webpayments-method-identifiers/issues/11#issuecomment-240828636