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

Sunday, 31 January 2016
- RE: Concerns around Web Payments HTTP API de-prioritization David Ezell
- Re: [webpayments] Some amendmends (#75) ianbjacobs
- Re: [webpayments] Some amendmends (#75) Alessio Basso
Saturday, 30 January 2016
- RE: Concerns around Web Payments HTTP API de-prioritization Katie Haritos-Shea GMAIL
- Concerns around Web Payments HTTP API de-prioritization Manu Sporny
Friday, 29 January 2016
- Re: [webpayments] Some amendmends (#75) ianbjacobs
- [webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabilized. (#73) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabilized. (#73) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) 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: 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: [web-payments-browser-api] Step 6 of the payment flow is incomplete/unclear (#5) Adrian Hope-Bailie
- Re: [webpayments] SEPA SDD one-off e-mandate Version 01 28 2016 (#74) Adrian Hope-Bailie
- Re: [webpayments] Some amendmends (#75) Adrian Hope-Bailie
- [webpayments] Some amendmends (#75) Alessio Basso
Thursday, 28 January 2016
- wpwg-ACTION-12: Contact the ig chairs about taking up the terms Web Payments Working Group Issue Tracker
- Re: Weekly Web Payments Working Group Meetings - Update your Calendars Ian Jacobs
- 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
- 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) Dave Longley
- Re: [web-payments-browser-api] Step 6 of the payment flow is incomplete/unclear (#5) Dave Longley
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabilized. (#73) Dave Longley
- 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
- 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
- [web-payments-browser-api] Step 6 of the payment flow is incomplete/unclear (#5) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabilized. (#73) ianbjacobs
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) Manu Sporny
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) Manu Sporny
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) ianbjacobs
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) Manu Sporny
- Re: [webpayments] SEPA SDD one-off e-mandate Version 01 28 2016 (#74) fredMeignien
- Re: [webpayments] SEPA SDD one-off e-mandate Version 01 28 2016 (#74) fredMeignien
- [webpayments] SEPA SDD one-off e-mandate Version 01 28 2016 (#74) fredMeignien
- Re: [webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) Manu Sporny
- Re: [webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64) Manu Sporny
- Re: [webpayments] PROPOSAL: The PaymentRequest object MUST NOT expose internal state information to the developer. (#64) Manu Sporny
- Web Payments Community Group Browser API Polyfill Released Manu Sporny
- Re: Agenda 28 January 17:00 UTC Nick Shearer
- Re: Agenda 28 January 17:00 UTC Mountie Lee
Wednesday, 27 January 2016
- Agenda 28 January 17:00 UTC Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Adrian Hope-Bailie
- [webpayments] PROPOSAL: Postpone release of an HTTP API FPWD until the messaging schemas have stabalized. (#73) Adrian Hope-Bailie
- Dashboard Adrian Hope-Bailie
- Re: [webpayments] Should we be publishing a specification for an HTTP API? (#17) ianbjacobs
- Re: Polyfills/Wireframes for the browser API proposals Håvard Molland
- Re: [webpayments] Should we be publishing a specification for an HTTP API? (#17) bifurcation
- [webpayments] ACTION: Summarize arguments for/against shipping address capture (#72) Adrian Hope-Bailie
- Re: [webpayments] Should we be publishing a specification for an HTTP API? (#17) Adrian Hope-Bailie
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Manu Sporny
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Manu Sporny
Tuesday, 26 January 2016
- Re: [webpayments] Updated skins for taskforce reviewed flows (#71) mattsaxon
- [webpayments] Updated skins for taskforce reviewed flows (#71) mattsaxon
- Re: Polyfills/Wireframes for the browser API proposals Zach Koch
- Re: [webpayments] Moved skin from realtime payments into include file (#70) mattsaxon
- Re: Polyfills/Wireframes for the browser API proposals Håvard Molland
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Adrian Hope-Bailie
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Adrian Hope-Bailie
- Process question Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) fredMeignien
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Nick S
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Manu Sporny
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) bifurcation
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Nick S
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) Dave Longley
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Manu Sporny
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) Manu Sporny
Monday, 25 January 2016
- Re: [webpayments] Moved skin from realtime payments into include file (#70) mattsaxon
- [webpayments] Moved skin from realtime payments into include file (#70) mattsaxon
- Re: [webpayments] Added Skin file, participant name changes to ISO20022 (#69) mattsaxon
- [webpayments] Added Skin file, participant name changes to ISO20022 (#69) mattsaxon
- Re: [webpayments] Updated 3DS flow with extra detail (#68) mattsaxon
- [webpayments] Updated 3DS flow with extra detail (#68) mattsaxon
- Re: [webpayments] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#66) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) mattsaxon
Saturday, 23 January 2016
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Manu Sporny
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Zach Koch
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Manu Sporny
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Manu Sporny
- Re: [webpayments] PROPOSAL: Hold WG meetings every week until further notice. (#58) Manu Sporny
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) bifurcation
- Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Hold WG meetings every week until further notice. (#58) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Hold WG meetings every week until further notice. (#58) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Adrian Hope-Bailie
- [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Adrian Hope-Bailie
Friday, 22 January 2016
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Dave Longley
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) bifurcation
- FYI: Web API Design Cookbook Ian Jacobs
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Dave Longley
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Mike West
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Manu Sporny
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Manu Sporny
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Mike West
Thursday, 21 January 2016
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Manu Sporny
- Weekly Web Payments Working Group Meetings - Update your Calendars Ian Jacobs
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) ianbjacobs
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) ianbjacobs
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Zach Koch
- Re: Polyfills/Wireframes for the browser API proposals Manu Sporny
- Re: [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) Dave Longley
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Manu Sporny
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Manu Sporny
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Manu Sporny
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Manu Sporny
- Re: Polyfills/Wireframes for the browser API proposals Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Manu Sporny
- Re: Updated Agenda for 21 January call Manu Sporny
- Re: Polyfills/Wireframes for the browser API proposals Manu Sporny
- Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) ianbjacobs
- Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) ianbjacobs
- Re: [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) kketels
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) mattsaxon
- Re: [paymentrequest] Support for "enrollment" use of API (#43) Adrian Hope-Bailie
- Re: [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) Adrian Hope-Bailie
- [webpayments] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#66) Adrian Hope-Bailie
- [webpayments] How can the API support enrollment (future payment) use cases? (#65) Adrian Hope-Bailie
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Adrian Hope-Bailie
- Updated Agenda for 21 January call Adrian Hope-Bailie
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Adrian Hope-Bailie
- Re: [webpayments] Should a payment request be just data, or a programmable object? (#36) Adrian Hope-Bailie
- [webpayments] PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (#64) Adrian Hope-Bailie
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Adrian Hope-Bailie
- [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63) Adrian Hope-Bailie
- Re: Polyfills/Wireframes for the browser API proposals Adrian Hope-Bailie
- Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) Manu Sporny
- Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) Manu Sporny
- Re: [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) Manu Sporny
- Re: [paymentrequest] Support for "enrollment" use of API (#43) Manu Sporny
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Manu Sporny
- Re: Polyfills/Wireframes for the browser API proposals Manu Sporny
- Re: [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Manu Sporny
- Re: [webpayments] Should a payment request be just data, or a programmable object? (#36) Manu Sporny
- Re: [webpayments] Should a payment request be just data, or a programmable object? (#36) Manu Sporny
Wednesday, 20 January 2016
- Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) Adrian Hope-Bailie
- Additional agenda item for 21 January call Adrian Hope-Bailie
- [webpayments] PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (#62) Adrian Hope-Bailie
- Re: [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) ianbjacobs
- Re: [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) ianbjacobs
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) mattsaxon
- Re: [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) mattsaxon
- Re: [paymentrequest] Support for "enrollment" use of API (#43) mattsaxon
- Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Adrian Hope-Bailie
- RE: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) VIGNET cyril
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) ianbjacobs
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) bifurcation
- Re: [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) bifurcation
- RE: Agenda - 21 January - 17:00 UTC Telford-Reed, Nick
- Re: [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) bifurcation
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Nick Telford-Reed
- [paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46) Ade Bateman
- [paymentrequest] Need a "really closed" event (#45) Ade Bateman
- Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39) Ade Bateman
- Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39) Ade Bateman
- [webpayments] Security and Privacy Self-Review (#61) ianbjacobs
- Re: [paymentrequest] Support for "enrollment" use of API (#43) Ade Bateman
- Re: [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) Ade Bateman
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Laurent Castillo
- Re: [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Adrian Hope-Bailie
- Re: [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Ade Bateman
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Dave Longley
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Vincent Kuntz
- [webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60) Vincent Kuntz
- Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Adrian Hope-Bailie
- [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59) Adrian Hope-Bailie
- Re: [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Zach Koch
- Re: [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Zach Koch
- Re: [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Ade Bateman
- Re: [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Zach Koch
- [paymentrequest] Minor spec changes based on implementation experience and feedback (#44) Ade Bateman
Tuesday, 19 January 2016
- Agenda - 21 January - 17:00 UTC Adrian Hope-Bailie
- [webpayments] PROPOSAL: Hold WG meetings every week until further notice. (#58) Adrian Hope-Bailie
- [webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57) Adrian Hope-Bailie
- Re: European Banking Authority (EBA) Discussion Paper on strong customer and secure communication under PSD2 Ian Jacobs
- Re: [webpayments] Adding ISO 20022 definitions highlights for W3C Web Payments WG (#56) Adrian Hope-Bailie
- [webpayments] Adding ISO 20022 definitions highlights for W3C Web Payments WG (#56) Laurent Castillo
Monday, 18 January 2016
- 3DS 2.0 Adrian Hope-Bailie
Thursday, 14 January 2016
- Polyfills/Wireframes for the browser API proposals Adrian Hope-Bailie
Wednesday, 13 January 2016
- [paymentrequest] Support for "enrollment" use of API (#43) ianbjacobs
- [webpayments] What is the appropriate conversational pattern for the API? (#55) Adrian Hope-Bailie
- Re: [webpayments] Should the payment request contain line item details? (#38) Adrian Hope-Bailie
Tuesday, 12 January 2016
- RE: European Banking Authority (EBA) Discussion Paper on strong customer and secure communication under PSD2 VIGNET cyril
- RE: Progress rapidification (was Re: Labels and Milestones on GitHub) Telford-Reed, Nick
- Re: [webpayments] Capture proposed work changes in wiki (#50) Adrian Hope-Bailie
- Re: [webpayments] Capture proposed work changes in wiki (#50) Adrian Hope-Bailie
- Re: Progress rapidification (was Re: Labels and Milestones on GitHub) Adrian Hope-Bailie
- Progress rapidification (was Re: Labels and Milestones on GitHub) Manu Sporny
Monday, 11 January 2016
- FYI: European Banking Authority (EBA) Discussion Paper on strong customer and secure communication under PSD2 Ian Jacobs
- FYI: W3C Member review of Web Authentication Working Group Charter until 25 January Ian Jacobs
Sunday, 10 January 2016
- Re: [webpayments] Patch 1 (#54) mattsaxon
- [webpayments] Patch 1 (#54) mountielee
- Re: [webpayments] Separated PayPal flow into standard and PSP intermediated following discussions with Dave (#53) mattsaxon
- [webpayments] Separated PayPal flow into standard and PSP intermediated following discussions with Dave (#53) mattsaxon
Saturday, 9 January 2016
- Re: [webpayments] Updated PayPal with annotation based on Dave's feedback (#52) mattsaxon
- [webpayments] Updated PayPal with annotation based on Dave's feedback (#52) mattsaxon
Friday, 8 January 2016
- Re: Labels and Milestones on GitHub Adrian Hope-Bailie
- Re: Labels and Milestones on GitHub Adrian Hope-Bailie
- Re: Labels and Milestones on GitHub Ian Jacobs
- Re: [webpayments] Updated Authentication to read Authorisation (#51) mattsaxon
- [webpayments] Updated Authentication to read Authorisation (#51) mattsaxon
Thursday, 7 January 2016
- [Minutes] 7 January 2016 call Ian Jacobs
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) ianbjacobs
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Dave Longley
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) ianbjacobs
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: Labels and Milestones on GitHub Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) ianbjacobs
- Re: Labels and Milestones on GitHub Adrian Hope-Bailie
- [webpayments] Capture proposed work changes in wiki (#50) Adrian Hope-Bailie
- [webpayments] Refactor flows to use common terminology and entry/exit points (#49) Adrian Hope-Bailie
- wpwg-ACTION-11: Ping mountie about samsung and escrow flows Web Payments Working Group Issue Tracker
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- RE: Agenda: 7 Jan 2016 Web Payments WG call David Ezell
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) ianbjacobs
- RE: Labels and Milestones on GitHub Katie Haritos-Shea GMAIL
- Labels and Milestones on GitHub Adrian Hope-Bailie
- Re: [webpayments] Update Apple Pay flow and add Bank Mobile Wallet (#45) Adrian Hope-Bailie
- RE: SCAI - update with Credit Transfer and Direct debit flows VIGNET cyril
- Meta-issues for the group Adrian Hope-Bailie
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
Wednesday, 6 January 2016
- Re: [webpayments] Updated PayPal to correct redirect and add notifications (#48) mattsaxon
- [webpayments] Updated PayPal to correct redirect and add notifications (#48) mattsaxon
- Re: [webpayments] Added Cross Border, minor revisions to RealTime payment (#47) mattsaxon
- [webpayments] Added Cross Border, minor revisions to RealTime payment (#47) mattsaxon
- Agenda: 7 Jan 2016 Web Payments WG call Ian Jacobs
- Re: [webpayments] Gh pages (#46) mattsaxon
- [webpayments] Gh pages (#46) mattsaxon
- [webpayments] Update Apple Pay flow and add Bank Mobile Wallet (#45) Laurent Castillo
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) ianbjacobs
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Manu Sporny
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Adrian Hope-Bailie
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) ianbjacobs
- Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) Stefan Thomas
- Re: SCAI - update with Credit Transfer and Direct debit flows Anders Rundgren
Tuesday, 5 January 2016
- Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37) kevingordonwp
Monday, 4 January 2016
- Re: [paymentrequest] Refactor PaymentDetails. (383c224) jayrenn
- Re: [paymentrequest] Refactor PaymentDetails. (383c224) jayrenn
- SCAI - update with Credit Transfer and Direct debit flows VIGNET cyril

Last message date: Sunday, 31 January 2016 18:16:34 UTC
Archived on: Friday, 17 January 2020 16:43:13 UTC

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