public-payments-wg@w3.org from August 2016 by date

Wednesday, 31 August 2016

Minutes [Was: [Agenda] 31 August Payment Apps task force meeting] Ian Jacobs

Tuesday, 30 August 2016

Re: [Agenda] 1 September WPWG teleconference Dave Longley
[Agenda] 1 September WPWG teleconference Ian Jacobs
[Agenda] 31 August Payment Apps task force meeting Ian Jacobs

Friday, 26 August 2016

Re: [w3c/webpayments] Fix typo: `fishing` => `phishing`. (#172) maxpassion

Thursday, 25 August 2016

Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Christopher Allen
wpwg-ACTION-29: Ask the list about implementors and what they can support for an extant payment method for testing purposes. Web Payments Working Group Issue Tracker
wpwg-ACTION-28: Prepare a "state of affairs", due 2016-09-01 Web Payments Working Group Issue Tracker
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Adam Roach
[w3c/webpayments] Fix typo: `fishing` => `phishing`. (#172) Dave Longley
Payment app authenticity management proposal 刘大鹏(鹏成)

Wednesday, 24 August 2016

Minutes [Was: [Agenda] 24 August Payment Apps task force meeting] Ian Jacobs

Tuesday, 23 August 2016

[Agenda] 24 August Payment Apps task force meeting Ian Jacobs
[Agenda] 25 August WPWG teleconference Ian Jacobs
Re: Extension to 25 August (1pm EDT) [Was: CfC on publishing HTTP API and Core Messages] 刘大鹏(鹏成)

Monday, 22 August 2016

Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Gregory Estrade
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Jeffrey Burdges
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Gregory Estrade

Sunday, 21 August 2016

Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Jason Normore

Friday, 19 August 2016

Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Sailesh Panchang
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Manu Sporny
Re: Note on CfC Manu Sporny
RE: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED VIGNET cyril
Re: Introductions: new rep for Ceweb.br/Nic.br Adrian Hope-Bailie
RE: Introductions: new rep for Ceweb.br/Nic.br diogo@nic.br
RE: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Matt Saxon
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Tommy Thorsen
[Minutes] 18 August 2016 WPWG teleconference Ian Jacobs

Thursday, 18 August 2016

Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Leandro Bernal Minniti
Re: [w3c/webpayments] Pull filters out of payment method data (#170) Adrian Hope-Bailie
Re: [w3c/webpayments] Pull filters out of payment method data (#170) Adrian Hope-Bailie
Introductions: new rep for Ceweb.br/Nic.br Yaso
Note on CfC Adrian Hope-Bailie
RE: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Adrian Bateman
Draft regulatory technical standards on strong consumer authentication for payments Telford-Reed, Nick
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Sailesh Panchang
wpwg-ACTION-27: Send link to new eba regs to the wg Web Payments Working Group Issue Tracker
Re: [Agenda] 17 August Payment Apps task force meeting Shane McCarron

Wednesday, 17 August 2016

Tuesday, 16 August 2016

Monday, 15 August 2016

Re: Payment Apps Javascript Proposal Dave Longley
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Shane McCarron
Advancing the Web Payments HTTP API and Core Messages Manu Sporny
RE: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED David Ezell
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Ian Jacobs
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Manu Sporny
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Adrian Hope-Bailie
RE: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED David Ezell
Payment Apps Javascript Proposal Adrian Hope-Bailie
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Adrian Hope-Bailie
RE: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED David Ezell

Friday, 12 August 2016

[Minutes] 11 August 2016 WPWG teleconference Ian Jacobs

Thursday, 11 August 2016

wpwg-ACTION-26: Follow up with amex about security review of specs Web Payments Working Group Issue Tracker
wpwg-ACTION-25: Will write a proposal about storing numbers (#2) Web Payments Working Group Issue Tracker
Re: CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Adrian Hope-Bailie
CfC on publishing HTTP API and Core Messages - ACTION REQUIRED Telford-Reed, Nick
Reminder - WPWG meeting at 10:00 ET on 11 August (new meeting time) Ian Jacobs

Wednesday, 10 August 2016

Re: [w3c/webpayments] Overview document figure 5 (#171) Dave Longley
Re: Use of URNs for PMIs Ian Jacobs
Minutes [Was: [Agenda] 10 August Payment Apps task force meeting] Ian Jacobs
Re: [w3c/webpayments] Overview document figure 5 (#171) Rouslan Solomakhin
Re: [w3c/webpayments] Overview document figure 5 (#171) Dave Longley
Re: [w3c/webpayments] Overview document figure 5 (#171) Rouslan Solomakhin
Re: [w3c/webpayments] Overview document figure 5 (#171) Dave Longley
Re: [w3c/webpayments] Overview document figure 5 (#171) Rouslan Solomakhin
Re: [w3c/webpayments] Overview document figure 5 (#171) Dave Longley
Re: [w3c/webpayments] Overview document figure 5 (#171) Rouslan Solomakhin
Re: [w3c/webpayments] Overview document figure 5 (#171) Rouslan Solomakhin
Re: [w3c/webpayments] Overview document figure 5 (#171) rvm4
Agenda for tomorrow's teleconference Telford-Reed, Nick
Re: [w3c/webpayments] Overview document figure 5 (#171) Shane McCarron
Re: [w3c/webpayments] Overview document figure 5 (#171) Rouslan Solomakhin

Tuesday, 9 August 2016

Re: Use of URNs for PMIs Adrian Hope-Bailie

Wednesday, 10 August 2016

[w3c/webpayments] Overview document figure 5 (#171) rvm4
Re: Use of URNs for PMIs Roy McElmurry

Tuesday, 9 August 2016

Re: Use of URNs for PMIs Adam Roach
Re: Use of URNs for PMIs Ian Jacobs
[Agenda] 10 August Payment Apps task force meeting Ian Jacobs

Monday, 8 August 2016

Friday, 5 August 2016

NEW weekly meeting time for Web Payments Working Group Ian Jacobs

Thursday, 4 August 2016

Re: [w3c/webpayments] Pull filters out of payment method data (#170) Manu Sporny
[w3c/webpayments] Pull filters out of payment method data (#170) Adrian Hope-Bailie
W3C has launched Patent Advisory Group for Web Payments Working Group Ian Jacobs
Signed REST Requests Anders Rundgren

Wednesday, 3 August 2016

Minutes [Was: [Agenda] 3 August Payment Apps task force meeting] Ian Jacobs
Re: POLL - Preferred time for WG calls going forward Kepeng Li
[Agenda] 3 August Payment Apps task force meeting Ian Jacobs

Tuesday, 2 August 2016

Re: POLL - Preferred time for WG calls going forward Marta Piekarska
Re: POLL - Preferred time for WG calls going forward Adrian Hope-Bailie
Re: POLL - Preferred time for WG calls going forward Christopher Allen
Re: POLL - Preferred time for WG calls going forward Shane McCarron
Re: POLL - Preferred time for WG calls going forward Adam Roach
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Adrian Hope-Bailie

Monday, 1 August 2016

Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Dave Longley
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Manu Sporny
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Manu Sporny
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Adrian Hope-Bailie
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Manu Sporny
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Adrian Hope-Bailie
Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] How can we optimize user experience when there is only one match? (#169) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] How can we optimize user experience when there is only one match? (#169) Adrian Hope-Bailie
Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) Adrian Hope-Bailie
Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) Adrian Hope-Bailie
Re: [w3c/webpayments] Should the browser pass user data it has collected (email etc) to the payment app? (#137) Adrian Hope-Bailie
Re: [w3c/webpayments] Should the browser pass user data it has collected (email etc) to the payment app? (#137) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] Should payment instrument details be included at registration? (#142) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] Should payment instrument details be included at registration? (#142) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] How should third-party payment apps be displayed by the browser? (#143) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] How should third-party payment apps be displayed by the browser? (#143) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] What should be the user experience when an app is recommended for two methods? (#155) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment apps] What should be the user experience when an app is recommended for two methods? (#155) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment Apps] “Security Error” on different origins (#157) Adrian Hope-Bailie
Re: [w3c/webpayments] [Payment Apps] “Security Error” on different origins (#157) Adrian Hope-Bailie
Re: Payment Request API Ian Jacobs
Payment Request API Avish Yeshurun

Last message date: Wednesday, 31 August 2016 14:03:16 UTC