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

Saturday, 30 April 2016

Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Michael[tm] Smith
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Manu Sporny
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Shane McCarron
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Shane McCarron
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) rvm4
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) rvm4
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) rvm4
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) rvm4

Friday, 29 April 2016

Re: [w3c/browser-payment-api] Change the way we request user data (#65) Andrew Paliga
Re: [w3c/browser-payment-api] Payment app discovery (#155) Shane McCarron
Re: [w3c/browser-payment-api] Payment app discovery (#155) Andrew Paliga
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Michael[tm] Smith
[w3c/browser-payment-api] API flow (#177) mattsaxon
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Nick S
Re: [w3c/browser-payment-api] Fix #129 (#153) mattsaxon
Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) mattsaxon
[w3c/browser-payment-api] Required fields (#176) mattsaxon
Re: [w3c/browser-payment-api] Do we need payment method identifier aliases? (#149) Erik Wilde
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) Ade Bateman
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) Ade Bateman
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman
[w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) Ade Bateman
Re: [w3c/browser-payment-api] Adding support for phone and email (#174) Ade Bateman
[w3c/browser-payment-api] Adding support for phone and email (#174) Ade Bateman
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) ianbjacobs
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) mattsaxon
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add section on internationalization (#53) Michael[tm] Smith
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Michael[tm] Smith
Re: [w3c/browser-payment-api] Add section on internationalization (#53) Ade Bateman
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Ade Bateman
Re: [w3c/browser-payment-api] Do we need payment method identifier aliases? (#149) Ade Bateman
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) Ade Bateman
Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) Tommy Thorsen
Re: [w3c/browser-payment-api] Fix old reference to items and use total/displayItems (#169) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should well-known identifiers be used for ubiquitous payment methods (#10) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Do we need payment method identifier aliases? (#149) Adrian Hope-Bailie
[w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update security and privacy considerations sections (#170) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Fix old reference to items and use total/displayItems (#169) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add previous publication metadata. (#167) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Nick S
Re: [w3c/browser-payment-api] Do we need payment method identifier aliases? (#149) Erik Wilde
Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman
Re: [w3c/browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Ade Bateman
Re: [w3c/browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Ade Bateman
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Ade Bateman
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Ade Bateman
[w3c/browser-payment-api] Updated to use [SecureContext] extended attribute. (#172) Ade Bateman
Re: [w3c/browser-payment-api] Add explicit note that shippingOptions is only required if requesting shipping (#128) Ade Bateman
Re: [w3c/browser-payment-api] Add explicit note that shippingOptions is only required if requesting… (#171) Ade Bateman
[w3c/browser-payment-api] Add explicit note that shippingOptions is only required if requesting… (#171) Ade Bateman
[w3c/browser-payment-api] Update security and privacy considerations sections (#170) Ade Bateman

Thursday, 28 April 2016

Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman
Re: [w3c/browser-payment-api] Fix old reference to items and use total/displayItems (#169) Ade Bateman
Re: [w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Shane McCarron
[w3c/browser-payment-api] Fix old reference to items and use total/displayItems (#169) Ade Bateman
[w3c/browser-payment-api] Remove issue #119 note and assert that total should be non-negative (#168) Ade Bateman
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Shane McCarron
Re: [w3c/browser-payment-api] Do we need payment method identifier aliases? (#149) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Do we need payment method identifier aliases? (#149) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] complete does not talk to the Payment App (#129) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] complete does not talk to the Payment App (#129) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Manu Sporny
Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Manu Sporny
Re: [w3c/browser-payment-api] Remove issue #48 label. (#165) Ade Bateman
Re: [w3c/browser-payment-api] Remove issue #48 label. (#165) Ade Bateman
Re: [w3c/browser-payment-api] Should list of accepted payment methods be strings or objects? (#48) Ade Bateman
Re: [w3c/browser-payment-api] Examples need updating with recent PRs (#164) Ade Bateman
Re: [w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (#166) Ade Bateman
Re: [w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (#166) Ade Bateman
Re: [w3c/browser-payment-api] Add previous publication metadata. (#167) Ade Bateman
[w3c/browser-payment-api] Add previous publication metadata. (#167) Ade Bateman
[w3c/browser-payment-api] Updated examples to reflect changes in recent PRs (#166) Ade Bateman
[w3c/browser-payment-api] Remove issue #48 label. (#165) Ade Bateman
Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Adrian Hope-Bailie
[w3c/browser-payment-api] Examples need updating with recent PRs (#164) Ade Bateman
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Ade Bateman
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Ade Bateman
Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Ade Bateman
Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Ade Bateman
Re: [w3c/browser-payment-api] Fix #129 (#153) hober
Re: [w3c/browser-payment-api] Fix #129 (#153) Ade Bateman
Re: [w3c/browser-payment-api] Fix #129 (#153) Ade Bateman
Re: [w3c/browser-payment-api] Refactor the supportedMethods and payment specific data (#162) Ade Bateman
Re: [w3c/browser-payment-api] Refactor the supportedMethods and payment specific data (#162) Ade Bateman
Re: [w3c/browser-payment-api] Separate total from line items. (#158) Ade Bateman
Re: [w3c/browser-payment-api] Separate total from line items. (#158) Ade Bateman
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Ade Bateman
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Ade Bateman
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Ade Bateman
Re: [w3c/browser-payment-api] Should PaymentItems have a type? (#163) Shane McCarron
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Jason Normore
[w3c/browser-payment-api] Should PaymentItems have a type? (#163) rvm4
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Jason Normore
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Dave Longley
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Nick S
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Dave Longley
Re: [w3c/browser-payment-api] Separate total from line items. (#158) Ade Bateman
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Ade Bateman
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Ade Bateman
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove id attribute from PaymentItem (#160) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment app discovery (#155) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Manu Sporny
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Dave Longley
Re: [w3c/browser-payment-api] Separate total from line items. (#158) Manu Sporny
Re: [w3c/browser-payment-api] Update complete() method to take a string and clarify its purpose (#161) Manu Sporny
Re: [w3c/browser-payment-api] Refactor the supportedMethods and payment specific data (#162) Manu Sporny

Wednesday, 27 April 2016

Tuesday, 26 April 2016

Re: [w3c/browser-payment-api] Fix #129 (#153) hober
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Payment app discovery (#155) Andrew Paliga
Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) mattsaxon
Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) mattsaxon
Re: [w3c/browser-payment-api] Specification of required fields (#114) mattsaxon
Re: [w3c/browser-payment-api] Specification of required fields (#114) mattsaxon
Re: [w3c/browser-payment-api] Payment app discovery (#155) Adrian Hope-Bailie

Monday, 25 April 2016

Re: [w3c/browser-payment-api] Identifiers or Locators (#150) kirkalx
Re: [w3c/browser-payment-api] Change the way we request user data (#65) ianbjacobs
Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Dave Longley
Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) ianbjacobs
Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Jeff Burdges
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Payment app discovery (#155) ianbjacobs
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] Fix #129 (#153) Zach Koch
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Dave Longley
Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Dave Longley
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Dave Longley
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Manu Sporny
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment app discovery (#155) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment app discovery (#155) Nick S
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie
[w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment app discovery (#155) Andrew Paliga
Re: [w3c/browser-payment-api] Payment app discovery (#155) Andrew Paliga
Re: [w3c/browser-payment-api] Payment app discovery (#155) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Andre Lyver
Re: [w3c/browser-payment-api] De-duplicate markup for “user agents” def (#156) Michael[tm] Smith
Re: [w3c/browser-payment-api] Support for negative amounts (#119) kirkalx
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) kirkalx
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Nick S
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Nick S
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) kirkalx
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Nick S
[w3c/browser-payment-api] De-duplicate markup for “user agents” def (#156) HubleGiter

Sunday, 24 April 2016

Re: [w3c/browser-payment-api] Payment app discovery (#155) kirkalx
Re: [w3c/browser-payment-api] Payment app discovery (#155) Shane McCarron
Re: [w3c/browser-payment-api] Payment app discovery (#155) kirkalx
Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) Jeff Burdges
Re: [w3c/browser-payment-api] Adding baseline CONTRIBUTING.md (c5b89a3) HubleGiter
Re: [w3c/browser-payment-api] Payment app discovery (#155) Shane McCarron
Re: [w3c/browser-payment-api] Payment app discovery (#155) ianbjacobs
Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) ianbjacobs
Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) ianbjacobs
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) kirkalx
Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Michael[tm] Smith
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) kirkalx
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) kirkalx
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) kirkalx

Saturday, 23 April 2016

Re: [w3c/browser-payment-api] Payment app discovery (#155) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Shane McCarron
Re: [w3c/browser-payment-api] Payment app discovery (#155) kirkalx
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) kirkalx
Re: [w3c/browser-payment-api] Fix #129 (#153) Zach Koch

Friday, 22 April 2016

Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Jeff Burdges
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Jeff Burdges
Re: [w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Fix #129 (#153) Dave Longley
Re: [w3c/browser-payment-api] Fix #129 (#153) Ade Bateman
Re: [w3c/browser-payment-api] Payment app discovery (#155) Rouslan Solomakhin
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Michael[tm] Smith
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) ianbjacobs
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Dave Longley
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) ianbjacobs
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Shane McCarron
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Michael[tm] Smith
[w3c/browser-payment-api] Payment app discovery (#155) Andrew Paliga
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Manu Sporny
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Dave Longley
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Shane McCarron
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Dave Longley
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Dave Longley
Re: [w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Dave Longley
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
[w3c/browser-payment-api] Should the browser API support the concept of "messages"? (#154) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Adding baseline README.md (c68b812) HubleGiter
Re: [w3c/browser-payment-api] Adding baseline README.md (c68b812) HubleGiter
Re: [w3c/browser-payment-api] Should the list of transaction types be extensible? (#112) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the list of transaction types be extensible? (#112) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Shane McCarron
[w3c/browser-payment-api] Fix #129 (#153) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Proposed text for issue 23. (#140) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove issue 55 note and add security considerations section. (#142) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Removing references to closed issues #47 and #56. (#144) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Handling non-decimal currencies (#14) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Handling non-decimal currencies (#14) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) kirkalx
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Shane McCarron
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Shane McCarron
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Erik Wilde

Thursday, 21 April 2016

Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Shane McCarron
Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) Shane McCarron
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) ianbjacobs
Re: [w3c/browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) ianbjacobs
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Dave Longley
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Dave Longley
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) ianbjacobs
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) ianbjacobs
Re: [w3c/browser-payment-api] General Comment on Registry Design (#148) ianbjacobs
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Nick S
Re: [w3c/browser-payment-api] Identifiers or Locators (#150) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fixing typo (#152) Ade Bateman
Re: [w3c/browser-payment-api] fixing typo (#152) Ade Bateman
[w3c/browser-payment-api] fixing typo (#152) Erik Wilde
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Erik Wilde
[w3c/browser-payment-api] Registry Access/Handling Registry Change (#151) Erik Wilde
[w3c/browser-payment-api] Identifiers or Locators (#150) Erik Wilde
[w3c/browser-payment-api] Identifier Aliases (#149) Erik Wilde
[w3c/browser-payment-api] General Comment on Registry Design (#148) Erik Wilde
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Ade Bateman
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Ade Bateman
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Ade Bateman
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Ade Bateman
Re: [w3c/browser-payment-api] Specify shipping address fields based on OASIS xAL. (#147) Ade Bateman
Re: [w3c/browser-payment-api] Specify shipping address fields based on OASIS xAL. (#147) Ade Bateman
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Ade Bateman
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Ade Bateman
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Dave Longley
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Rouslan Solomakhin
[w3c/browser-payment-api] Specify shipping address fields based on OASIS xAL. (#147) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Axel Nennker
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Axel Nennker
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Rouslan Solomakhin
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) rvm4
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) ianbjacobs
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Dave Longley
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) ianbjacobs
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Nick S
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Manu Sporny
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Flows issue 32 (#131) mattsaxon
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Shane McCarron
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Flows issue 32 (#131) mattsaxon
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Axel Nennker
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Axel Nennker
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Ade Bateman
Re: [w3c/browser-payment-api] Write-up proposal for shipping address fields (#6) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Nick Telford-Reed
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) mattsaxon
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Jason Normore

Wednesday, 20 April 2016

Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) Andrew Paliga
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) ianbjacobs
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) David Jackson
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Rouslan Solomakhin
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Shane McCarron
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Dave Longley
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Manu Sporny
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Ade Bateman
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Dave Longley
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) Manu Sporny
Re: [w3c/browser-payment-api] Issue Prioritisation Explainer (#105) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Issue Prioritisation Explainer (#105) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Payment instrument installation is platform-dependent (#8) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Remove issue 55 note and add security considerations section. (#142) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Removing references to closed issues #47 and #56. (#144) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) ianbjacobs
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Dave Longley
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Dave Longley
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payee be able to inspect the status of a payment? (#28) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] API Data Integrity (#31) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Adrian Hope-Bailie
[w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Shane McCarron
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Zach Koch
Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Andre Lyver

Tuesday, 19 April 2016

Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) Shane McCarron
Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) Andrew Paliga
Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) ianbjacobs
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
[w3c/browser-payment-api] Support for gift cards and discount codes (#145) Andrew Paliga
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) Dave Longley
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) Dave Longley
Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Shane McCarron
Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) ianbjacobs
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) Dave Longley
Re: [w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) Dave Longley
[w3c/browser-payment-api] Removing references to closed issues #47 and #56. (#144) Ade Bateman
[w3c/browser-payment-api] What semantics is needed for payment method specific data? (#143) ianbjacobs
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Ade Bateman
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Ade Bateman
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Ade Bateman
[w3c/browser-payment-api] Remove issue 55 note and add security considerations section. (#142) Ade Bateman
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Sebastien Domergue
Re: [w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Shane McCarron
Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Shane McCarron
Re: [w3c/browser-payment-api] Should a payment request be just data, or a programmable object? (#47) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a payment request be just data, or a programmable object? (#47) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Axel Nennker
Re: [w3c/browser-payment-api] Add reference to issue #45. (#79) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add reference to issue #49. (#83) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Adrian Hope-Bailie
[w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51) Adrian Hope-Bailie

Monday, 18 April 2016

Friday, 15 April 2016

Thursday, 14 April 2016

Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) ianbjacobs
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) ianbjacobs
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Dave Longley
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Manu Sporny
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Dave Longley

Wednesday, 13 April 2016

Tuesday, 12 April 2016

Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) ianbjacobs
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Ade Bateman
Re: [w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) Adrian Hope-Bailie
[w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) ianbjacobs
Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) Ade Bateman
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Ade Bateman

Monday, 11 April 2016

Sunday, 10 April 2016

Re: [w3c/browser-payment-api] Flows issue 32 (#131) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) dezell
Re: [w3c/browser-payment-api] [api] Change e.g. to e.g., (#66) rvm4
Re: [w3c/browser-payment-api] Change e.g. to e.g., (#126) rvm4
Re: [w3c/browser-payment-api] Specification of required fields (#114) mattsaxon
[w3c/browser-payment-api] codemod user agent to payment mediator in payment request (#137) rvm4
[w3c/browser-payment-api] provide partial shipping address in PaymentRequest and full shipping … (#136) rvm4
Re: [w3c/browser-payment-api] provide partial shipping address in PaymentRequest and full shipping … (#135) rvm4
Re: [w3c/browser-payment-api] provide partial shipping address in PaymentRequest and full shipping … (#135) rvm4
[w3c/browser-payment-api] provide partial shipping address in PaymentRequest and full shipping … (#135) rvm4
Re: [w3c/browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) rvm4
Re: [w3c/browser-payment-api] Specification of required fields (#114) Jeff Burdges
Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) Jeff Burdges
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Axel Nennker
[w3c/browser-payment-api] BasicCardResponse: cardholderName should be optional. (#134) Gregory Estrade
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Andrew Betts
Re: [w3c/browser-payment-api] Should the messages support field-level encryption? (#55) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the web page be able to provide status information before calling complete() (#5) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Use navigator.payments singleton, factory method, or PaymentRequest constructor (#16) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add reference to issue #45. (#79) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Flows issue 32 (#131) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Specification to include Flow Diagram (#32) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should API support billing address capture (for tax computation)? (#27) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the merchant be able to request your email and recipient phone number (#1) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Michael[tm] Smith
Re: [w3c/browser-payment-api] Constructor should not include "total" in list of items (#18) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Zen Smith
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Michael[tm] Smith
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should list of accepted payment methods be strings or objects? (#48) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
[w3c/browser-payment-api] Merged PaymentRequest params and tweaked to address some issues (#133) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Specification of required fields (#114) Adrian Hope-Bailie
[w3c/browser-payment-api] Should payment method specifications contain WebIDL? (#132) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] grammatical updates to the payment method identifier spec (#124) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Reference names should have hyphens (#125) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Change e.g. to e.g., (#126) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] fields in abort() Update paymentrequest.html (#130) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Wayne Carr

Saturday, 9 April 2016

Re: [w3c/browser-payment-api] Flows issue 32 (#131) mattsaxon
Re: [w3c/browser-payment-api] Flows issue 32 (#131) mattsaxon
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) Dave Longley
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) Michael[tm] Smith

Friday, 8 April 2016

Thursday, 7 April 2016

Wednesday, 6 April 2016

Tuesday, 5 April 2016

Re: [w3c/browser-payment-api] Add option 1b to payment method identifier spec. (#108) kirkalx
Re: [w3c/browser-payment-api] Proposal to add negative value support (#120) Ade Bateman
Re: [w3c/browser-payment-api] Proposal to add negative value support (#120) Ade Bateman
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Shane McCarron
Re: [w3c/browser-payment-api] Support for negative amounts (#119) kirkalx
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Shane McCarron
Re: [w3c/browser-payment-api] Support for negative amounts (#119) Michael[tm] Smith

Monday, 4 April 2016

Re: [w3c/browser-payment-api] Support for negative amounts (#119) kirkalx
Re: [w3c/browser-payment-api] API Data Integrity (#31) ianbjacobs
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Shane McCarron
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Shane McCarron
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Manu Sporny
Re: [w3c/browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Michael[tm] Smith
Re: [w3c/browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Consider revising the design of complete() (#122) Michael[tm] Smith
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Michael[tm] Smith
[w3c/browser-payment-api] Consider revising the design of complete() (#122) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Update Introduction to describe actors better (#121) Michael[tm] Smith
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) Adrian Hope-Bailie
[w3c/browser-payment-api] Update Introduction to describe actors better (#121) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Proposal to add negative value support (#120) Adrian Hope-Bailie
[w3c/browser-payment-api] Proposal to add negative value support (#120) Adrian Hope-Bailie
[w3c/browser-payment-api] Support for negative amounts (#119) Adrian Hope-Bailie

Sunday, 3 April 2016

[w3c/browser-payment-api] Review and respond to Andrew Betts’ TAG review of the spec (#118) Michael[tm] Smith
[w3c/browser-payment-api] Replace non-RFC-2219 “may”s in normative text (#117) Michael[tm] Smith
[w3c/browser-payment-api] De-duplicate markup for “user agents” def (#116) Michael[tm] Smith

Saturday, 2 April 2016

[w3c/browser-payment-api] Make other Payments-drafts refs be absolute URLs (#115) Michael[tm] Smith
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) mattsaxon
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) mattsaxon
[w3c/browser-payment-api] Gh pages (#114) mattsaxon
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) mattsaxon
Re: [w3c/browser-payment-api] Currency amount (#101) kirkalx
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Michael[tm] Smith
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Michael[tm] Smith
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Michael[tm] Smith
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Michael[tm] Smith
Re: [w3c/browser-payment-api] Currency amount (#101) Ade Bateman
Re: [w3c/browser-payment-api] Currency amount (#101) Dave Longley
Re: [w3c/browser-payment-api] Currency amount (#101) Dave Longley
Re: [w3c/browser-payment-api] Currency amount (#101) Ade Bateman
Re: [w3c/browser-payment-api] Currency amount (#101) Dave Longley
Re: [w3c/browser-payment-api] Currency amount (#101) Ade Bateman
Re: [w3c/browser-payment-api] Currency amount (#101) Dave Longley
Re: [w3c/browser-payment-api] Currency amount (#101) Ade Bateman
Re: [w3c/browser-payment-api] Currency amount (#101) Ade Bateman

Friday, 1 April 2016

Re: [w3c/browser-payment-api] Add reference to issue #45. (#79) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Currency amount (#101) Ade Bateman
Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Manu Sporny
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add option 1b to payment method identifier spec. (#108) Ade Bateman
Re: [w3c/browser-payment-api] Add option 1b to payment method identifier spec. (#108) Ade Bateman
Re: [w3c/browser-payment-api] Resubmitting because the document moved (#106) Ade Bateman
Re: [w3c/browser-payment-api] Resubmitting because the document moved (#106) Ade Bateman
Re: [w3c/browser-payment-api] Issue marker requesting security considerations section (#98) Ade Bateman
Re: [w3c/browser-payment-api] Issue marker requesting security considerations section (#98) Ade Bateman
Re: [w3c/browser-payment-api] Alternative issue marker for issue#38 (#96) Ade Bateman
Re: [w3c/browser-payment-api] Alternative issue marker for issue#38 (#96) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #55. (#87) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #55. (#87) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #51. (#85) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #51. (#85) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #50. (#84) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #50. (#84) Ade Bateman
Re: [w3c/browser-payment-api] Add reference to issue #48. (#82) Ade Bateman
Re: [w3c/browser-payment-api] Add reference to issue #48. (#82) Ade Bateman
Re: [w3c/browser-payment-api] Add reference to issue #47. (#81) Ade Bateman
Re: [w3c/browser-payment-api] Add reference to issue #47. (#81) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #39 (#77) Ade Bateman
Re: [w3c/browser-payment-api] Add a reference to issue #39 (#77) Ade Bateman
Re: [w3c/browser-payment-api] Some friendly editorial changes (#64) Ade Bateman
Re: [w3c/browser-payment-api] Some friendly editorial changes (#64) Ade Bateman
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) mattsaxon
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Rouslan Solomakhin
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) mattsaxon
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Shane McCarron
Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Shane McCarron
Re: [w3c/browser-payment-api] Currency amount (#101) Dave Longley
Re: [w3c/browser-payment-api] Currency amount (#101) Dave Longley
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Jeff Burdges
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) mattsaxon
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) mattsaxon
Re: [w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) mattsaxon
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Adrian Hope-Bailie
[w3c/browser-payment-api] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) mattsaxon
Re: [w3c/browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) mattsaxon
Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Jeff Burdges
Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) mattsaxon
[w3c/browser-payment-api] Should the list of transaction types be extensible? (#112) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) mattsaxon
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Jeff Burdges
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) mattsaxon
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a payment app identifier (URL) or a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) kirkalx
Re: [w3c/browser-payment-api] Currency amount (#101) kirkalx
Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) mattsaxon
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) David Illsley
Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should a payment app identifier (URL) or a payment method identifier (URL) resolve to a machine readable resource that describes it? (#46) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Adrian Hope-Bailie
Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Jason Normore

Last message date: Saturday, 30 April 2016 21:07:34 UTC