Issue updates based on WPWG FTF discussion - please be sure to add any others you have in mind

Hi all,

I reviewed the FTF minutes ([1], [2]) to extract issues that people raised during
the meeting. Some I found already appear in the issues lists. Below are the ones
I added today.

PLEASE NOTE: If YOU have other issues, please be sure to add them to the spec issues list or
the general issues list.

Ian

[1] https://www.w3.org/2016/02/23-wpwg-minutes
[2] https://www.w3.org/2016/02/24-wpwg-minutes

===============
Specs issues list

 Should API support billing address capture (for tax computation)?
 https://github.com/w3c/browser-payment-api/issues/27

 Should the payee be able to inspect the status of a payment?
 https://github.com/w3c/browser-payment-api/issues/28

 What happens when currency of offer differs from currency of selected payment instrument?
 https://github.com/w3c/browser-payment-api/issues/29

 Should we define nesting/grouping semantics for payment method identifier matching?
 https://github.com/w3c/browser-payment-api/issues/30

===============
General issues list

 Registration: App supports method but user has no instrument for that method
 https://github.com/w3c/webpayments/issues/110

 Registration: How is registration information updated?
 https://github.com/w3c/webpayments/issues/111

 Registration: Should we support payee knowing user has payee-controlled payment app?
 https://github.com/w3c/webpayments/issues/112

 Note: I used “registration” in the issue name but better practice might be using labels.

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447