Re: [w3c/payment-handler] Revisiting Payment Method specific filter/capability matching (#157)

@rsolomakhin, thank you for the follow-up from yesterday's call. In terms of the spec, this suggests the following sorts of changes:

 * In the PaymentInstrument dictionary, replace "capabilities" with a canMakePayment() method 
    (and defining it).
 * Including either a requirement or a strongly worded suggestion that the user agent provide
    a means for the user to disable the method. (Would the method definition include a "disabled"
    status, or would that status be determined through some other means?)
 * Similarly, it could be useful to have an "undefined" state --no canMakePayment() method
    for the instrument-- which would mean "therefore matches any merchant-provided filters."
    Or perhaps something similar; we should discuss behavior in this case, as some payment
    apps may not wish or need to define this method.
 * Updating explanatory text and examples accordingly

Anything else you would add to this list?

Ian

-- 
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-handler/issues/157#issuecomment-303827851