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

> Yes "payment instrument" is a real-world concept and won't go away. This bug is about the technical question of whether "payment instrument" should be exposed to the browser in the web payments architecture. Framed from the user's perspective, the question is: should the browser offer users choices of payment apps or choices of payment instruments from within the apps?

It's one of the fundamental questions for Web Payments. As a user, I personally would prefer a selection of the payment apps, but I guess there might be good arguments for the alternative approach.

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

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