Re: [w3c/browser-payment-api] Payment app discovery (#155)

A question to address is; who should provide the suggested list?

We seem to all be implying that it is the payee but if they don't should the mediator also be able to suggest some payment apps?

Bare in mind that just as they track all sorts of other data on the Web browsers will very quickly have data on which apps support which payment methods (and maybe even how often payments are successfully processed by that app - see PR #153) and how to install those apps.

They will be very well placed to give users options if the payee doesn't suggest anything.

## PROPOSAL

 1. Add a section to the payment request where a payee can suggest payment apps that they know support payment methods they also support.
 1. Allow the mediator to also have a "backup" list of payment apps they know about and can suggest to the payer.
 1. Define an algorithm for the mediator (browser) that populates the app selection choices (in the following order of preference):
    1. The set of apps that are already registered and known to support the supported payment methods in the payment request.
    1. The set of apps suggested by the payee
    1. The set of apps suggested by the mediator

## Considerations

* The size of the list presented to the payee. Will the suggested apps ever even be shown?
* The change of focus when a user decides in the midst of a payment to go off and register a new app.

(Both sound like nice areas for UAs to differentiate and offer users a great experience)



---
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/browser-payment-api/issues/155#issuecomment-214401468