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

Adam Roach

Re: Encrypting basic card data (Friday, 15 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Encrypting basic card data (Saturday, 9 July)
Group Photo from Face-to-Face (Friday, 8 July)
Re: Thoughts on Native Payments (Wednesday, 6 July)
Re: Thoughts on Native Payments (Wednesday, 6 July)
Thoughts on Native Payments (Tuesday, 5 July)

adamroach

Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Tuesday, 5 July)

Adrian Bateman

RE: Encrypting basic card data (Monday, 11 July)
RE: Encrypting basic card data (Sunday, 10 July)

Adrian Hope-Bailie

PMI proposal (Friday, 29 July)
Re: Concerns about Core Messages specification (Thursday, 21 July)
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) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168) (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168) (Wednesday, 20 July)
Concerns about Core Messages specification (Wednesday, 20 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Tuesday, 19 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Tuesday, 19 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Tuesday, 19 July)
Re: POLL - Preferred time for WG calls going forward (Monday, 18 July)
POLL - Preferred time for WG calls going forward (Monday, 18 July)
Re: ACTION REQUIRED: Payment Method Identifiers (Monday, 18 July)
ACTION REQUIRED: Payment Method Identifiers (Monday, 18 July)
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) (Monday, 18 July)
Re: Comments on HTTP API before publishing FPWD (Friday, 15 July)
Re: Comments on HTTP API before publishing FPWD (Thursday, 14 July)
Comments on HTTP API before publishing FPWD (Thursday, 14 July)
Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) (Wednesday, 13 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Wednesday, 13 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Wednesday, 13 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Wednesday, 13 July)
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) (Tuesday, 12 July)
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) (Tuesday, 12 July)
Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) (Tuesday, 12 July)
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) (Tuesday, 12 July)
Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) (Tuesday, 12 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Web Payments Overview published (Monday, 11 July)
WPWG - No Meeting - 14 July (Monday, 11 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Security and Privacy Considerations (Monday, 11 July)
Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) (Monday, 11 July)
Re: Encrypting basic card data (Saturday, 9 July)
Encrypting basic card data (Saturday, 9 July)
[w3c/webpayments] [Payment App] PROPOSAL: Payment Apps are javascript code that use event listeners to get the PaymentRequest (#163) (Friday, 8 July)
[w3c/webpayments] [Payment Apps] What is the process for rendering the payment app UI (#162) (Friday, 8 July)
[w3c/webpayments] [Payment Apps] Display may be subject to user and local policy (consider UA making security decisions etc) (#161) (Friday, 8 July)
[w3c/webpayments] [Payment Apps] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#160) (Friday, 8 July)
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) (Friday, 8 July)
[w3c/webpayments] [Payment Request] Should we allow a "polling" mechanism for websites to not invoke the API if there are no enabled methods (#159) (Friday, 8 July)
[w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) (Friday, 8 July)
Re: ISO 4217 proposal to improve support for digital currencies (Thursday, 7 July)
Re: Thoughts on Native Payments (Tuesday, 5 July)
Re: Web Payments Architecture Summary? (Tuesday, 5 July)
Re: [w3c/webpayments] Minor fix to register also (#154) (Monday, 4 July)
[w3c/webpayments] Minor fix to register also (#154) (Monday, 4 July)
Re: [w3c/webpayments] Add reference to origin and fix a mistake in the registration API (#153) (Monday, 4 July)
[w3c/webpayments] Add reference to origin and fix a mistake in the registration API (#153) (Monday, 4 July)
Payment Apps Proposal (Monday, 4 July)
Re: Security Review of 3 WPWG WDs (using W3C TAG checklist) (Monday, 4 July)
Re: Security Review of 3 WPWG WDs (using W3C TAG checklist) (Monday, 4 July)
Re: [w3c/webpayments] Registration: Should payment instrument details be included? (#142) (Sunday, 3 July)
Re: [w3c/webpayments] Editorial walk-through (#152) (Sunday, 3 July)
Re: [w3c/webpayments] Editorial walk-through (#152) (Sunday, 3 July)
Re: [w3c/webpayments] Replace empty section on development payment app good practices (#151) (Friday, 1 July)
Re: New payment method draft (Friday, 1 July)

Anders Rundgren

Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) (Friday, 15 July)
Re: Encrypting basic card data (Friday, 15 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Wednesday, 13 July)
Re: [w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) (Wednesday, 13 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Wednesday, 13 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Wednesday, 13 July)
Re: [Minutes] London FTF meeting (7-8 July 2016) (Wednesday, 13 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Security and Privacy Considerations (Saturday, 9 July)
Re: [w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) (Friday, 8 July)
[w3c/webpayments] [Payment App] How is Native App integration code supplied? (#164) (Friday, 8 July)
Re: Group Photo from Face-to-Face (Friday, 8 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Thursday, 7 July)
Re: Thoughts on Native Payments (Thursday, 7 July)
Re: Thoughts on Native Payments (Wednesday, 6 July)
Re: ANSI X9.122 Secure Customer Authentication for Internet Payments (Wednesday, 6 July)
Re: Thoughts on Native Payments (Wednesday, 6 July)
Re: ANSI X9.122 Secure Customer Authentication for Internet Payments (Tuesday, 5 July)

Erik Anderson

Re: Security and Privacy Considerations (Friday, 22 July)
Re: Encrypting basic card data (Thursday, 14 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: Security and Privacy Considerations (Friday, 8 July)
ANSI X9.122 Secure Customer Authentication for Internet Payments (Tuesday, 5 July)

Hackett, Conor

RE: Payment Apps Proposal (Thursday, 21 July)
RE: Payment Apps Proposal (Wednesday, 6 July)

Ian Jacobs

[Minutes] 28 July 2016 WPWG teleconference (Thursday, 28 July)
[Agenda] 28 July 2016 WPWG teleconference (Wednesday, 27 July)
WPWG Blog post on July FTF meeting (Wednesday, 27 July)
Minutes [Was: [Agenda] 27 July Payment Apps task force meeting] (Wednesday, 27 July)
[Agenda] 27 July Payment Apps task force meeting (Tuesday, 26 July)
[Time-sensitive] Please register WPWG FTF meeting on 19-20 September, and other parts of TPAC by 2 September (Tuesday, 26 July)
Payment Apps Task Force Update (Wednesday, 20 July)
Visa Europe disclosure of patents and exclusion of claims in Web Payments Working Group (Tuesday, 19 July)
Re: Encrypting basic card data (Monday, 18 July)
Re: POLL - Preferred time for WG calls going forward (Monday, 18 July)
Re: New payment method draft (Monday, 18 July)
[Minutes] London FTF meeting (7-8 July 2016) (Saturday, 9 July)
Re: W3C WPWG: Dinner for tonight (Friday, 8 July)
Re: ANSI X9.122 Secure Customer Authentication for Internet Payments (Tuesday, 5 July)
Updated (TR) drafts of Payment Request API and Payment Method Identifiers (Tuesday, 5 July)
Re: Web Payments Architecture Summary? (Monday, 4 July)
Security Review of 3 WPWG WDs (using W3C TAG checklist) (Monday, 4 July)

ianbjacobs

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) (Thursday, 21 July)
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) (Wednesday, 20 July)
[w3c/webpayments] [Payment apps] How can we optimize user experience when there is only one match? (#169) (Tuesday, 19 July)
[w3c/webpayments] [Payment app] Should merchants be able to limit matching to trusted apps? (#168) (Tuesday, 19 July)
Re: [w3c/webpayments] [Payment Apps] Split out enabled and supported methods (#158) (Tuesday, 19 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Tuesday, 19 July)
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) (Monday, 18 July)
Re: [w3c/webpayments] Security and Privacy Self-Review (#61) (Monday, 18 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Monday, 18 July)
Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Monday, 18 July)
Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) (Tuesday, 12 July)
Re: [w3c/webpayments] Editorial walk-through (#152) (Saturday, 2 July)
[w3c/webpayments] Editorial walk-through (#152) (Friday, 1 July)
[w3c/webpayments] Replace empty section on development payment app good practices (#151) (Friday, 1 July)
Re: [w3c/webpayments] Fix payment options references + proposal on recommended apps (#150) (Friday, 1 July)

Jason Normore

Jeff Burdges

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) (Wednesday, 27 July)

Katie Haritos-Shea GMAIL

RE: Group Photo from Face-to-Face (Friday, 8 July)

KETELS Kris

ISO 4217 proposal to improve support for digital currencies (Thursday, 7 July)

Laurent Castillo

[w3c/webpayments] [Payment Apps] What portion of the PaymentRequest is sent to the payment app? (#166) (Friday, 8 July)
[w3c/webpayments] [Payment App] Should the payment app registration be for Browsers only or also for other types of User Agents (#165) (Friday, 8 July)
[w3c/webpayments] [Payment Apps] “Security Error” on different origins (#157) (Thursday, 7 July)
[w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156) (Thursday, 7 July)
[w3c/webpayments] What should be the user experience when an app is recommended for two methods? (#155) (Thursday, 7 July)

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) (Saturday, 30 July)
Re: Concerns about Core Messages specification (Thursday, 21 July)
Re: Concerns about Core Messages specification (Wednesday, 20 July)
Re: Comments on HTTP API before publishing FPWD (Friday, 15 July)
Re: Comments on HTTP API before publishing FPWD (Thursday, 14 July)
Re: Comments on HTTP API before publishing FPWD (Thursday, 14 July)
Three new first public drafts: Overview, Core Messages, HTTP API (Wednesday, 13 July)
Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) (Monday, 11 July)
Web Payments Overview published (Monday, 11 July)
Re: Security and Privacy Considerations (Friday, 8 July)
Security and Privacy Considerations (Friday, 8 July)
Re: Web Payments Architecture Summary? (Tuesday, 5 July)
Presentation on Web Payments Core Messages and HTTP API (Monday, 4 July)
Web Payments Architecture Summary? (Monday, 4 July)

Marcos Cáceres

Re: [WICG/historical-paymentrequest] Web Payments WG relation to this repo (#71) (Wednesday, 20 July)
Re: [WICG/historical-paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) (Wednesday, 20 July)

Marta Piekarska

Re: Group Photo from Face-to-Face (Friday, 8 July)
Re: Security and Privacy Considerations (Friday, 8 July)

Matt Saxon

RE: New payment method draft (Monday, 4 July)

Melvin Carvalho

Re: Web Payments Architecture Summary? (Monday, 4 July)

Michael[tm] Smith

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) (Friday, 29 July)
Re: Thoughts on Native Payments (Wednesday, 6 July)
Re: Web Payments Architecture Summary? (Tuesday, 5 July)

Mountie Lee

Re: W3C WPWG: Dinner for tonight (Friday, 8 July)
Re: New payment method draft (Tuesday, 5 July)
Re: New payment method draft (Friday, 1 July)

Nick Shearer

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) (Monday, 18 July)
Re: New payment method draft (Monday, 4 July)

Peter Potgieser

RE: New Web Payments Architecture document proposal (Sunday, 3 July)

Rouslan Solomakhin

Re: Payment Apps Proposal (Tuesday, 5 July)

Roy McElmurry

Re: Encrypting basic card data (Monday, 11 July)

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) (Saturday, 30 July)
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) (Friday, 29 July)
ReSpec and messed up characters in the ToC jump at F2F (Tuesday, 12 July)
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) (Tuesday, 12 July)
Re: Encrypting basic card data (Monday, 11 July)
Re: [w3c/webpayments] How should the group update documents in 'TR' space? (#167) (Monday, 11 July)
[w3c/webpayments] How should the group update documents in 'TR' space? (#167) (Monday, 11 July)
Re: Web Payments Overview published (Monday, 11 July)
Re: Security and Privacy Considerations (Friday, 8 July)
Re: Web Payments Architecture Summary? (Wednesday, 6 July)

Sullivan, Brian (Alpha)

W3C WPWG: Dinner for tonight (Thursday, 7 July)

Telford-Reed, Nick

No meeting tomorrow (21st July) (Wednesday, 20 July)
NO meeting tomorrow (Wednesday, 13 July)
RE: WPWG - No Meeting - 14 July (Monday, 11 July)
Face to face notes (Wednesday, 6 July)
RE: Web Payments Architecture Summary? (Tuesday, 5 July)
RE: Payment Apps Proposal (Monday, 4 July)

Tommy Thorsen

Web Payments Working Group Issue Tracker

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 (Thursday, 28 July)
wpwg-ACTION-23: Look into what the right practice is if we use urns. (Thursday, 28 July)
wpwg-ACTION-22: Try to get a security review within bpce (Thursday, 7 July)
wpwg-ACTION-21: Try to get a security review organized within worldpay (Thursday, 7 July)
wpwg-ACTION-20: Work on concrete spec language around currency codes (Thursday, 7 July)

Zach Koch

Re: ACTION REQUIRED: Payment Method Identifiers (Monday, 18 July)

刘大鹏(鹏成)

New payment method draft (Friday, 1 July)

Last message date: Saturday, 30 July 2016 19:40:17 UTC