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

adamroach

Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) (Wednesday, 19 October)
Re: [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) (Thursday, 6 October)
[w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#18) (Thursday, 6 October)
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) (Thursday, 6 October)
Re: [w3c/webpayments-methods-card] Add privacy and security section (#8) (Thursday, 6 October)
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) (Thursday, 6 October)
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) (Thursday, 6 October)
[w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) (Monday, 3 October)
[w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) (Monday, 3 October)

Adrian Hope-Bailie

Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Tuesday, 25 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Monday, 17 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Thursday, 13 October)
Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Monday, 10 October)
Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Thursday, 6 October)
Re: [w3c/webpayments-methods-card] Add text about why the api can reduce need to store credit card information (#17) (Tuesday, 4 October)

Andre Lyver

Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 7 October)

Dave Longley

Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 20 October)
Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 20 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)

ianbjacobs

Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Thursday, 20 October)
Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Wednesday, 19 October)
Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Wednesday, 19 October)
Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Wednesday, 19 October)
Re: [w3c/webpayments-payment-apps-api] Editorial fixes and clarifications (#66) (Wednesday, 19 October)
[w3c/webpayments-payment-apps-api] Editorial fixes and clarifications (#66) (Wednesday, 19 October)
Re: [w3c/webpayments-payment-apps-api] Add note to design considerations about ephemeral data for unregistered apps and step in invokation procedure (#65) (Wednesday, 19 October)
Re: [w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) (Wednesday, 19 October)
Re: [w3c/webpayments-payment-apps-api] Update (#64) (Wednesday, 19 October)
[w3c/webpayments-payment-apps-api] Update (#64) (Wednesday, 19 October)
Re: [w3c/browser-payment-api] Supporting push payment methods (#224) (Tuesday, 18 October)
[w3c/webpayments-payment-apps-api] Should payment apps implement payment method-specific filters? (#63) (Friday, 14 October)
Re: [w3c/webpayments-payment-apps-api] Should merchants be able to limit matching to trusted apps? (#1) (Friday, 14 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)
Re: [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) (Thursday, 6 October)
Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Thursday, 6 October)
Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) (Thursday, 6 October)
Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) (Thursday, 6 October)
Re: [w3c/webpayments-payment-apps-api] Cleaned up text (#52) (Thursday, 6 October)
Re: [w3c/webpayments-payment-apps-api] Cleaned up text (#52) (Thursday, 6 October)
Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) (Tuesday, 4 October)
Re: [w3c/webpayments-methods-card] Propose text about why the api can reduce need; without any recommendations (#16) (Tuesday, 4 October)

Jason Normore

[w3c/webpayments-payment-apps-api] Add note to design considerations about ephemeral data for unregistered apps and step in invokation procedure (#65) (Wednesday, 19 October)

Jeff Burdges

Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Friday, 21 October)

Lukasz Olejnik

Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Friday, 7 October)

Manu Sporny

Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Friday, 14 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Friday, 14 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Friday, 14 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)
Re: [w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)
[w3c/browser-payment-api] How are digital signatures supported for Payment Requests? (#291) (Wednesday, 12 October)

mattsaxon

Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Wednesday, 12 October)

rvm4

[w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Wednesday, 19 October)

Shane McCarron

Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Thursday, 6 October)
Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Thursday, 6 October)

Zach Koch

Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Friday, 28 October)
Re: [w3c/browser-payment-api] Introduce transaction_id and server callback (#292) (Tuesday, 25 October)

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