[w3c/webpayments-payment-apps-api] Should payment instrument details be included at registration? (#12)

Migrated from https://github.com/w3c/webpayments/issues/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: https://github.com/w3c/browser-payment-api/issues/185#issuecomment-223047965

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

---
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/webpayments-payment-apps-api/issues/12