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

@adrianhopebailie 
> Is [the Payment App Identifier] equivalent to the scope of the ServiceWorker for web-based Payment Apps? (I believe there have been some concerns about this)

I did raise a concern about this in the previous payment apps task force meeting, in the context of merchant-recommended payment apps. The current spec says that these should be provided by means of the Payment App Identifier, but that only works if you can find the manifest file based on the PAI. If we use the scope of the ServiceWorker for the PAI, that's not the case.

It is still possible to use the ServiceWorker scope as the PAI, but then the merchant needs to recommend apps by means of the url to the manifest file instead of the PAI (and we need to change section 4.4 to say this).

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

Received on Friday, 18 November 2016 10:06:38 UTC