- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Adrian Hope-Bailie (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Zach Koch (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Jeff Burdges (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Laurent Castillo (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Laurent Castillo (Wednesday, 24 February)
- Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66) Dave Longley (Thursday, 25 February)
Meeting today Telford-Reed, Nick (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny (Monday, 15 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Adrian Hope-Bailie (Monday, 15 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Adrian Hope-Bailie (Monday, 15 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) ianbjacobs (Monday, 15 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Adrian Hope-Bailie (Tuesday, 16 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) mattsaxon (Wednesday, 17 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Rouslan Solomakhin (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Rouslan Solomakhin (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Zach Koch (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Rouslan Solomakhin (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Nick S (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Nick Telford-Reed (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley (Thursday, 18 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny (Sunday, 21 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Nick S (Sunday, 21 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Adrian Hope-Bailie (Sunday, 21 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley (Sunday, 21 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Dave Longley (Sunday, 21 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny (Monday, 22 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) ianbjacobs (Monday, 22 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny (Monday, 22 February)
- Re: [webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89) Manu Sporny (Monday, 22 February)
- Re: Checkout API spec published Zach Koch (Monday, 8 February)
- Re: Checkout API spec published Adrian Hope-Bailie (Monday, 8 February)
- Re: Checkout API spec published Manu Sporny (Monday, 8 February)
- Re: Checkout API spec published Ian Jacobs (Monday, 8 February)
- Re: Checkout API spec published Manu Sporny (Tuesday, 9 February)
- Re: Checkout API spec published Ian Jacobs (Tuesday, 9 February)
- Re: Checkout API spec published Manu Sporny (Tuesday, 9 February)
- Re: Checkout API spec published Ian Jacobs (Tuesday, 9 February)
- Re: Checkout API spec published Dave Longley (Tuesday, 9 February)
- Re: Checkout API spec published Adrian Hope-Bailie (Tuesday, 9 February)
- Re: Checkout API spec published Ian Jacobs (Tuesday, 9 February)
- Re: Checkout API spec published Dave Longley (Tuesday, 9 February)
- Re: Checkout API spec published Ian Jacobs (Tuesday, 9 February)
- Re: Checkout API spec published Dave Longley (Tuesday, 9 February)
- Re: Checkout API spec published Ian Jacobs (Tuesday, 9 February)
- Re: Checkout API spec published Rouslan Solomakhin (Wednesday, 10 February)
- Re: Checkout API spec published Dave Longley (Thursday, 11 February)
- Re: Checkout API spec published Adrian Hope-Bailie (Thursday, 11 February)
- Checkout API spec published Zach Koch (Thursday, 11 February)
- Re: Checkout API spec published Adrian Hope-Bailie (Thursday, 11 February)
- Re: Checkout API spec published Dave Longley (Thursday, 11 February)
Re: Checkout API spec published Doug Schepers (Thursday, 11 February)
interested in JSON-LD omar.khan@wellsfargo.com (Saturday, 6 February)
Checkout API Dave Longley (Thursday, 4 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Manu Sporny (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Rouslan Solomakhin (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Thursday, 11 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Rouslan Solomakhin (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Zach Koch (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Friday, 12 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie (Monday, 15 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie (Monday, 15 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman (Monday, 15 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie (Tuesday, 16 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Ade Bateman (Tuesday, 16 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Tuesday, 16 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Tuesday, 16 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Jake Archibald (Tuesday, 16 February)
- Re: [webpayments] What is the appropriate conversational pattern for the API? (#55) Dave Longley (Tuesday, 16 February)
- 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) Ade Bateman (Thursday, 4 February)
- 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) Manu Sporny (Thursday, 4 February)
- 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) Ade Bateman (Thursday, 4 February)
- 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 (Friday, 5 February)
- 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) Manu Sporny (Saturday, 6 February)
- 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) Manu Sporny (Saturday, 6 February)
- 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) Manu Sporny (Saturday, 6 February)
- 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) Manu Sporny (Saturday, 6 February)
- 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 (Tuesday, 9 February)
- 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) Manu Sporny (Wednesday, 10 February)
- 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 (Thursday, 11 February)
- 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 (Thursday, 11 February)
- 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 (Monday, 15 February)
- 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) Manu Sporny (Monday, 15 February)
- 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) Manu Sporny (Monday, 15 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Vincent Kuntz (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Adrian Hope-Bailie (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Adrian Hope-Bailie (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dan Brickley (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Erik Anderson (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) ianbjacobs (Wednesday, 3 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) obkhan (Thursday, 4 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Manu Sporny (Sunday, 7 February)
- Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27) Melvin Carvalho (Wednesday, 10 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Adrian Hope-Bailie (Tuesday, 2 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Dave Longley (Tuesday, 2 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Alessio Basso (Tuesday, 2 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Manu Sporny (Wednesday, 3 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Rouslan Solomakhin (Wednesday, 3 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Alessio Basso (Thursday, 4 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Shane McCarron (Sunday, 7 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Ade Bateman (Thursday, 11 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Adrian Hope-Bailie (Thursday, 11 February)
- Re: [webpayments] Should the payment request support multiple pricing options? (#79) Dave Longley (Thursday, 11 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) haavardmolland (Monday, 1 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Adrian Hope-Bailie (Monday, 1 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) haavardmolland (Monday, 1 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Ade Bateman (Thursday, 11 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Adrian Hope-Bailie (Thursday, 11 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) mattsaxon (Friday, 12 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Rouslan Solomakhin (Thursday, 18 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Håvard Molland (Thursday, 18 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Rouslan Solomakhin (Thursday, 18 February)
- Re: [webpayments] How are third-party native wallets integrated? (#42) Håvard Molland (Friday, 19 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Manu Sporny (Wednesday, 3 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Adrian Hope-Bailie (Wednesday, 3 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Dave Longley (Wednesday, 3 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Rouslan Solomakhin (Wednesday, 3 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Alessio Basso (Thursday, 4 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Ade Bateman (Thursday, 4 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Alessio Basso (Thursday, 4 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) mattsaxon (Wednesday, 10 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Ade Bateman (Thursday, 11 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Adrian Hope-Bailie (Thursday, 11 February)
- Re: [webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77) Adrian Hope-Bailie (Monday, 15 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Dave Longley (Monday, 1 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Dave Longley (Thursday, 4 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Rouslan Solomakhin (Tuesday, 9 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs (Tuesday, 9 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Rouslan Solomakhin (Tuesday, 9 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Zach Koch (Wednesday, 10 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs (Wednesday, 10 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs (Wednesday, 10 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Ade Bateman (Thursday, 11 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs (Thursday, 11 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Nick S (Thursday, 11 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Adrian Hope-Bailie (Thursday, 11 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) fredMeignien (Friday, 12 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs (Friday, 12 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Nick S (Friday, 12 February)
- Re: [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) ianbjacobs (Friday, 12 February)
Last message date: Monday, 29 February 2016 21:50:31 UTC