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

I'm struggling to get a handle on this issue while all the specs are in flux. Is there an example somewhere of how this pieces together, end-to-end. FWIW, this could go in an `explainer.md` or readme in the root of the repo ([example](https://github.com/jakearchibald/background-fetch/blob/master/README.md)), in case others are struggling to get a handle on what's going on.

Specifically, how are things expected to work (or not work) when the payment provider "foo" is supported by a shop, but it's not one of the stored "user agent-based payment app"s?

-- 
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#issuecomment-273151111

Received on Tuesday, 17 January 2017 13:14:35 UTC