Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153)

The WPWG discussed this today:
 https://www.w3.org/2017/07/20-wpwg-minutes.html#item06

* There is some support for the use cases (e.g., Worldpay, Airbnb) although also some sentiment that they may not be the top priority use cases.
* There is support for addressing these use cases through means other than specific API features (Wallet Dictionary). 
* The first alternative suggest was to use service workers with different scopes and independent Web app manifests. @rsolomakhin said he would be willing to write up an example for the spec about how to do this (once he has time).
* This raised the question about a hard dependency on web app manifest. There was some sentiment on the call that its implementation and spec status would likely remain ahead of payment handler, so this hard dependency was currently perceived as an important risk.
* The second alternative was to use subdomains, which offer web security benefits. However, there was also mention of certificate "cost" with this approach.

In summary, I'd like to propose that we remove the "Wallet" feature but mention in the spec how to fulfill the use cases through other means, including an example from Rouslan.

Ian

-- 
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/payment-handler/issues/153#issuecomment-316744069