[browser-payment-api] Should a payment app identifier (URL) or a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46)

Migrating from https://github.com/w3c/webpayments/issues/30:

> If the payment app identifier or payment method identifier is a URL, should there be a resource that can be fetched from the URL? 

Yes. We should suggest that the resource should be machine-readable (expressed as JSON-LD, at a minimum) for the reasons specified here:

http://www.w3.org/TR/json-ld/#introduction

> Is there a need to describe the payment method at the URL or provide some other information?

We should not require it, but encourage it. 

At a bare minimum, you could publish a human readable string in various languages for the payment method / app. You could also publish the payment method and/or apps branding image.

You could also make it so that a payment method URL may list the payment apps that are capable of processing the payment method. This would make it easy for user agents to retrieve a payment app if one isn't available in the user agent already. It could address the "no available payment apps" use case. I'm not suggesting that's how it would work, just that it seems like there are enough use cases to think more deeply about it.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/46