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

Adam Roach

• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Monday, 9 May)
• User Consent and Addresses (Friday, 6 May)
• Undiscussed (?) issues in Payments API (Wednesday, 4 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)

adamroach

• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Wednesday, 18 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Friday, 13 May)

Adrian Bateman

• RE: User Consent and Addresses (Friday, 6 May)
• RE: Undiscussed (?) issues in Payments API (Thursday, 5 May)
• RE: Payment Method Identifiers (Wednesday, 4 May)

Adrian Hope-Bailie

• GitHub updates and new repos (Tuesday, 31 May)
• Re: [w3c/webpayments] Should payment method specifications contain WebIDL? (#133) (Tuesday, 31 May)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Tuesday, 31 May)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Tuesday, 31 May)
• [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Tuesday, 31 May)
• [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) (Tuesday, 31 May)
• [w3c/webpayments] Should payment method specifications contain WebIDL? (#133) (Tuesday, 31 May)
• Re: Web Payments Demo (Saturday, 28 May)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Saturday, 28 May)
• Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110) (Saturday, 28 May)
• Re: Web Payments Demo (Saturday, 28 May)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Friday, 27 May)
• Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110) (Friday, 27 May)
• Re: Web Payments Demo (Friday, 27 May)
• Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110) (Thursday, 26 May)
• Agenda - 26 May (Wednesday, 25 May)
• Re: Web Payments Demo (Wednesday, 25 May)
• Re: Google I/O talk about PaymentRequest (Saturday, 21 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: AGENDA - Web Payments WG call - 19 May (Thursday, 19 May)
• AGENDA - Web Payments WG call - 19 May (Thursday, 19 May)
• Re: Updates to Payment Apps wiki page (Wednesday, 18 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Wednesday, 18 May)
• New payment apps proposal (Wednesday, 18 May)
• Re: [w3c/webpayments] Update reference labels to match other docs (#117) (Wednesday, 18 May)
• Re: [w3c/webpayments] Update reference labels to match other docs (#117) (Wednesday, 18 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Wednesday, 18 May)
• Re: [web-payments/web-payments-http-api] Source points to the wrong repo (#1) (Tuesday, 17 May)
• Re: [web-payments/web-payments-http-api] Issues point to the wrong repo (#2) (Tuesday, 17 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Monday, 16 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Monday, 16 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Monday, 16 May)
• [w3c/webpayments] Payment Apps (#129) (Friday, 13 May)
• Re: Updates to Payment Apps wiki page (Friday, 13 May)
• Re: Updates to Payment Apps wiki page (Thursday, 12 May)
• TechCrunch article on Wallets (Thursday, 12 May)
• Re: Agenda for our call tomorrow (Thursday, 12 May)
• Issues for today's call (Thursday, 12 May)
• Re: User Consent and Addresses (Wednesday, 11 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Hardware Security CG (Tuesday, 10 May)
• Updates to Payment Apps wiki page (Monday, 9 May)
• Re: Dealing with Wallets (Friday, 6 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: New repos for specs (Wednesday, 4 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: New repos for specs (Tuesday, 3 May)
• New repos for specs (Tuesday, 3 May)

Anders Rundgren

• New ISO standards for mobile payments (Thursday, 26 May)
• Re: Google I/O talk about PaymentRequest (Monday, 23 May)
• Re: Google I/O talk about PaymentRequest (Monday, 23 May)
• Re: The WebPayment API vs Personal Payment Terminal (Sunday, 22 May)
• The WebPayment API vs Personal Payment Terminal (Sunday, 22 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Friday, 20 May)
• Experiences with Native wallet Web shop integration (Sunday, 8 May)
• Re: Dealing with Wallets (Friday, 6 May)
• Re: Dealing with Wallets (Friday, 6 May)
• Dealing with Wallets (Friday, 6 May)

Andre Lyver

• Re: User Consent and Addresses (Tuesday, 10 May)

Anton Tveretin

• Suggestions on API change (Wednesday, 4 May)

Axel Nennker

• Re: [w3c/webpayments] Should payment method specifications contain WebIDL? (#133) (Tuesday, 31 May)
• Re: [w3c/webpayments] Should payment method specifications contain WebIDL? (#133) (Tuesday, 31 May)

Bakshi, Sanjay

• RE: Google I/O talk about PaymentRequest (Monday, 23 May)

Christopher Allen

• Re: Updates to Payment Apps wiki page (Wednesday, 11 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Wednesday, 4 May)

Dave Longley

• Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) (Wednesday, 18 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Tuesday, 3 May)

David Ezell

• RE: Updates to Payment Apps wiki page (Tuesday, 10 May)
• RE: Updates to Payment Apps wiki page (Tuesday, 10 May)

fredMeignien

• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Tuesday, 31 May)

GALINDO Virginie

• RE: Hardware Security CG (Tuesday, 10 May)

Håvard Molland

• Re: Updates to Payment Apps wiki page (Wednesday, 18 May)
• Re: Updates to Payment Apps wiki page (Friday, 13 May)
• Re: Updates to Payment Apps wiki page (Wednesday, 11 May)
• Re: Updates to Payment Apps wiki page (Wednesday, 11 May)

Ian Jacobs

• Re: GitHub updates and new repos (Tuesday, 31 May)
• [Minutes] 26 May 2016 WPWG teleconference (Thursday, 26 May)
• Google I/O talk about PaymentRequest (Friday, 20 May)
• [Minutes] 19 May 2016 WPWG Teleconference (Thursday, 19 May)
• [Minutes] 12 May 2016 WPWG teleconference (Thursday, 12 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Monday, 9 May)
• July 2016 Face-to-face meetings for Web Payments Interest and Working Group (Monday, 9 May)
• Re: Request for 2 new repositories (Friday, 6 May)
• [Minutes] 5 May 2016 WPWG teleconference (Thursday, 5 May)
• Re: Agenda for today? (Thursday, 5 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: [Suggestions on API change (Wednesday, 4 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)

ianbjacobs

• Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134) (Tuesday, 31 May)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Tuesday, 31 May)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Tuesday, 31 May)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Friday, 27 May)
• Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110) (Friday, 27 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Friday, 20 May)
• Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) (Wednesday, 18 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Monday, 16 May)

Jason Normore

• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Tuesday, 31 May)
• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Tuesday, 31 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Monday, 16 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Thursday, 5 May)

Katie Haritos-Shea GMAIL

• RE: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)
• RE: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)
• RE: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)

KETELS Kris

• comments on web payment HTTP API and core message components (Tuesday, 3 May)

KUNTZ Vincent

• FW: comments on web payment HTTP API and core message components (Wednesday, 4 May)
• RE: comments on web payment HTTP API and core message components (Wednesday, 4 May)

Manu Sporny

• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Tuesday, 31 May)
• Re: [w3c/webpayments] Terminology across all Web Payments documents should be aligned (#135) (Tuesday, 31 May)
• Re: Google I/O talk about PaymentRequest (Friday, 27 May)
• Re: [web-payments/web-payments-http-api] Issues point to the wrong repo (#2) (Tuesday, 17 May)
• Re: [web-payments/web-payments-http-api] Issues point to the wrong repo (#2) (Tuesday, 17 May)
• Re: [web-payments/web-payments-http-api] Source points to the wrong repo (#1) (Tuesday, 17 May)
• Re: [web-payments/web-payments-http-api] Source points to the wrong repo (#1) (Tuesday, 17 May)
• Regrets for the next two weeks (Monday, 9 May)
• Re: Spec-Ops Comments on Web Payments Core Messages 1.0 (Saturday, 7 May)
• Editor's Drafts for Web Payments Core Messages and HTTP API (Friday, 6 May)
• Re: Request for 2 new repositories (Friday, 6 May)
• Request for 2 new repositories (Friday, 6 May)
• Re: comments on web payment HTTP API and core message components (Thursday, 5 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Thursday, 5 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Thursday, 5 May)
• Re: Spec-Ops comments on Web Payments HTTP API 1.0 (Thursday, 5 May)
• Summary of feedback on proposed adoption of Core Messages/HTTP API (Thursday, 5 May)
• Re: Review of Payment Apps Proposal (Wednesday, 4 May)
• Re: Payment Method Identifiers (Wednesday, 4 May)
• Re: comments on web payment HTTP API and core message components (Tuesday, 3 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)
• Basic implementation of Payment App, Payment Mediator, and Merchant App (HTTP API) (Monday, 2 May)

Matt Saxon

• RE: Review of Payment Apps Proposal (Friday, 6 May)
• RE: New repos for specs (Wednesday, 4 May)
• Re: New repos for specs (Tuesday, 3 May)

mattsaxon

• Re: [w3c/webpayments] New Architecture Proposal (#125) (Wednesday, 4 May)

Melvin Carvalho

• Re: Updates to Payment Apps wiki page (Wednesday, 18 May)
• [web-payments/web-payments-http-api] Issues point to the wrong repo (#2) (Tuesday, 17 May)
• [web-payments/web-payments-http-api] Source points to the wrong repo (#1) (Tuesday, 17 May)
• Re: Updates to Payment Apps wiki page (Saturday, 14 May)
• Re: Updates to Payment Apps wiki page (Wednesday, 11 May)
• Re: Request for 2 new repositories (Friday, 6 May)

Michael[tm] Smith

• Re: Web Payments Demo (Friday, 27 May)
• Re: Web Payments Demo (Wednesday, 25 May)
• Re: Payment Method Identifiers (Thursday, 5 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)

Nick Shearer

• Re: Web Payments Demo (Friday, 27 May)
• Re: User Consent and Addresses (Tuesday, 10 May)

Rouslan Solomakhin

• Re: GitHub updates and new repos (Tuesday, 31 May)
• Re: Web Payments Demo (Friday, 27 May)
• Re: Web Payments Demo (Friday, 27 May)
• Re: Web Payments Demo (Thursday, 26 May)
• Re: Google I/O talk about PaymentRequest (Monday, 23 May)
• Re: Google I/O talk about PaymentRequest (Monday, 23 May)
• Re: Google I/O talk about PaymentRequest (Monday, 23 May)
• Re: Google I/O talk about PaymentRequest (Sunday, 22 May)

Shane McCarron

• Re: Agenda for our call tomorrow (Thursday, 12 May)
• Re: Request for 2 new repositories (Friday, 6 May)
• Agenda for today? (Thursday, 5 May)

Telford-Reed, Nick

• RE: Web Payments Demo (Friday, 27 May)
• Agenda for our call tomorrow (Wednesday, 11 May)
• RE: Request for 2 new repositories (Friday, 6 May)

Tommy Thorsen

• Re: [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Friday, 27 May)
• [w3c/webpayments] Clarify the concepts of enabled vs. supported (#132) (Friday, 27 May)
• Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110) (Friday, 27 May)
• Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110) (Thursday, 26 May)
• Web Payments Demo (Wednesday, 25 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Monday, 23 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Friday, 20 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Friday, 20 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Friday, 20 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Thursday, 19 May)
• Re: [w3c/webpayments] Choosing between javascript and http communication. (#131) (Thursday, 19 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Wednesday, 18 May)
• [w3c/webpayments] Choosing between javascript and http communication. (#131) (Wednesday, 18 May)
• Re: [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Wednesday, 18 May)
• Re: Updates to Payment Apps wiki page (Wednesday, 18 May)
• [w3c/webpayments] Letting the payment app decide between HTTP and Javascript communication (#130) (Wednesday, 18 May)
• Re: Updates to Payment Apps wiki page (Wednesday, 18 May)
• Re: [w3c/webpayments] Payment Apps (#129) (Monday, 16 May)
• Re: User Consent and Addresses (Wednesday, 11 May)
• Re: User Consent and Addresses (Wednesday, 11 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: User Consent and Addresses (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: Updates to Payment Apps wiki page (Tuesday, 10 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Tuesday, 3 May)
• Re: Call for reviews of HTTP API and Core Messages proposals (Monday, 2 May)

Tony Arcieri

• Re: The WebPayment API vs Personal Payment Terminal (Sunday, 22 May)

Zach Koch

• Payment Method Identifiers (Wednesday, 4 May)

Last message date: Tuesday, 31 May 2016 22:37:30 UTC