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

There's a conversation among @zkoch, @dlongley, and me starting with this comment: https://github.com/w3c/webpayments-method-identifiers/issues/9#issuecomment-240247631 -- I'm moving it to its own issue because it's not strictly relevant to issue 9.

The crux of the matter is: is it necessary to have some technical countermeasures to prevent malicious apps from registering with a claim of supporting payment methods that they cannot actually fulfill? If so, is there a different need for W3C-defined payment methods versus third-party-defined payment methods?

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