@marcoscaceres I may be misunderstanding what you have done here but I think you have replaced an algorithm for _determining which handlers are suitable to process the payment request_ with an algorithm that _validates the payment method specific data_. We've all agreed that the latter is required but I think it should be in addition to the former not replace it. i.e. For all accepted methods in the request, validate the `data`, then for all known handlers establish if they can handle one of the accepted methods. The outcome is a list of potential handlers that determine what the browser can present to the user as options to process the payment request. This does beg the question as to whether methods with invalid data should just be discarded with a warning? -- 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/pull/536#issuecomment-308685059
Received on Thursday, 15 June 2017 09:52:58 UTC