Re: [w3c/payment-handler] Drop PaymentInstrument in favor of MethodCapability (#302)

I think the proposal here is to move away from a world where the Payment Handler defines a set of instruments/hints and instead declares what types of payments it can process. Chrome already only uses the instruments for that purpose (capabilities matching) and we don't display instruments (only the single PaymentManager's userHint might eventually be displayed). We don't plan on letting the user select anything more granular than the Payment Handler and instead will defer instrument selection to the Handler through openWindow. This seems consistent with what other implementers are looking at doing too.

As far as the name is concerned, Ian and I were also not 100% satisfied. We came up with PaymentMethod (which was already used in the Payment Request spec) and SupportedMethod (which isn't super reusable elsewhere in the spec if it comes back without a being in a "this is supported" context). Suggestions welcome!

-- 
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/302#issuecomment-387823140