- From: Ian Jacobs <ij@w3.org>
- Date: Tue, 14 Feb 2017 11:04:00 -0600
- To: Payments WG <public-payments-wg@w3.org>
Hi all, Minutes from today’s payment apps call: https://www.w3.org/2017/02/14-apps-minutes#item06 Next call: 21 February Ian > On Feb 13, 2017, at 12:33 PM, Ian Jacobs <ij@w3.org> wrote: > > Participants in the payments app task force, > > We meet 14 January at 10am ET. > > Previous meeting 7 February: > https://www.w3.org/2017/02/07-apps-minutes > > WebEx: > http://www.w3.org/2017/01/paymentapps-2017.ics > > Ian > > ======== > I continue to update the "Proposal" based on discussion: > https://github.com/w3c/webpayments-payment-apps-api/wiki/Proposal-20170130 > > > Here are the primary issues [0] and where I think we are. > [0] https://github.com/w3c/webpayments-payment-apps-api/issues > > ---------------------------------------- > Information provided to the payment app (99) > Consensus to use new request/response objects for payment apps > > See Marcos' suggestion that the objects align well with those in PR API > https://lists.w3.org/Archives/Public/public-payments-wg/2017Feb/0016.html > > ---------------------------------------- > OPENING WINDOWS (73, 97). > Consensus to a new openClientWindow method. > > ACTION: Marcos and Tommy to draft a proposal for openClientWindow. > > ---------------------------------------- > FILTERS/CAPABILITIES (83, 96) > > ACTION: Task force to review Ian's proposal (for browser's matching string sets) and thread: > https://github.com/w3c/webpayments-payment-apps-api/issues/96#issuecomment-278754087 > > ---------------------------------------- > SETTING PAYMENT METHOD INFORMATION (95) > > ACTION: Task force to review Adrian's proposal (to use a new structure for payment app input and response data): > https://github.com/w3c/webpayments-payment-apps-api/issues/99#issuecomment-278326772 > > ---------------------------------------- > RECOMMENDED PAYMENT APPS (74, 79) > > ACTION: Task force to review Ian's proposal (to drop Recommended payment apps > from the payment app API but continue to investigate as a separate layer): > https://github.com/w3c/webpayments-payment-apps-api/issues/74#issuecomment-278340715 > > ACTION: Task force to review Tommy's approach to recommending apps when none available: > https://github.com/w3c/webpayments-payment-apps-api/issues/74#issuecomment-278941318 > > Should we put that code on the new developer site? > https://github.com/w3c/payment-request-info > > ---------------------------------------- > DISPLAY OF OPTIONS / GRANULARITY (90) > Consensus not to require user agents to display options if provided. > Still discussing use cases and granularity requirements (including desktop) > > ACTION: Andre to write up use cases for "wallet" containers within a payment app. > > ---------------------------------------- > ICONS AND LABELS / GRANULARITY (69, 70, 90)) > > ACTION: AdamR to write a proposal for providing icons and labels for different granularities. > Some were discussed 31 Jan: https://www.w3.org/2017/01/31-apps-minutes#item01 > > ---------------------------------------- > SETTING PAYMENT METHOD INFORMATION (95) > > ACTION: AdamR to write a proposal for setting payment method information at finer grain than setManifest. > The proposal will take into account Mathieu's desire for easy reset. > > ====================== > Next steps on the spec > > * Marcos suggested [1] that we write code to demonstrate the following: > > - Getting permission > - adding, removing, updating, payment methods > - handling .canMakePayment(), > - handling POSTing for payment (without a secure window). > - Getting the browser to open a secure window > - handling PaymentRequest .abort(), .updateWith() > - creating a PaymentResponse - and showing how it coordinates > between the secure window and merchant. > > Marcos asked for one or more people to work with him on this code. > > VOLUNTEERS? > > * I would like to update the Payment App API based on the recent > discussions and clearer model. I can spend some time on that > this week and next. The goal is to have an updated specification > for discussion at the FTF meeting. > > [1] https://lists.w3.org/Archives/Public/public-payments-wg/2017Feb/0016.html > > ======= > Next meeting > > * 21 February > > ======== > Other issues > https://github.com/w3c/webpayments-payment-apps-api/issues > > -- > Ian Jacobs <ij@w3.org> > https://www.w3.org/People/Jacobs/ > Tel: +1 718 260 9447 > > > > -- Ian Jacobs <ij@w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447
Received on Tuesday, 14 February 2017 17:04:08 UTC