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

As mentioned previously, I'm in support of changing the name from `PaymentInstrument` to better reflect that what is being registered is actually some kind of user-selectable hint (plus some constraints by which the browser can filter) that the use and PaymentHandler mutually understand.

In my view, it has never necessarily represented a "payment instrument", rather there's some contract between the user and the PaymentHandler regarding what the specific meaning of the hint will entail. The only requirement, as far as the mediator is concerned, is that the hint include the aforementioned constraints so that matching can occur.

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