Re: [w3c/payment-handler] Remove "instrument" concept from PaymentManager (#371)

> As per my understanding currently, the payment instrument is the only way to specify which payment method given payment handler supports. Payment manager sets the payment instrument with the method specifying the payment method identifier.

The `PaymentInstruments` is only used when a payment handler is installed explicitly. Today it is involved in the setting of a payment handler's supported payment methods, but it doesn't need to be. The original post at the top has a proposal for how this functionality can still be supported in a world without `PaymentInstruments`.

> > So far, there is no payment handler that actually leverages the capability of exposing instruments to the browser. So I'm taking this as a signal that this capability is not useful. Removing it would simplify browser's implementation. But if a developer demonstrates a real use case for this capability, we would definitely consider keeping it.
> 
> At the moment there are very little payment handlers in general, so I doubt the conclusion that the capability of exposing instruments is not useful. 

Fair enough.

> We've tried in one of the early prototypes to expose multiple instruments from single payment handler and it didn't work as expected in Chrome, because the instruments weren't displayed on the list.

Can you elaborate a bit more how it didn't work as expected? What's the ideal user flow you'd like to achieve?

-- 
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/371#issuecomment-635623925