Should payment instrument details be included at registration?

[adrianhopebailie]

Migrated from w3c/webpayments#142

@ianbjacobs said:

I wouldn't call these "payment instruments" but I support the idea of apps being able to register multiple "choices" for the user that reflect different combinations of payment method identifiers.

Apps can use this to reflect the instruments that the user has installed or just to put the choice of payment method or funding source in the initial app selection list.

See also: w3c/payment-request#185 (comment)

@adrianhopebailie said:

The latest payment apps proposal includes the idea of "payment options" which supports this requirement.

A payment app (single endpoint URL) can register multiple payment options (groups of supported payment methods, a single label and icon for user selection).

[ianbjacobs]

@rsolomakhin has weighed in on this question: " I have heard feedback that this may not be desirable for the first iteration of the payment app spec, because it's one more layer of abstraction with marginal benefit. Let's stick with one-to-one mapping here for now. So BobPay should be able to display only one item on browser UI: "BobPay"."

[ianbjacobs]

As of the 30 November call I believe there was consensus to include options; see this edit to resolve this issue:
0176dfb