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

Monday, 29 February 2016

Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Zach Koch
Re: [Minutes] 23-24 February face-to-face meeting Doug Schepers
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Shane McCarron
Re: [paymentrequest] At the time complete() is called, your ability to say success (true) or failure (false) may depend on the payment method (#67) Rouslan Solomakhin
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Rouslan Solomakhin
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Rouslan Solomakhin
Under W3C Member Review: Hardware Security Working Group Charter (until 1 April) Ian Jacobs
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Jeff Burdges
JSON signatures for "node.js" Anders Rundgren

Friday, 26 February 2016

Thursday, 25 February 2016

Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) mattsaxon
[Minutes] 23-24 February face-to-face meeting Ian Jacobs
Re: [webpayments] Gh pages (#108) mattsaxon
[webpayments] Gh pages (#108) mattsaxon
[webpayments] Gh pages (#107) mattsaxon
Re: [webpayments] Gh pages (#107) mattsaxon
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Shane McCarron
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Shane McCarron
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Dave Longley
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) dezell
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley

Wednesday, 24 February 2016

Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Laurent Castillo
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Mountie Lee
Re: [paymentrequest] Constructor should not include "total" in list of items (#68) Zach Koch
[paymentrequest] Constructor should not include "total" in list of items (#68) Shane McCarron
[paymentrequest] At the time complete() is called, your ability to say success (true) or failure (false) may depend on the payment method (#67) Ade Bateman
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley
RE: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Joerg.Heuer@telekom.de
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Laurent Castillo
Re: [webpayments] Repo my apps (#103) Adrian Hope-Bailie
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Jeff Burdges
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Zach Koch
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley
Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Adrian Hope-Bailie
Re: [webpayments] Taler flows (#106) Jeff Burdges

Tuesday, 23 February 2016

[paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Laurent Castillo
Re: [webpayments] Taler flows (#106) Jeff Burdges
[webpayments] Taler flows (#106) Jeff Burdges
Draft of PaymentRequest Registration Doc Available Zach Koch
Re: [webpayments] Gh pages (#105) mattsaxon
[webpayments] Gh pages (#105) mattsaxon
Re: [paymentrequest] Write-up initial proposal for payment app registration spec (#27) Ade Bateman
Re: [paymentrequest] Write-up initial proposal for payment app registration spec (#27) Ade Bateman
Re: [paymentrequest] Write-up initial proposal for card payment method spec (#31) Ade Bateman
Re: [paymentrequest] Write-up initial proposal for card payment method spec (#31) Ade Bateman
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Rouslan Solomakhin
Re: [paymentrequest] Add link to registration explainer to index page. (#65) Ade Bateman
[paymentrequest] Add link to registration explainer to index page. (#65) Ade Bateman
Re: [paymentrequest] Add registration explainer (#64) Ade Bateman
Re: [paymentrequest] Add registration explainer (#64) Ade Bateman
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Nick S
[paymentrequest] Add registration explainer (#64) Zach Koch
Re: [paymentrequest] Error types used are weird and excessive (#56) Ade Bateman
Re: [paymentrequest] Error types used are weird and excessive (#56) Ade Bateman
Re: [paymentrequest] Algorithm for complete(success) does not use its argument (#55) Ade Bateman
Re: [paymentrequest] Algorithm for complete(success) does not use its argument (#55) Ade Bateman
Re: [paymentrequest] "JSON object" is confusing; consider "JSON-serializable object" (#59) Ade Bateman
Re: [paymentrequest] "JSON object" is confusing; consider "JSON-serializable object" (#59) Ade Bateman
Re: [paymentrequest] Don't have a <dfn> for "user agent" (#60) Ade Bateman
Re: [paymentrequest] Don't have a <dfn> for "user agent" (#60) Ade Bateman
Re: [paymentrequest] State in each class's definition which internal slots it has (#61) Zach Koch
Re: [paymentrequest] Example 1 typo: payment.complete(true) should be paymentResponse.complete(true) (#53) Zach Koch
Re: [paymentrequest] Add skeleton of basic card spec and tidy-up API spec (#63) Zach Koch

Monday, 22 February 2016

[paymentrequest] Add skeleton of basic card spec and tidy-up API spec (#63) Ade Bateman
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Rouslan Solomakhin
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Dave Longley
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Rouslan Solomakhin
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Dave Longley
Re: [paymentrequest] Write-up proposal for shipping address fields (#28) Rouslan Solomakhin
Re: [paymentrequest] Example 1 typo: payment.complete(true) should be paymentResponse.complete(true) (#53) Rouslan Solomakhin
[webpayments] Minor Changes (#104) mattsaxon
Re: [webpayments] Minor Changes (#104) mattsaxon

Saturday, 20 February 2016

Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Gregory Estrade

Monday, 22 February 2016

Sunday, 21 February 2016

RE: Dinner at Croqueta on Sunday at 7pm in San Francisco Katie Haritos-Shea
RE: Dinner at Croqueta on Sunday at 7pm in San Francisco Joerg.Heuer@telekom.de
RE: Dinner at Croqueta on Sunday at 7pm in San Francisco Joerg.Heuer@telekom.de
JSON Signatures for Financial Messaging Anders Rundgren
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Doug Schepers
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Adrian Hope-Bailie
[webpayments] Repo my apps (#103) Daniel Torres
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Nick S
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny
Re: CHANGE OF VENUE: Sunday dinner now at La Mar Cebichería Peruana at 7:30pm Katie Haritos-Shea

Saturday, 20 February 2016

CHANGE OF VENUE: Sunday dinner now at La Mar Cebichería Peruana at 7:30pm Manu Sporny
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Katie Haritos-Shea
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Paddy Ramanathan
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Shane McCarron
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Ian Jacobs
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Adrian Hope-Bailie
Re: Dinner at Croqueta on Sunday at 7pm in San Francisco Mountie Lee
Dinner at Croqueta on Sunday at 7pm in San Francisco Manu Sporny

Friday, 19 February 2016

New PaymentRequest Doc Zach Koch
Re: [paymentrequest] Add rationale and update document locations (#62) Manu Sporny
Re: [paymentrequest] Add rationale and update document locations (#62) ianbjacobs
Re: [paymentrequest] Add rationale and update document locations (#62) Ade Bateman
Re: [paymentrequest] Add rationale and update document locations (#62) Ade Bateman
Re: [paymentrequest] Add rationale and update document locations (#62) Zach Koch
Re: [paymentrequest] Add rationale and update document locations (#62) Ade Bateman
Re: [paymentrequest] Add rationale and update document locations (#62) Zach Koch
Re: [paymentrequest] Add rationale and update document locations (#62) Zach Koch
[paymentrequest] Add rationale and update document locations (#62) Zach Koch
Re: [webpayments] Removed Spaces From File Name (#102) mattsaxon
[webpayments] Removed Spaces From File Name (#102) mattsaxon
Re: [webpayments] Gh pages (#101) mattsaxon
[webpayments] Gh pages (#101) mattsaxon
RE: The Open Banking Standard (HTTP API) Telford-Reed, Nick
Re: [webpayments] How are third-party native wallets integrated? (#42) Håvard Molland
Re: Draft requirements for discussion at the WPWG FTF meeting Ian Jacobs
Re: Draft requirements for discussion at the WPWG FTF meeting Manu Sporny
Draft requirements for discussion at the WPWG FTF meeting Ian Jacobs

Thursday, 18 February 2016

[paymentrequest] State in each class's definition which internal slots it has (#61) Domenic Denicola
[paymentrequest] Don't have a <dfn> for "user agent" (#60) Domenic Denicola
[paymentrequest] "JSON object" is confusing; consider "JSON-serializable object" (#59) Domenic Denicola
[paymentrequest] Use [SecureContext] instead of manually checking inside the PaymentRequest constructor (#58) Domenic Denicola
[paymentrequest] Spec references are all pretty outdated (#57) Domenic Denicola
[paymentrequest] Error types used are weird and excessive (#56) Domenic Denicola
[paymentrequest] Algorithm for complete(success) does not use its argument (#55) Domenic Denicola
[paymentrequest] boolean arguments are an anti-pattern; consider separate methods for complete() (#54) Domenic Denicola
[paymentrequest] Example 1 typo: payment.complete(true) should be paymentResponse.complete(true) (#53) Domenic Denicola
Re: Face to face - some important reading Zach Koch
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Nick Telford-Reed
Face to face - some important reading Telford-Reed, Nick
[Minutes] 18 Feb WPWG call Ian Jacobs
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Nick S
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Rouslan Solomakhin
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley
Re: [webpayments] How are third-party native wallets integrated? (#42) Rouslan Solomakhin
Re: [webpayments] How do we prevent keyboard hooking during payment? (#90) Rouslan Solomakhin
Re: The Open Banking Standard (HTTP API) Ian Jacobs
Re: The Open Banking Standard (HTTP API) Ian Jacobs
Meeting today Telford-Reed, Nick
Re: The Open Banking Standard (HTTP API) Adrian Hope-Bailie
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Zach Koch
Re: The Open Banking Standard (HTTP API) Frédéric Meignien
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny
Re: The Open Banking Standard (HTTP API) Frédéric Meignien
The Open Banking Standard (HTTP API) Manu Sporny
Re: [webpayments] How are third-party native wallets integrated? (#42) Håvard Molland
Re: [webpayments] Review: UPI - a method and standard that went BETA in India (#100) Madhu
Re: [webpayments] Review: UPI - a method and standard that went BETA in India (#100) ianbjacobs
[webpayments] Review: UPI - a method and standard that went BETA in India (#100) Madhu
Re: [webpayments] How do we prevent keyboard hooking during payment? (#90) ianbjacobs
Re: [webpayments] How are third-party native wallets integrated? (#42) Rouslan Solomakhin
Re: [webpayments] Multilingual Support for human-readable labels (#84) ianbjacobs
Re: [webpayments] Multilingual Support for human-readable labels (#84) Rouslan Solomakhin
Re: [webpayments] Transition and Adoption (#94) Rouslan Solomakhin
Re: [webpayments] How do we prevent keyboard hooking during payment? (#90) Rouslan Solomakhin
Re: [webpayments] Transition and Adoption (#94) Dave Longley
Re: [webpayments] Transition and Adoption (#94) Rouslan Solomakhin
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Rouslan Solomakhin
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Rouslan Solomakhin

Wednesday, 17 February 2016

Re: [webpayments] PISP under PSD2_SCT flows_Shopper PISP (#99) mattsaxon
[webpayments] PISP under PSD2_SCT flows_Shopper PISP (#99) fredMeignien
Re: [webpayments] Added Credit Transfer clarifications (#98) mattsaxon
Re: [webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) mattsaxon
[webpayments] Added Credit Transfer clarifications (#98) mattsaxon
Re: [webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) Erik Anderson
Re: [webpayments] PISP under PSD2_SCT flows_Merchant PISP.pml (#97) mattsaxon
[webpayments] PISP under PSD2_SCT flows_Merchant PISP.pml (#97) fredMeignien
Re: [webpayments] Minor fixes/annoatations (#96) mattsaxon
[webpayments] Minor fixes/annoatations (#96) mattsaxon
Re: [webpayments] ISO20022 terminology adoption (#93) mattsaxon
Re: [webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) mattsaxon
Re: [webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) fredMeignien
Re: [webpayments] ISO20022 terminology adoption (#93) Erik Anderson
Re: [webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) Erik Anderson
[webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95) Erik Anderson
Re: Sanity check on API using flows from Flows Task Force Frédéric Meignien
Re: [webpayments] ISO20022 terminology adoption (#93) fredMeignien
RE: Sanity check on API using flows from Flows Task Force Matt Saxon
Re: Sanity check on API using flows from Flows Task Force Frédéric Meignien
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) mattsaxon
RE: Sanity check on API using flows from Flows Task Force Matt Saxon
Re: [webpayments] ISO20022 terminology adoption (#93) mattsaxon
Re: Sanity check on API using flows from Flows Task Force Frédéric Meignien
Re: [webpayments] ISO20022 terminology adoption (#93) fredMeignien
Re: Sanity check on API using flows from Flows Task Force Adrian Hope-Bailie
Re: [webpayments] Flow terminology (#92) mattsaxon
Re: [webpayments] Flow terminology (#92) mattsaxon
Re: [webpayments] ISO20022 terminology adoption (#93) mattsaxon
Re: [webpayments] ISO20022 terminology adoption (#93) mattsaxon
Re: [webpayments] ISO20022 terminology adoption (#93) mattsaxon
[webpayments] Transition and Adoption (#94) mattsaxon
[webpayments] ISO20022 terminology adoption (#93) mattsaxon
[webpayments] Flow terminology (#92) mattsaxon

Tuesday, 16 February 2016

Re: Sanity check on API using flows from Flows Task Force Shane McCarron
RE: Sanity check on API using flows from Flows Task Force Matt Saxon
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Jake Archibald
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman
Re: [webpayments] Security and Privacy Self-Review (#61) ianbjacobs
Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Adrian Hope-Bailie
Re: [webpayments] Fix typos (#91) Adrian Hope-Bailie
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie
Re: [webpayments] How do we prevent keyboard hooking during payment? (#90) oldoldb
Re: [webpayments] How do we prevent keyboard hooking during payment? (#90) ianbjacobs
Re: [webpayments] How do we prevent keyboard hooking during payment? (#90) oldoldb

Monday, 15 February 2016

Sunday, 14 February 2016

Re: ACTION STRONGLY ENCOURAGED: Flows ready for wider review Matt Saxon
Re: ACTION STRONGLY ENCOURAGED: Flows ready for wider review Manu Sporny
Re: Sanity check on API using flows from Flows Task Force Manu Sporny
RE: Sanity check on API using flows from Flows Task Force Matt Saxon
Re: [webpayments] Consolidate updated from Freed into single file (#88) mattsaxon
[webpayments] Consolidate updated from Freed into single file (#88) mattsaxon
[webpayments] Consolidate updated from Freed into single file (#87) mattsaxon
Re: [webpayments] Consolidate updated from Freed into single file (#87) mattsaxon
RE: ACTION STRONGLY ENCOURAGED: Flows ready for wider review Matt Saxon
Re: [webpayments] Returned Skin to default, moved target flows out of directory structure, removed partial flows for SEPA Credit Transfer (#80) mattsaxon
Re: [webpayments] Consolidate updated from Freed into single file (#86) mattsaxon
[webpayments] Consolidate updated from Freed into single file (#86) mattsaxon
Re: [webpayments] Changes based on discussion with Ian Jacobs (#85) mattsaxon
[webpayments] Changes based on discussion with Ian Jacobs (#85) mattsaxon
Re: [webpayments] PSD2 about Payment Initiation 4 Feb 2016 (#82) mattsaxon

Saturday, 13 February 2016

Re: [paymentrequest] Tidy-up per discussion (#52) Zach Koch
[paymentrequest] Tidy-up per discussion (#52) Ade Bateman
Re: [webpayments] Multilingual Support for human-readable labels (#84) Nick S

Friday, 12 February 2016

Thursday, 11 February 2016

Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Adrian Hope-Bailie
Comments on MasterPass flow Ian Jacobs
Re: [paymentrequest] No mention of non-decimal currencies (#40) Adrian Hope-Bailie
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Nick S
Re: [paymentrequest] No mention of non-decimal currencies (#40) Nick S
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley
Re: Checkout API spec published Manu Sporny
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Rouslan Solomakhin
Re: [webpayments] Should we expose status change events in the browser API? (#41) Adrian Hope-Bailie
Re: [webpayments] Should the payment request support multiple pricing options? (#79) Dave Longley
Re: Checkout API spec published Doug Schepers
Re: [web-payments-browser-api] Use of "MUST" in sentence might cause confusion (#6) Manu Sporny
Re: [webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83) Manu Sporny
[web-payments-browser-api] Use of "MUST" in sentence might cause confusion (#6) ianbjacobs
Re: Checkout API spec published Dave Longley
Re: [webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83) Adrian Hope-Bailie
Re: [webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83) Adrian Hope-Bailie
Re: PROPOSAL regarding JSON-LD material Manu Sporny
Re: PROPOSAL regarding JSON-LD material Manu Sporny
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie
Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Manu Sporny
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Manu Sporny
Re: [paymentrequest] Shipping: should merchant supply supported destinations (#2) Ade Bateman
Re: [paymentrequest] Shipping: should merchant supply supported destinations (#2) Ade Bateman
Re: [paymentrequest] Need a "really closed" event (#45) Ade Bateman
Re: [paymentrequest] Need a "really closed" event (#45) Ade Bateman
Re: [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) Ade Bateman
Re: [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) Ade Bateman
Re: PROPOSAL regarding JSON-LD material Ian Jacobs
Re: PROPOSAL regarding JSON-LD material Ian Jacobs
Re: PROPOSAL regarding JSON-LD material Dave Longley
Re: PROPOSAL regarding JSON-LD material Manu Sporny
Comments on 3DS Flow Ian Jacobs
Re: [webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83) Adrian Hope-Bailie
Re: PROPOSAL regarding JSON-LD material Ian Jacobs
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs
Re: [webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83) ianbjacobs
Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Adrian Hope-Bailie
Re: [webpayments] Should the payment request support multiple pricing options? (#79) Adrian Hope-Bailie
Re: [webpayments] How do we protect certian data in the messages from certain parties in the flow as the use case requires? (#78) Adrian Hope-Bailie
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie
Re: [webpayments] How are third-party native wallets integrated? (#42) Adrian Hope-Bailie
Re: Checkout API spec published Adrian Hope-Bailie
Checkout API spec published Zach Koch
Re: [paymentrequest] Proposal to move the complete() method to the PaymentResponse interface (#48) Zach Koch
Re: PROPOSAL regarding JSON-LD material Adrian Hope-Bailie
[webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83) Adrian Hope-Bailie
Re: Checkout API spec published Adrian Hope-Bailie
Re: [webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64) Adrian Hope-Bailie
Re: [webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64) Adrian Hope-Bailie
Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Adrian Hope-Bailie
Re: [webpayments] How are third-party native wallets integrated? (#42) Ade Bateman
Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Ade Bateman
Re: [webpayments] How do we protect certian data in the messages from certain parties in the flow as the use case requires? (#78) Ade Bateman
Re: [webpayments] Should the payment request support multiple pricing options? (#79) Ade Bateman
Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Ade Bateman
Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Ade Bateman
Re: [webpayments] How can the API support enrollment (future payment) use cases? (#65) Nick Shearer
[paymentrequest] Proposal to move the complete() method to the PaymentResponse interface (#48) Ade Bateman
Re: PROPOSAL regarding JSON-LD material Ian Jacobs
Re: [paymentrequest] Spec correctness updates based on review feedback (#47) Ade Bateman
Re: [paymentrequest] Spec correctness updates based on review feedback (#47) Ade Bateman
[paymentrequest] Spec correctness updates based on review feedback (#47) Ade Bateman
Re: PROPOSAL regarding JSON-LD material Manu Sporny
Re: Checkout API spec published Dave Longley

Wednesday, 10 February 2016

Tuesday, 9 February 2016

Re: [webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64) Rouslan Solomakhin
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Rouslan Solomakhin
Re: [webpayments] How can the API support enrollment (future payment) use cases? (#65) Rouslan Solomakhin
Re: [webpayments] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#66) Rouslan Solomakhin
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Rouslan Solomakhin
Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Rouslan Solomakhin
Re: PROPOSAL regarding JSON-LD material Ian Jacobs
Re: PROPOSAL regarding JSON-LD material omar.khan@wellsfargo.com
Re: Checkout API Rouslan Solomakhin
Re: Checkout API Dave Longley
Re: Checkout API Rouslan Solomakhin
Re: Checkout API spec published Ian Jacobs
Re: Checkout API spec published Dave Longley
PROPOSAL regarding JSON-LD material Ian Jacobs
Re: Checkout API spec published Ian Jacobs
Re: Checkout API spec published Dave Longley
Re: Checkout API spec published Ian Jacobs
Re: Checkout API spec published Adrian Hope-Bailie
Re: Checkout API spec published Dave Longley
Re: Checkout API spec published Ian Jacobs
Re: Checkout API spec published Manu Sporny
Re: Checkout API spec published Ian Jacobs
Re: Checkout API spec published Manu Sporny

Monday, 8 February 2016

Re: Checkout API spec published Ian Jacobs
Re: Checkout API spec published Manu Sporny
Web Authentication Working Group Launched Ian Jacobs
Re: Checkout API spec published Adrian Hope-Bailie
Re: Checkout API spec published Zach Koch
Checkout API spec published Manu Sporny

Sunday, 7 February 2016

Saturday, 6 February 2016

Friday, 5 February 2016

Re: [webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64) Zach Koch

Thursday, 4 February 2016

Wednesday, 3 February 2016

Tuesday, 2 February 2016

Monday, 1 February 2016

Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Adrian Hope-Bailie
Registration for ILP Workshop is OPEN Adrian Hope-Bailie
Re: [webpayments] How are cloud-based payment apps supported? (#16) Adrian Hope-Bailie
Re: [webpayments] How are cloud-based payment apps supported? (#16) ianbjacobs
ACTION STRONGLY ENCOURAGED: Flows ready for wider review Telford-Reed, Nick
Re: [webpayments] How are cloud-based payment apps supported? (#16) Adrian Hope-Bailie
Re: [webpayments] How are payment apps shared between different browser brands? (#15) Adrian Hope-Bailie
Re: Concerns around Web Payments HTTP API de-prioritization Adrian Hope-Bailie
Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Erik Anderson
RE: Concerns around Web Payments HTTP API de-prioritization Telford-Reed, Nick
Re: [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Zach Koch
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Dave Longley
Re: [webpayments] How are payment apps shared between different browser brands? (#15) Dave Longley
Re: [webpayments] How are cloud-based payment apps supported? (#16) Dave Longley
Re: [webpayments] How are payment apps shared between different browser brands? (#15) Adrian Hope-Bailie
Re: [webpayments] How are third-party native wallets integrated? (#42) haavardmolland
Re: [webpayments] How are third-party native wallets integrated? (#42) Adrian Hope-Bailie
Re: [webpayments] Should we have separate specifications for payment and registration of payment apps? (#26) Adrian Hope-Bailie
Re: [webpayments] How are payment apps registered? (#14) Adrian Hope-Bailie
Re: [webpayments] How are third-party native wallets integrated? (#42) haavardmolland
Re: [webpayments] How are cloud-based payment apps supported? (#16) Adrian Hope-Bailie
[webpayments] How do we protect certian data in the messages from certain parties in the flow as the use case requires? (#78) Adrian Hope-Bailie
Re: [webpayments] Is tracking payment request state necessary? (#35) Adrian Hope-Bailie
Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) Adrian Hope-Bailie
Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) Adrian Hope-Bailie
Re: [webpayments] How are third-party native wallets integrated? (#42) Adrian Hope-Bailie
[webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Adrian Hope-Bailie
Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Adrian Hope-Bailie
Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Adrian Hope-Bailie
Re: [webpayments] Expression of monetary amounts (#40) Adrian Hope-Bailie
Re: [webpayments] Expression of monetary amounts (#40) Adrian Hope-Bailie
Re: [webpayments] Some amendmends (#75) Adrian Hope-Bailie
Re: [webpayments] Some amendmends (#75) Adrian Hope-Bailie
Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) Adrian Hope-Bailie
Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Adrian Hope-Bailie
Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Adrian Hope-Bailie
Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) Vincent Kuntz
Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Vincent Kuntz
Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Vincent Kuntz
Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Vincent Kuntz
Re: [webpayments] Some amendmends (#75) Alessio Basso

Last message date: Monday, 29 February 2016 21:50:31 UTC