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

Thursday, 31 March 2016

[Minutes] 31 March 2016 WPWG Teleconference Ian Jacobs
wpwg-ACTION-17: Submit a pr for http api into the proposals folder for the wpwg repo. Web Payments Working Group Issue Tracker
Re: The Web Browser API Incubation Anti-Pattern Jeff Jaffe
RE: The Web Browser API Incubation Anti-Pattern Telford-Reed, Nick
Re: The Web Browser API Incubation Anti-Pattern Adrian Hope-Bailie
Re: The Web Browser API Incubation Anti-Pattern Anders Rundgren
The Web Browser API Incubation Anti-Pattern Manu Sporny

Wednesday, 30 March 2016

Final editors' draft Telford-Reed, Nick
Re: Update on getting to a Call for Consensus Manu Sporny

Tuesday, 29 March 2016

[Agenda] 31 March WPWG teleconference Ian Jacobs
Update on getting to a Call for Consensus Telford-Reed, Nick

Friday, 25 March 2016

RE: Call for consensus update Telford-Reed, Nick

Thursday, 24 March 2016

Re: Call for consensus update Shane McCarron

Monday, 21 March 2016

Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) mattsaxon

Friday, 18 March 2016

Re: [paymentrequest] Redirect specs to the Web Payments WG versions (#69) Ade Bateman
Call for consensus update Telford-Reed, Nick

Thursday, 17 March 2016

[Minutes] 17 March 2016 WPWG Teleconference Ian Jacobs
RE: Important telecon on Thursday 17th March at 16h00 UTC (12pm EDT, 9am PDT, 4pm GMT, David Ezell
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Marcos Caceres
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Marcos Caceres

Wednesday, 16 March 2016

Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Dave Longley
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Manu Sporny
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Manu Sporny
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Melvin Carvalho
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Marcos Caceres
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Marcos Caceres
Re: [paymentrequest] Conflation of manifest + payments seem unnecessary (#70) ianbjacobs
[paymentrequest] Conflation of manifest + payments seem unnecessary (#70) Marcos Caceres

Tuesday, 15 March 2016

RE: Important telecon on Thursday 17th March at 16h00 UTC (12pm EDT, 9am PDT, 4pm GMT, Telford-Reed, Nick
Re: Important telecon on Thursday 17th March at 16h00 UTC (12pm EDT, 9am PDT, 4pm GMT, Ian Jacobs
Important telecon on Thursday 17th March at 16h00 UTC (12pm EDT, 9am PDT, 4pm GMT, Telford-Reed, Nick

Monday, 14 March 2016

Saturday, 12 March 2016

Re: Updates to "Payment Request API Architecture" Shane McCarron

Friday, 11 March 2016

[webpayments] Adding registration proposal (#113) Zach Koch
Updates to "Payment Request API Architecture" Ian Jacobs
Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) Jeff Burdges
Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) mattsaxon
Re: [webpayments] How are third-party native wallets integrated? (#42) Anders Rundgren

Thursday, 10 March 2016

[Minutes] 10 March teleconference Ian Jacobs
New list: public-webpayments-specs@w3.org to mirror spec repo notifications Ian Jacobs
wpwg-ACTION-16: Reach out to wg participants to secure reviews Web Payments Working Group Issue Tracker
wpwg-ACTION-15: Review payment request api spec by march 15th 2016 (and attempt to do the other ones as well). Web Payments Working Group Issue Tracker
Re: [webpayments] How are third-party native wallets integrated? (#42) Anders Rundgren
Re: [webpayments] How are third-party native wallets integrated? (#42) Ade Bateman
Re: [webpayments] How are third-party native wallets integrated? (#42) Anders Rundgren
Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) Adrian Hope-Bailie
Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) ianbjacobs
Re: [webpayments] Registration: How is registration information updated? (#111) Adrian Hope-Bailie
Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) Adrian Hope-Bailie
Re: [webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112) ianbjacobs

Wednesday, 9 March 2016

Tuesday, 8 March 2016

Re: [webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) Erik Anderson

Friday, 4 March 2016

Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) mattsaxon
Re: Blog post on WPWG meeting and next steps Ian Jacobs
Blog post on WPWG meeting and next steps Ian Jacobs

Thursday, 3 March 2016

wpwg-ACTION-14: Look at dates when worldpay could host a meeting Web Payments Working Group Issue Tracker
wpwg-ACTION-13: Create poll for f2f days at tpac 2016 Web Payments Working Group Issue Tracker
[paymentrequest] Redirect specs to the Web Payments WG versions (#69) Ade Bateman
Re: [paymentrequest] Use [SecureContext] instead of manually checking inside the PaymentRequest constructor (#58) Ade Bateman
Re: [paymentrequest] Use [SecureContext] instead of manually checking inside the PaymentRequest constructor (#58) Ade Bateman
Re: [paymentrequest] Spec references are all pretty outdated (#57) Ade Bateman
Re: [paymentrequest] Spec references are all pretty outdated (#57) Ade Bateman
Re: [paymentrequest] Support for "enrollment" use of API (#43) Ade Bateman
Re: [paymentrequest] Support for "enrollment" use of API (#43) Ade Bateman
Re: [paymentrequest] Overridng Common Payment Instruments (#21) Ade Bateman
Re: [paymentrequest] Overridng Common Payment Instruments (#21) Ade Bateman
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Ade Bateman
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Ade Bateman
Re: [paymentrequest] boolean arguments are an anti-pattern; consider separate methods for complete() (#54) Ade Bateman
Re: [paymentrequest] boolean arguments are an anti-pattern; consider separate methods for complete() (#54) Ade Bateman
Re: [paymentrequest] At the time complete() is called, your ability to say success (true) or failure (false) may depend on the payment method (#67) Ade Bateman
Re: [paymentrequest] At the time complete() is called, your ability to say success (true) or failure (false) may depend on the payment method (#67) Ade Bateman
Re: [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) Ade Bateman
Re: [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) Ade Bateman
Re: [paymentrequest] Combine API parameters into a single request object + options (#41) Ade Bateman
Re: [paymentrequest] Combine API parameters into a single request object + options (#41) Ade Bateman
Re: [paymentrequest] No mention of non-decimal currencies (#40) Ade Bateman
Re: [paymentrequest] No mention of non-decimal currencies (#40) Ade Bateman

Wednesday, 2 March 2016

Tuesday, 1 March 2016

Re: [webpayments] Gh pages (#109) mattsaxon
[webpayments] Gh pages (#109) mattsaxon
Re: [webpayments] Taler flows (#106) mattsaxon

Last message date: Thursday, 31 March 2016 19:35:37 UTC