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

Thursday, 31 March 2016

• Re: [w3c/browser-payment-api] Currency amount (#101) kirkalx
• Re: [w3c/browser-payment-api] Currency amount (#101) kirkalx
• Re: [w3c/browser-payment-api] Currency amount (#101) Zach Koch
• Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Zach Koch
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Zach Koch
• Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Shane McCarron
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) mattsaxon
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Zach Koch
• Re: [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) mattsaxon
• 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) Zach Koch
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Zach Koch
• 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] complete() should take a string argument not boolean (#17) mattsaxon
• Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) mattsaxon
• 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) Zach Koch
• Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Jeff Burdges
• Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Shane McCarron
• Re: [w3c/browser-payment-api] Issue Prioritisation Explainer (#105) Dave Longley
• Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) ianbjacobs
• Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Manu Sporny
• Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Manu Sporny
• [w3c/browser-payment-api] Add PaymentItem type to deal with transaction types (#111) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) ianbjacobs
• [w3c/browser-payment-api] Migrate PaymentRequest text from arch to payment request spec. (#110) Manu Sporny
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) 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] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) Jeff Burdges
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Jeff Burdges
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) 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) Jeff Burdges
• Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) Jeff Burdges
• 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] complete() should take a string argument not boolean (#17) Adrian Hope-Bailie
• [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] 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] Add option 1b to payment method identifier spec. (#108) Adrian Hope-Bailie

Wednesday, 30 March 2016

• 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
• [w3c/browser-payment-api] Add option 1b to payment method identifier spec. (#108) Manu Sporny
• [w3c/browser-payment-api] add rvm4 as editor on the other 3 specs (#107) rvm4
• Re: [w3c/browser-payment-api] add rvm4 as editor on the other 3 specs (#107) rvm4
• Re: [w3c/browser-payment-api] complete() should take a string argument not boolean (#17) Jason Normore
• Re: [w3c/browser-payment-api] Should the payment request contain line item details? (#49) Manu Sporny
• Re: [w3c/browser-payment-api] Add a reference to issue #38 (#73) Manu Sporny
• Re: [w3c/browser-payment-api] Add a reference to issue #38 (#73) Manu Sporny
• Re: [w3c/browser-payment-api] Add a reference to issue #55. (#87) Manu Sporny
• Re: [w3c/browser-payment-api] Add a reference to issue #50. (#84) Manu Sporny
• Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) David Illsley
• Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Dave Longley
• 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] Currency amount (#101) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] What happens when currency of offer differs from currency of selected payment instrument? (#29) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Resubmitting because the document moved (#106) Shane McCarron
• [w3c/browser-payment-api] Resubmitting because the document moved (#106) Shane McCarron
• Re: [w3c/browser-payment-api] Issue Prioritisation Explainer (#105) fredMeignien
• Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) mattsaxon
• Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) mattsaxon

Tuesday, 29 March 2016

• Re: [w3c/browser-payment-api] Add a reference to issue #51. (#85) Manu Sporny
• Re: [w3c/browser-payment-api] Add reference to issue #48. (#82) Manu Sporny
• Re: [w3c/browser-payment-api] Add a reference to issue #39 (#77) Manu Sporny
• Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Zach Koch
• Re: [w3c/browser-payment-api] Add reference to issue #47. (#81) Manu Sporny
• Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) Rouslan Solomakhin
• Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) ianbjacobs
• Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) Zach Koch
• Re: [w3c/browser-payment-api] Add reference to issue #45. (#79) Manu Sporny
• Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) ianbjacobs
• Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) Zach Koch
• Re: [w3c/browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) ianbjacobs
• Re: [w3c/browser-payment-api] Payment Instrument clarification (#104) mattsaxon
• Re: [w3c/browser-payment-api] Payment Instrument clarification (#104) ianbjacobs
• Re: [w3c/browser-payment-api] Currency amount (#101) mattsaxon
• Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) ianbjacobs
• [w3c/browser-payment-api] Issue Prioritisation Explainer (#105) mattsaxon
• Re: [w3c/browser-payment-api] mark rvm4 as a new editor of the spec (#102) rvm4
• [w3c/browser-payment-api] Payment Instrument clarification (#104) mattsaxon
• [w3c/browser-payment-api] What component does the payment method intersection? (#103) mattsaxon
• Re: [w3c/browser-payment-api] Rvm4 editor (#99) rvm4
• Re: [w3c/browser-payment-api] Rvm4 editor (#99) rvm4
• [w3c/browser-payment-api] mark rvm4 as a new editor of the spec (#102) rvm4
• Re: [w3c/browser-payment-api] Card Sub-Brands (#95) ianbjacobs
• Re: [w3c/browser-payment-api] Currency amount (#101) Shane McCarron
• 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) ianbjacobs
• 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] Currency amount (#101) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie
• Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Manu Sporny
• Re: [w3c/browser-payment-api] Currency amount (#101) Shane McCarron
• [w3c/browser-payment-api] Currency amount (#101) Adrian Hope-Bailie
• [w3c/browser-payment-api] Basic Card Payment Spec will become a Note not a Rec (#100) ianbjacobs
• Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) mattsaxon
• Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) mattsaxon
• Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) ianbjacobs
• Re: [w3c/browser-payment-api] Add a reference to issue #38 (#73) mattsaxon
• Re: [w3c/browser-payment-api] How are payment apps shared between different browser brands? (#38) 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) ianbjacobs
• 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) Matt Saxon
• Re: [w3c/browser-payment-api] Card Sub-Brands (#95) Matt Saxon
• Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Matt Saxon

Monday, 28 March 2016

• [browser-payment-api] Rvm4 editor (#99) rvm4

Sunday, 27 March 2016

• [browser-payment-api] Issue marker requesting security considerations section (#98) Adrian Hope-Bailie
• Re: [browser-payment-api] Add a reference to issue #39 (#77) Adrian Hope-Bailie
• Re: [browser-payment-api] Add a reference to issue #50. (#84) Adrian Hope-Bailie
• Re: [browser-payment-api] Add a reference to issue #51. (#85) Adrian Hope-Bailie
• Re: [browser-payment-api] Add reference to issue #48. (#82) Adrian Hope-Bailie
• Re: [browser-payment-api] Add reference to issue #47. (#81) Adrian Hope-Bailie
• Re: [browser-payment-api] Add reference to issue #45. (#79) Adrian Hope-Bailie
• Re: [browser-payment-api] Some friendly editorial changes (#64) Adrian Hope-Bailie
• Re: [browser-payment-api] How are web-based payment apps supported? (#39) Adrian Hope-Bailie
• Re: [browser-payment-api] How are web-based payment apps supported? (#39) Adrian Hope-Bailie
• Re: [browser-payment-api] Add a reference to issue #55. (#87) Adrian Hope-Bailie
• Re: [browser-payment-api] Add a reference to issue #38 (#73) Adrian Hope-Bailie

Friday, 25 March 2016

• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren

Thursday, 24 March 2016

• Re: [browser-payment-api] Change the way we request user data (#65) Zach Koch
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Dave Longley
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Shane McCarron
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Ade Bateman
• Re: [browser-payment-api] Should the payment request contain line item details? (#49) Ade Bateman
• Re: [browser-payment-api] Should the payment request contain line item details? (#49) Shane McCarron
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Shane McCarron
• Re: [browser-payment-api] Change the way we request user data (#65) Jeff Burdges
• Re: [browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
• Re: [browser-payment-api] Add reference to issue #49. (#83) Adrian Hope-Bailie
• Re: [browser-payment-api] Some friendly editorial changes (#64) Shane McCarron
• Re: [browser-payment-api] Some friendly editorial changes (#64) Adrian Hope-Bailie
• Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) David Illsley
• Re: [browser-payment-api] Should the payment request contain line item details? (#49) Ade Bateman
• Re: [browser-payment-api] Add issue #43 to payment request spec. (#61) Ade Bateman
• Re: [browser-payment-api] Add issue #43 to payment request spec. (#61) Ade Bateman
• Re: [browser-payment-api] Add reference to issue #44. (#78) Ade Bateman
• Re: [browser-payment-api] Add reference to issue #44. (#78) Ade Bateman
• Re: [browser-payment-api] Add a reference to issue #40. (#72) Ade Bateman
• Re: [browser-payment-api] Add a reference to issue #40. (#72) Ade Bateman
• Re: [browser-payment-api] Card Sub-Brands (#95) Ade Bateman
• Re: [browser-payment-api] Card Sub-Brands (#95) Ade Bateman
• Re: [browser-payment-api] Add a reference to issue #53. (#86) Ade Bateman
• Re: [browser-payment-api] Add a reference to issue #53. (#86) Ade Bateman
• Re: [browser-payment-api] Remove note and add description for diagram (#74) Ade Bateman
• Re: [browser-payment-api] Remove note and add description for diagram (#74) Ade Bateman
• Re: [browser-payment-api] Make activation language more permissive (#70) Ade Bateman
• Re: [browser-payment-api] Make activation language more permissive (#70) Ade Bateman
• Re: [browser-payment-api] Document titles were wrong (#69) Ade Bateman
• Re: [browser-payment-api] Document titles were wrong (#69) Ade Bateman

Wednesday, 23 March 2016

• Re: [browser-payment-api] Wrong document names and British English (#93) Ade Bateman
• Re: [browser-payment-api] Wrong document names and British English (#93) Ade Bateman
• Re: [browser-payment-api] User Agent should not be hyphenated (#68) Ade Bateman
• Re: [browser-payment-api] User Agent should not be hyphenated (#68) Ade Bateman
• Re: [browser-payment-api] Remove duplicate conformance language (#67) Ade Bateman
• Re: [browser-payment-api] Remove duplicate conformance language (#67) Ade Bateman
• Re: [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: [browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Rouslan Solomakhin
• Re: [browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Rouslan Solomakhin
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin
• Re: [browser-payment-api] Added respec defines to improve github links (#57) Ade Bateman
• Re: [browser-payment-api] Added respec defines to improve github links (#57) Ade Bateman
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Rouslan Solomakhin
• Re: [browser-payment-api] Card Sub-Brands (#95) Rouslan Solomakhin
• Re: [browser-payment-api] Specifying Mandatory Data (#97) mattsaxon
• Re: [browser-payment-api] Card Sub-Brands (#95) mattsaxon
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) mattsaxon
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Dave Longley
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Adrian Hope-Bailie
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Nick S
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Dave Longley
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Dave Longley
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Rouslan Solomakhin
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) Rouslan Solomakhin
• Re: [browser-payment-api] Card Sub-Brands (#95) Rouslan Solomakhin
• Re: [browser-payment-api] Specifying Mandatory Data (#97) Adrian Hope-Bailie
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Dave Longley
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) mattsaxon
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) David Illsley

Monday, 21 March 2016

• Re: [browser-payment-api] Should we define nesting/grouping semantics for payment method identifier matching? (#30) mattsaxon
• [browser-payment-api] Specifying Mandatory Data (#97) mattsaxon
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Anders Rundgren
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Adrian Hope-Bailie

Sunday, 20 March 2016

• [browser-payment-api] Alternative issue marker for issue#38 (#96) Nick Telford-Reed
• Re: [browser-payment-api] Add a reference to issue #38 (#73) Nick Telford-Reed
• Re: [browser-payment-api] Add a reference to issue #40. (#72) Nick Telford-Reed
• Re: [browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) mattsaxon
• [browser-payment-api] Gh pages (#95) mattsaxon
• Re: [browser-payment-api] Should the API support field-level encryption? (#55) mattsaxon
• Re: [browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) mattsaxon
• Re: [browser-payment-api] Change the way we request user data (#65) mattsaxon

Saturday, 19 March 2016

• Re: [browser-payment-api] Write-up proposal for shipping address fields (#6) Adrian Hope-Bailie

Friday, 18 March 2016

• Re: [browser-payment-api] Some friendly editorial changes (#64) Manu Sporny
• Re: [browser-payment-api] Add a reference to issue #40. (#72) Manu Sporny
• Re: [browser-payment-api] Add a reference to issue #38 (#73) Adrian Hope-Bailie
• Re: [browser-payment-api] Some friendly editorial changes (#64) Shane McCarron
• Re: [browser-payment-api] Add a reference to issue #40. (#72) Adrian Hope-Bailie
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Adrian Hope-Bailie
• Re: [browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) ianbjacobs
• Re: [browser-payment-api] Add a reference to issue #40. (#72) Adrian Hope-Bailie

Thursday, 17 March 2016

• Re: [browser-payment-api] Make activation language more permissive (#70) Adrian Hope-Bailie
• Re: [browser-payment-api] Document titles were wrong (#69) Adrian Hope-Bailie
• Re: [browser-payment-api] User Agent should not be hyphenated (#68) Adrian Hope-Bailie
• Re: [browser-payment-api] Some friendly editorial changes (#64) Adrian Hope-Bailie
• Re: [browser-payment-api] Some friendly editorial changes (#64) Adrian Hope-Bailie
• Re: [browser-payment-api] Add issue #43 to payment request spec. (#61) Adrian Hope-Bailie
• Re: [browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) Adrian Hope-Bailie
• Re: [browser-payment-api] Added respec defines to improve github links (#57) Adrian Hope-Bailie
• Re: [browser-payment-api] Change the way we request user data (#65) Adrian Hope-Bailie
• Re: [browser-payment-api] Add reference to issue #56. (#89) Zach Koch
• Re: [browser-payment-api] Add a reference to issue #39 (#77) Zach Koch
• Re: [browser-payment-api] "Shown" is not inclusive enough (#71) Zach Koch
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Shane McCarron
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Håvard Molland
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Shane McCarron
• Re: [browser-payment-api] Add a reference to issue #38 (#73) Manu Sporny
• Re: [browser-payment-api] Add a reference to issue #38 (#73) Zach Koch
• Re: [browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) Manu Sporny
• Re: [browser-payment-api] Removed references to "browser" (#92) Zach Koch
• Re: [browser-payment-api] [architecture] Use "user agent", not "browser" (#59) Zach Koch
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Dave Longley
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Manu Sporny
• Re: [browser-payment-api] Add reference to issue #46. (#80) ianbjacobs
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Dave Longley
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Manu Sporny
• Re: [browser-payment-api] Add reference to issue #46. (#80) Manu Sporny
• Re: [browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) ianbjacobs
• Re: [browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) Manu Sporny
• Re: [browser-payment-api] Add section on Extensibility (#44) Manu Sporny
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Wendy Seltzer
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Shane McCarron
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Dave Longley
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Dave Longley
• Re: [browser-payment-api] Add section on Extensibility (#44) Shane McCarron
• Re: [browser-payment-api] Added respec defines to improve github links (#57) Shane McCarron
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Shane McCarron
• [browser-payment-api] [basic] Reference trademarks (#94) Shane McCarron
• [browser-payment-api] Wrong document names and British English (#93) Shane McCarron
• [browser-payment-api] Removed references to "browser" (#92) Ade Bateman
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Håvard Molland
• Re: [browser-payment-api] Add reference to issue #46. (#80) Ade Bateman
• Re: [browser-payment-api] Add reference to issue #46. (#80) Ade Bateman
• Re: [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Ade Bateman
• Re: [browser-payment-api] Add reference to issue #46. (#80) Ade Bateman
• Re: [browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) Ade Bateman
• Re: [browser-payment-api] Add section on Extensibility (#44) Ade Bateman
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Ade Bateman
• Re: [browser-payment-api] Add UnionPay, Correct typo on Diners (#91) Ade Bateman
• Re: [browser-payment-api] Add UnionPay, Correct typo on Diners (#91) Ade Bateman
• [browser-payment-api] Add UnionPay, Correct typo on Diners (#91) mattsaxon
• Re: [browser-payment-api] Gh pages (#90) mattsaxon
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• Re: [browser-payment-api] Remove trailing whitespace. (#60) Zach Koch
• Re: [browser-payment-api] Fix typo (#76) Zach Koch
• Re: [browser-payment-api] Some friendly editorial changes (#64) Zach Koch
• Re: [browser-payment-api] Some friendly editorial changes (#64) Zach Koch
• Re: [browser-payment-api] Added respec defines to improve github links (#57) Zach Koch
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Zach Koch
• Re: [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Rouslan Solomakhin

Wednesday, 16 March 2016

• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny
• Re: [browser-payment-api] Gh pages (#90) Zach Koch
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Zach Koch
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• [browser-payment-api] Gh pages (#90) mattsaxon
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• [browser-payment-api] Add reference to issue #56. (#89) Manu Sporny
• [browser-payment-api] Add a reference to issue #56. (#88) Manu Sporny
• Re: [browser-payment-api] Add a reference to issue #56. (#88) Manu Sporny
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• [browser-payment-api] Add a reference to issue #55. (#87) Manu Sporny
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley
• [browser-payment-api] Add a reference to issue #53. (#86) Manu Sporny
• [browser-payment-api] Add a reference to issue #51. (#85) Manu Sporny
• [browser-payment-api] Add a reference to issue #50. (#84) Manu Sporny
• [browser-payment-api] Add reference to issue #49. (#83) Manu Sporny
• [browser-payment-api] Add reference to issue #48. (#82) Manu Sporny
• [browser-payment-api] Add reference to issue #47. (#81) Manu Sporny
• [browser-payment-api] Add reference to issue #46. (#80) Manu Sporny
• [browser-payment-api] Add reference to issue #45. (#79) Manu Sporny
• [browser-payment-api] Add reference to issue #44. (#78) Manu Sporny
• [browser-payment-api] Add a reference to issue #39 (#77) Manu Sporny
• [browser-payment-api] Fix typo (#76) Shane McCarron
• [browser-payment-api] [api] Section 11 PaymentResponse seems to be missing shippingAddress (#75) Shane McCarron
• [browser-payment-api] Remove note and add description for diagram (#74) Shane McCarron
• [browser-payment-api] Add a reference to issue #38 (#73) Manu Sporny
• [browser-payment-api] Add a reference to issue #40. (#72) Manu Sporny
• [browser-payment-api] "Shown" is not inclusive enough (#71) Shane McCarron
• [browser-payment-api] Make activation language more permissive (#70) Shane McCarron
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Shane McCarron
• [browser-payment-api] Document titles were wrong (#69) Shane McCarron
• [browser-payment-api] User Agent should not be hyphenated (#68) Shane McCarron
• [browser-payment-api] Remove duplicate conformance language (#67) Shane McCarron
• [browser-payment-api] [api] Change e.g. to e.g., (#66) Shane McCarron

Tuesday, 15 March 2016

• Re: [browser-payment-api] Change the way we request user data (#65) ianbjacobs
• Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny
• Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny
• Re: [browser-payment-api] Change the way we request user data (#65) Zach Koch
• Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny
• Re: [browser-payment-api] Change the way we request user data (#65) Manu Sporny
• [browser-payment-api] Change the way we request user data (#65) Zach Koch
• Re: [browser-payment-api] Minor mod to paymentrequest.html (#62) Zach Koch
• [browser-payment-api] Some friendly editorial changes (#64) Shane McCarron
• [browser-payment-api] [architecture] Reference names should have hyphens (#63) Shane McCarron
• Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Nick Telford-Reed
• Re: [browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) Nick Telford-Reed
• [browser-payment-api] Minor mod to paymentrequest.html (#62) Nick Telford-Reed

Monday, 14 March 2016

• Re: [browser-payment-api] Should the API support field-level encryption? (#55) ianbjacobs
• [browser-payment-api] Add issue #43 to payment request spec. (#61) Manu Sporny
• [browser-payment-api] Remove trailing whitespace. (#60) Manu Sporny
• Re: [browser-payment-api] [architecture] Use "user agent", not "browser" (#59) Manu Sporny
• Re: [browser-payment-api] Should the API support field-level encryption? (#55) Jeff Burdges
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny
• Re: [browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) Manu Sporny
• Re: [browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) mwatson2
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Dave Longley
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs
• Re: [browser-payment-api] Should the payment request support multiple pricing options? (#54) Manu Sporny
• Re: [browser-payment-api] Should the payment request support multiple pricing options? (#54) Manu Sporny
• Re: [browser-payment-api] [architecture] Use "user agent", not "browser" (#59) Shane McCarron
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• Re: [browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) Manu Sporny
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny
• Re: [browser-payment-api] [architecture] Use "user agent", not "browser" (#59) Manu Sporny
• Re: [browser-payment-api] Should the payment request support multiple pricing options? (#54) ianbjacobs
• Re: [browser-payment-api] How does the API support enrollment (aka subscription, future payment) use cases? (#52) ianbjacobs
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs
• Re: [browser-payment-api] How does the API support enrollment (aka subscription, future payment) use cases? (#52) ianbjacobs
• Re: [browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) ianbjacobs
• Re: [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) ianbjacobs
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) ianbjacobs
• [browser-payment-api] [architecture] Use "user agent", not "browser" (#59) Shane McCarron
• Re: [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Shane McCarron
• Re: [browser-payment-api] How are payment apps shared between different browser brands? (#38) ianbjacobs
• [browser-payment-api] [architecture] SotD should indicate it is intended to be a Note (#58) Shane McCarron
• Re: [browser-payment-api] Write-up initial proposal for payment app registration spec (#12) ianbjacobs
• [browser-payment-api] Added respec defines to improve github links (#57) Shane McCarron
• Re: [browser-payment-api] Should the payment request support multiple pricing options? (#54) Adrian Hope-Bailie
• Re: [browser-payment-api] Should the API support field-level encryption? (#55) Adrian Hope-Bailie
• Re: [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: [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
• [browser-payment-api] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#56) Manu Sporny
• [browser-payment-api] Should the API support field-level encryption? (#55) Manu Sporny
• [browser-payment-api] Should the payment request support multiple pricing options? (#54) Manu Sporny
• [browser-payment-api] Add section on internationalization (#53) Manu Sporny
• [browser-payment-api] How does the API support enrollment (aka subscription, future payment) use cases? (#52) Manu Sporny
• [browser-payment-api] Should the payment API be more conversational vs. rigid? (#51) Manu Sporny
• [browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) Manu Sporny
• [browser-payment-api] Should the payment request contain line item details? (#49) Manu Sporny
• [browser-payment-api] Should list of accepted payment methods be strings or objects? (#48) Manu Sporny
• [browser-payment-api] Should a payment request be just data, or a programmable object? (#47) Manu Sporny
• [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) Manu Sporny
• [browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) Manu Sporny
• [browser-payment-api] Add section on Extensibility (#44) Manu Sporny
• Re: [browser-payment-api] Write-up initial proposal for payment app registration spec (#12) Manu Sporny
• Re: [browser-payment-api] What is the format for payment method identifiers for distributed extensibility (#11) Manu Sporny
• Re: [browser-payment-api] How do we ensure that the payment request from the merchant is not tampered with before it gets to the payment app? (#41) Manu Sporny
• Re: [browser-payment-api] How do we ensure that the payment request from the merchant is not tampered with before it gets to the payment app? (#41) Manu Sporny
• [browser-payment-api] Terminology across all Web Payments documents should be aligned (#43) Manu Sporny
• [browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) Manu Sporny
• Re: [browser-payment-api] Spec should use [SecureContext] once that is defined in Web IDL (#22) Manu Sporny
• [browser-payment-api] How do we ensure that the payment request from the merchant is not tampered with before it gets to the payment app? (#41) Manu Sporny
• Re: [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny
• [browser-payment-api] How do organizations layer additional information in the core payment messages? (#40) Manu Sporny
• [browser-payment-api] How are web-based payment apps supported? (#39) Manu Sporny
• [browser-payment-api] How are payment apps shared between different browser brands? (#38) Manu Sporny
• Re: [browser-payment-api] Write-up initial proposal for payment app registration spec (#12) Manu Sporny

Sunday, 13 March 2016

• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Zach Koch
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Nick S
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) dezell
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) dezell
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman

Saturday, 12 March 2016

• Re: [browser-payment-api] API Data Integrity (#31) Anders Rundgren
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Nick S
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Ade Bateman
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Ade Bateman
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Nick S

Friday, 11 March 2016

• Re: [browser-payment-api] Write-up proposal for shipping address fields (#6) Ade Bateman
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Dave Longley
• Re: [browser-payment-api] Editorial and some clarifications (#37) Ade Bateman
• Re: [browser-payment-api] Editorial and some clarifications (#37) Ade Bateman
• Re: [browser-payment-api] Gh pages (#36) Ade Bateman
• Re: [browser-payment-api] Gh pages (#36) Ade Bateman
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Zach Koch
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Dave Longley
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) Dave Longley
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Jeff Burdges
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) ianbjacobs
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Suggest two alternative payment method identifier proposals (#34) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) Adrian Hope-Bailie
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• [browser-payment-api] Editorial and some clarifications (#37) Adrian Hope-Bailie
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Redefinition of BasicCardResponse to address Issue 9 (#25) mattsaxon
• Re: [browser-payment-api] Different card schemes have different mandatory field requirements (#9) mattsaxon
• Re: [browser-payment-api] API Data Integrity (#31) mattsaxon
• Re: [browser-payment-api] Should the API handle pre-auth, recurring payments, and similar scenarios (#19) mattsaxon
• Re: [browser-payment-api] Write-up proposal for shipping address fields (#6) Adrian Hope-Bailie

Thursday, 10 March 2016

• [browser-payment-api] Gh pages (#36) ianbjacobs
• Re: [browser-payment-api] Write-up proposal for shipping address fields (#6) Rouslan Solomakhin
• Re: [browser-payment-api] Write-up proposal for shipping address fields (#6) Ade Bateman
• Re: [browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) Dave Longley
• Re: [browser-payment-api] Write-up proposal for shipping address fields (#6) Rouslan Solomakhin
• Test new list Ian Jacobs

Last message date: Thursday, 31 March 2016 23:55:19 UTC