public-webpayments-specs@w3.org from October 2016 by date

Friday, 28 October 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Zach Koch

Tuesday, 25 October 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Zach Koch
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Adrian Hope-Bailie

Friday, 21 October 2016

• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) Jeff Burdges

Thursday, 20 October 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Dave Longley
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) ianbjacobs
• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) Dave Longley

Wednesday, 19 October 2016

• Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) ianbjacobs
• [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) rvm4
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) ianbjacobs
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Editorial fixes and clarifications (#66) ianbjacobs
• [w3c/webpayments-payment-apps-api] Editorial fixes and clarifications (#66) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Add note to design considerations about ephemeral data for unregistered apps and step in invokation procedure (#65) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) adamroach
• Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) ianbjacobs
• [w3c/webpayments-payment-apps-api] Add note to design considerations about ephemeral data for unregistered apps and step in invokation procedure (#65) Jason Normore
• Re: [w3c/webpayments-payment-apps-api] Update (#64) ianbjacobs
• [w3c/webpayments-payment-apps-api] Update (#64) ianbjacobs

Tuesday, 18 October 2016

• Re: [w3c/browser-payment-api] Supporting push payment methods (#224) ianbjacobs

Monday, 17 October 2016

• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Adrian Hope-Bailie

Friday, 14 October 2016

• [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Should merchants be able to limit matching to trusted apps? (#1) ianbjacobs
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny

Thursday, 13 October 2016

• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Adrian Hope-Bailie

Wednesday, 12 October 2016

• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Dave Longley
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) ianbjacobs
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) ianbjacobs
• Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) Manu Sporny
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) mattsaxon

Monday, 10 October 2016

• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) Adrian Hope-Bailie

Friday, 7 October 2016

• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) Andre Lyver
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) Lukasz Olejnik

Thursday, 6 October 2016

• Re: [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) ianbjacobs
• Re: [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) adamroach
• [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18) adamroach
• Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) adamroach
• Re: [w3c/webpayments-methods-card] Add privacy and security section (#8) adamroach
• Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) adamroach
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) ianbjacobs
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) Shane McCarron
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) Adrian Hope-Bailie
• Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Cleaned up text (#52) ianbjacobs
• Re: [w3c/webpayments-payment-apps-api] Cleaned up text (#52) ianbjacobs
• Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) adamroach
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) Shane McCarron

Tuesday, 4 October 2016

• Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) ianbjacobs
• Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) Adrian Hope-Bailie
• Re: [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) ianbjacobs

Monday, 3 October 2016

• [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) adamroach
• [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) adamroach

Last message date: Friday, 28 October 2016 01:32:35 UTC