Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173)

I am personally not that fond of the `defaultInstrumentKey` concept, as I find it a bit strange.

I think that if the payment handler is launched with the `instrumentKey` property set, it should proceed directly to pay with that instrument (with our without opening a window), or if it is launched without the `instrumentKey` it should show UI for selecting an existing instrument or configuring a new one.

The browser could present the payment handlers/instruments in such a way as to make sure the user is not put in a situation like Adrian's Scenario 2 above, where the default instrument prevents the user from selecting a different payment instrument. Even though a default instrument is provided by the payment handler, the browser should *also* give the user a way to invoke the payment handler without this payment instrument. Exactly how this is done is a UX design question, but it would for instance be possible to add a button on the right hand side of the item that represents the payment handler with its default instrument. Something like:

:credit_card: BobPay (Green) :black_nib:

... where clicking on the pen would invoke the payment handler without `instrumentKey` set, or clicking anywhere else on the item would invoke the payment handler with `instrumentKey` set to the key of the default instrument `Green`.


-- 
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/173#issuecomment-308508202