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

Saturday, 30 July 2016
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Shane McCarron
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Manu Sporny
Friday, 29 July 2016
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Shane McCarron
- PMI proposal Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Michael[tm] Smith
Thursday, 28 July 2016
- [Minutes] 28 July 2016 WPWG teleconference Ian Jacobs
- wpwg-ACTION-24: Work with chairs + team contacts to formalize who is responsible for the activities mentioned at the ftf around tokenized card payment method spec, and payment method spec good practices Web Payments Working Group Issue Tracker
- wpwg-ACTION-23: Look into what the right practice is if we use urns. Web Payments Working Group Issue Tracker
Wednesday, 27 July 2016
- [Agenda] 28 July 2016 WPWG teleconference Ian Jacobs
- WPWG Blog post on July FTF meeting Ian Jacobs
- Minutes [Was: [Agenda] 27 July Payment Apps task force meeting] Ian Jacobs
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Jeff Burdges
Tuesday, 26 July 2016
- [Agenda] 27 July Payment Apps task force meeting Ian Jacobs
- [Time-sensitive] Please register WPWG FTF meeting on 19-20 September, and other parts of TPAC by 2 September Ian Jacobs
Friday, 22 July 2016
- Re: Security and Privacy Considerations Erik Anderson
Thursday, 21 July 2016
- Re: Concerns about Core Messages specification Manu Sporny
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) ianbjacobs
- Re: Concerns about Core Messages specification Adrian Hope-Bailie
- RE: Payment Apps Proposal Hackett, Conor
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Tommy Thorsen
Wednesday, 20 July 2016
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) ianbjacobs
- No meeting tomorrow (21st July) Telford-Reed, Nick
- Re: Concerns about Core Messages specification Manu Sporny
- Payment Apps Task Force Update Ian Jacobs
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168) Adrian Hope-Bailie
- Concerns about Core Messages specification Adrian Hope-Bailie
- Re: [WICG/historical-paymentrequest] Web Payments WG relation to this repo (#71) Marcos Cáceres
- Re: [WICG/historical-paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Marcos Cáceres
Tuesday, 19 July 2016
- [w3c/webpayments] [Payment apps] How can we optimize user experience when there is only one match? (#169) ianbjacobs
- [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168) ianbjacobs
- Visa Europe disclosure of patents and exclusion of claims in Web Payments Working Group Ian Jacobs
- Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) ianbjacobs
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) ianbjacobs
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
Monday, 18 July 2016
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) ianbjacobs
- Re: Encrypting basic card data Ian Jacobs
- Re: [w3c/webpayments] Security and Privacy Self-Review (#61) ianbjacobs
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) ianbjacobs
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) ianbjacobs
- Re: POLL - Preferred time for WG calls going forward Adrian Hope-Bailie
- Re: POLL - Preferred time for WG calls going forward Ian Jacobs
- POLL - Preferred time for WG calls going forward Adrian Hope-Bailie
- Re: ACTION REQUIRED: Payment Method Identifiers Adrian Hope-Bailie
- Re: ACTION REQUIRED: Payment Method Identifiers Zach Koch
- Re: New payment method draft Ian Jacobs
- ACTION REQUIRED: Payment Method Identifiers Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Tommy Thorsen
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Nick Shearer
Friday, 15 July 2016
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) Anders Rundgren
- Re: Encrypting basic card data Anders Rundgren
- Re: Comments on HTTP API before publishing FPWD Adrian Hope-Bailie
- Re: Encrypting basic card data Adam Roach
- Re: Comments on HTTP API before publishing FPWD Manu Sporny
Thursday, 14 July 2016
- Re: Encrypting basic card data Erik Anderson
- Re: Comments on HTTP API before publishing FPWD Manu Sporny
- Re: Comments on HTTP API before publishing FPWD Adrian Hope-Bailie
- Re: Comments on HTTP API before publishing FPWD Manu Sporny
- Comments on HTTP API before publishing FPWD Adrian Hope-Bailie
Wednesday, 13 July 2016
- NO meeting tomorrow Telford-Reed, Nick
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Anders Rundgren
- Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) 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 App] How is Native App integration code supplied? (#164) Anders Rundgren
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Anders Rundgren
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Anders Rundgren
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Adrian Hope-Bailie
- Re: [Minutes] London FTF meeting (7-8 July 2016) Anders Rundgren
- Three new first public drafts: Overview, Core Messages, HTTP API Manu Sporny
Tuesday, 12 July 2016
- ReSpec and messed up characters in the ToC jump at F2F Shane McCarron
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Jason Normore
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Jason Normore
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Shane McCarron
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) Adrian Hope-Bailie
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) ianbjacobs
Monday, 11 July 2016
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) Manu Sporny
- Re: Encrypting basic card data Shane McCarron
- Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) Shane McCarron
- Re: Encrypting basic card data Anders Rundgren
- [w3c/webpayments] How should the group update documents in 'TR' space? (#167) Shane McCarron
- Re: Encrypting basic card data Roy McElmurry
- Re: Web Payments Overview published Shane McCarron
- Re: Encrypting basic card data Adam Roach
- Re: Encrypting basic card data Adrian Hope-Bailie
- Re: Encrypting basic card data Adrian Hope-Bailie
- Re: Encrypting basic card data Erik Anderson
- RE: Encrypting basic card data Adrian Bateman
- Re: Encrypting basic card data Adrian Hope-Bailie
- Re: Encrypting basic card data Erik Anderson
- RE: WPWG - No Meeting - 14 July Telford-Reed, Nick
- Re: Web Payments Overview published Adrian Hope-Bailie
- Web Payments Overview published Manu Sporny
- WPWG - No Meeting - 14 July Adrian Hope-Bailie
- Re: Encrypting basic card data Adrian Hope-Bailie
- Re: Security and Privacy Considerations Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) Adrian Hope-Bailie
Sunday, 10 July 2016
- RE: Encrypting basic card data Adrian Bateman
Saturday, 9 July 2016
- [Minutes] London FTF meeting (7-8 July 2016) Ian Jacobs
- Re: Encrypting basic card data Adrian Hope-Bailie
- Re: Encrypting basic card data Adam Roach
- Encrypting basic card data Adrian Hope-Bailie
- Re: Security and Privacy Considerations Anders Rundgren
Friday, 8 July 2016
- Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) Anders Rundgren
- Re: Security and Privacy Considerations Erik Anderson
- RE: Group Photo from Face-to-Face Katie Haritos-Shea GMAIL
- [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166) Laurent Castillo
- [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) Laurent Castillo
- Re: Group Photo from Face-to-Face Marta Piekarska
- Re: Security and Privacy Considerations Marta Piekarska
- [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) Anders Rundgren
- [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163) Adrian Hope-Bailie
- [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162) Adrian Hope-Bailie
- [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161) Adrian Hope-Bailie
- [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160) Adrian Hope-Bailie
- Re: [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- [w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) Adrian Hope-Bailie
- [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) Adrian Hope-Bailie
- Re: Group Photo from Face-to-Face Anders Rundgren
- Group Photo from Face-to-Face Adam Roach
- Re: Security and Privacy Considerations Shane McCarron
- Re: Security and Privacy Considerations Manu Sporny
- Re: W3C WPWG: Dinner for tonight Ian Jacobs
- Security and Privacy Considerations Manu Sporny
- Re: W3C WPWG: Dinner for tonight Mountie Lee
Thursday, 7 July 2016
- Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Anders Rundgren
- wpwg-ACTION-22: Try to get a security review within bpce Web Payments Working Group Issue Tracker
- wpwg-ACTION-21: Try to get a security review organized within worldpay Web Payments Working Group Issue Tracker
- Re: Thoughts on Native Payments Anders Rundgren
- Re: ISO 4217 proposal to improve support for digital currencies Adrian Hope-Bailie
- ISO 4217 proposal to improve support for digital currencies KETELS Kris
- wpwg-ACTION-20: Work on concrete spec language around currency codes Web Payments Working Group Issue Tracker
- W3C WPWG: Dinner for tonight Sullivan, Brian (Alpha)
- [w3c/webpayments] [Payment Apps] “Security Error” on different origins (#157) Laurent Castillo
- [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) Laurent Castillo
- [w3c/webpayments] What should be the user experience when an app is recommended for two methods? (#155) Laurent Castillo
Wednesday, 6 July 2016
- RE: Payment Apps Proposal Hackett, Conor
- Re: Thoughts on Native Payments Anders Rundgren
- Re: Thoughts on Native Payments Adam Roach
- Re: Thoughts on Native Payments Adam Roach
- Face to face notes Telford-Reed, Nick
- Re: Web Payments Architecture Summary? Shane McCarron
- Re: ANSI X9.122 Secure Customer Authentication for Internet Payments Anders Rundgren
- Re: Thoughts on Native Payments Anders Rundgren
- Re: Thoughts on Native Payments Michael[tm] Smith
Tuesday, 5 July 2016
- Re: Thoughts on Native Payments Adrian Hope-Bailie
- Thoughts on Native Payments Adam Roach
- Re: ANSI X9.122 Secure Customer Authentication for Internet Payments Ian Jacobs
- Updated (TR) drafts of Payment Request API and Payment Method Identifiers Ian Jacobs
- Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) adamroach
- Re: ANSI X9.122 Secure Customer Authentication for Internet Payments Anders Rundgren
- Re: Web Payments Architecture Summary? Adrian Hope-Bailie
- RE: Web Payments Architecture Summary? Telford-Reed, Nick
- Re: Web Payments Architecture Summary? Manu Sporny
- ANSI X9.122 Secure Customer Authentication for Internet Payments Erik Anderson
- Re: Payment Apps Proposal Rouslan Solomakhin
- Re: New payment method draft Mountie Lee
- Re: Web Payments Architecture Summary? Michael[tm] Smith
Monday, 4 July 2016
- Re: Web Payments Architecture Summary? Melvin Carvalho
- Re: New payment method draft Nick Shearer
- Re: Web Payments Architecture Summary? Ian Jacobs
- Presentation on Web Payments Core Messages and HTTP API Manu Sporny
- Web Payments Architecture Summary? Manu Sporny
- RE: New payment method draft Matt Saxon
- RE: Payment Apps Proposal Telford-Reed, Nick
- Re: [w3c/webpayments] Minor fix to register also (#154) Adrian Hope-Bailie
- [w3c/webpayments] Minor fix to register also (#154) Adrian Hope-Bailie
- Re: [w3c/webpayments] Add reference to origin and fix a mistake in the registration API (#153) Adrian Hope-Bailie
- [w3c/webpayments] Add reference to origin and fix a mistake in the registration API (#153) Adrian Hope-Bailie
- Payment Apps Proposal Adrian Hope-Bailie
- Re: Security Review of 3 WPWG WDs (using W3C TAG checklist) Adrian Hope-Bailie
- Re: Security Review of 3 WPWG WDs (using W3C TAG checklist) Adrian Hope-Bailie
- Security Review of 3 WPWG WDs (using W3C TAG checklist) Ian Jacobs
Sunday, 3 July 2016
- RE: New Web Payments Architecture document proposal Peter Potgieser
- Re: [w3c/webpayments] Registration: Should payment instrument details be included? (#142) Adrian Hope-Bailie
- Re: [w3c/webpayments] Editorial walk-through (#152) Adrian Hope-Bailie
- Re: [w3c/webpayments] Editorial walk-through (#152) Adrian Hope-Bailie
Saturday, 2 July 2016
- Re: [w3c/webpayments] Editorial walk-through (#152) ianbjacobs
Friday, 1 July 2016
- [w3c/webpayments] Editorial walk-through (#152) ianbjacobs
- Re: New payment method draft Mountie Lee
- Re: [w3c/webpayments] Replace empty section on development payment app good practices (#151) Adrian Hope-Bailie
- [w3c/webpayments] Replace empty section on development payment app good practices (#151) ianbjacobs
- Re: New payment method draft Adrian Hope-Bailie
- Re: [w3c/webpayments] Fix payment options references + proposal on recommended apps (#150) ianbjacobs
- New payment method draft 刘大鹏(鹏成)

Last message date: Saturday, 30 July 2016 19:40:17 UTC
Archived on: Friday, 17 January 2020 16:43:18 UTC

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