[w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48)

Let's figure out how to map payment app identifier (e.g., `https://alipay.com/some/path`) to the manifest filename (e.g., `https://alipay.com/some/path/payment-manifest.json`). I prefer fixed filename because of simplicity for both user agent implementers and payment app writers.

@adrianhopebailie wrote:

> I don't like this model of fixed names for the manifests at all. This feels like the favicon debacle all over again. If you want to identify a payment method use the actual URL where the manifest file is not an origin that then gets converted into a URL by some magic formula.

Favicon is indeed not ideal design, because user agents try to download `https://example.com/favicon.ico` when the user wants to see `https://example.com/some/path/to/resource`. We've all been annoyed at seeing `404 /favicon.ico` in our server logs.

However, I believe that I'm proposing something more similar to `index.html` pattern, i.e., user is pointing their user agent to `https://example.com/some/path/to/resource` but sees the contents of `https://example.com/some/path/to/resource/index.html` instead.

The user agent will dereference `https://alipay.com/some/path/payment-manifest.json` only when a merchant wants to use `https://alipay.com/some/path` for payments. Therefore, there should be no spurious `404 /some/path/payment-manifest.json` in server logs.

-- 
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/48