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

@andrewpaliga asked:

> What would be an example of an payment app on this list?

Imagine a website supports basic card payments but has not suggested any payment apps for the user to install so the payment request is likely to fail if the user has no payment apps that support basic card payments.

In this instance the user agent might suggest one or more payment apps that support basic card payments, possibly even their own built-in payment app.

@ianbjacobs said:

> The mediator must distinguish for user-installed payment apps, merchant suggestions,
and user agent suggestions.

In this instance the user agent is the mediator so I'm not sure what this means.

> Allowing the user to easily store credentials in the browser when there are no registered payment apps.

This should be done by offering the user user of a built-in payment app suggested by the browser. 

If the process of registering a third-party payment app is necessarily harder than simply using the browser to pay then the system provides unfair advantage to the browsers and it's unlikely users will ever install third party apps (or even know they exist)

---
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-215327417