Re: [w3c/payment-request] remove matching .data text from .show() (#578)

@adrianhopebailie,

> Another implementation of the handler could choose to fail fast here and indicate that it can't handle the request.

How `basic-card` behaves with respect to "capabilities" is also likely to be quite different from other payment methods. `basic-card` is essentially a data collection mechanism, whereas other payment methods may produce more legitimate reasons for payment handlers to be unable to provide certain capabilities. The "capability requirements" will not simply be used to restrict the payment handler UI, but rather, a payment handler will be unable to actually process the request. Allowing the user to select such a payment handler will result in an unpleasant user experience.

It would be nice to provide a generic mechanism for payment methods to use that does not require the browsers to do additional implementation for every new payment method. However, I suppose the argument could be made that the appropriate mechanism for expressing even those granular distinctions is a payment method identifier -- or put another way -- that *is inevitably* how it will happen if we don't have another mechanism in the spec.

So I would anticipate new payment method specs that have a need for this sort of thing to essentially define multiple payment method identifiers. This will produce bloat in payment request data, but I'm not sure how common this sort of thing will happen.

-- 
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/payment-request/pull/578#issuecomment-320980852