[Payment apps] Should payment instrument details be included at registration?

[ianbjacobs]

Should the registration data also include details about payment instruments? This would allow the browser to display more detail and facilitate selection. The details might not be "all the information" but enough (e.g., a user-provided mnemonic label) to guide user selection. The browser might also use this information to improve per-instrument pricing.

[adrianhopebailie]

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]

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

[adrianhopebailie]

Migrated to w3c/payment-handler#12