public-payments-wg@w3.org from December 2015 by author

Adam Forsyth

• Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39) (Thursday, 17 December)
• [paymentrequest] No mention of non-decimal currencies (#40) (Wednesday, 16 December)
• [paymentrequest] CurrencyAmount description has exponent sign wrong (#39) (Wednesday, 16 December)

Ade Bateman

• Re: [paymentrequest] Update API document with missing details (#38) (Tuesday, 15 December)
• [paymentrequest] Update API document with missing details (#38) (Tuesday, 15 December)
• Re: [paymentrequest] Price breakdown (#25) (Friday, 11 December)
• [paymentrequest] Second set of API refactoring changes (#37) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [paymentrequest] Updated documents to ensure all issues notes link to issue in the repo. (#36) (Wednesday, 9 December)
• [paymentrequest] Updated documents to ensure all issues notes link to issue in the repo. (#36) (Wednesday, 9 December)
• [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Wednesday, 9 December)
• [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34) (Wednesday, 9 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Wednesday, 9 December)
• [paymentrequest] Should we support a delegated state for PaymentRequest? (#33) (Wednesday, 9 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Wednesday, 9 December)
• Re: [paymentrequest] Standardizing Common Payment Instruments (#20) (Wednesday, 9 December)
• Re: [paymentrequest] UI for Payment Instrument (#17) (Wednesday, 9 December)
• Re: [paymentrequest] UI for Payment Instrument (#17) (Wednesday, 9 December)
• [paymentrequest] Should the web page be able to provide status information before calling complete() (#32) (Wednesday, 9 December)
• Re: [paymentrequest] Let merchant pass in arbitrary data to payment request? (#11) (Wednesday, 9 December)
• Re: [paymentrequest] Let merchant pass in arbitrary data to payment request? (#11) (Wednesday, 9 December)
• Re: [paymentrequest] Reconsider the need to include shipping in this spec (#8) (Wednesday, 9 December)
• Re: [paymentrequest] Reconsider the need to include shipping in this spec (#8) (Wednesday, 9 December)
• [paymentrequest] Write-up initial proposal for card payment method spec (#31) (Wednesday, 9 December)
• Re: [paymentrequest] Chain of trust between browser and merchant (#9) (Wednesday, 9 December)
• Re: [paymentrequest] Chain of trust between browser and merchant (#9) (Wednesday, 9 December)
• [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Wednesday, 9 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a secure context? (#29) (Wednesday, 9 December)
• [paymentrequest] Should the Payment Request API only be available in a secure context? (#29) (Wednesday, 9 December)
• Re: [paymentrequest] Price breakdown (#25) (Wednesday, 9 December)
• [paymentrequest] Write-up proposal for shipping address fields (#28) (Wednesday, 9 December)
• Re: [paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14) (Wednesday, 9 December)
• Re: [paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14) (Wednesday, 9 December)
• [paymentrequest] Write-up initial proposal for payment app registration spec (#27) (Wednesday, 9 December)
• Re: [paymentrequest] Could we design appropriate declarative models to go along with the API? (#13) (Wednesday, 9 December)
• Re: [paymentrequest] Could we design appropriate declarative models to go along with the API? (#13) (Wednesday, 9 December)
• Re: [paymentrequest] How do we think it will work with ServiceWorker? (#12) (Wednesday, 9 December)
• Re: [paymentrequest] How do we think it will work with ServiceWorker? (#12) (Wednesday, 9 December)
• Re: [paymentrequest] Can we call out how this relates to other payment efforts? (#6) (Wednesday, 9 December)
• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 9 December)
• Re: [paymentrequest] Currency Specification (#18) (Wednesday, 9 December)
• Re: [paymentrequest] There should be a way for the merchant to indicate the instrumentResponse was a failure (#15) (Wednesday, 9 December)
• [paymentrequest] First set of API refactoring changes. (#26) (Wednesday, 9 December)
• Re: [paymentrequest] Overridng Common Payment Instruments (#21) (Tuesday, 8 December)
• Re: [paymentrequest] Overridng Common Payment Instruments (#21) (Tuesday, 8 December)
• Re: [paymentrequest] Standardizing Common Payment Instruments (#20) (Tuesday, 8 December)
• Re: [paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14) (Tuesday, 8 December)
• Re: [paymentrequest] Payment instruments not supported by proposal (#10) (Tuesday, 8 December)
• Re: [paymentrequest] Can we call out how this relates to other payment efforts? (#6) (Tuesday, 8 December)
• Re: [paymentrequest] Do we need to support transactions that aren't finalised by the merchant in v1? (#3) (Tuesday, 8 December)
• Re: [paymentrequest] Do we need to support transactions that aren't finalised by the merchant in v1? (#3) (Tuesday, 8 December)
• Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24) (Sunday, 6 December)
• [paymentrequest] Added initial spec drafts and architecture overview. (#24) (Saturday, 5 December)

Adrian Hope-Bailie

• [paymentrequest] Use navigator.payments rather than creating a new object instance (#42) (Monday, 21 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Friday, 18 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Friday, 18 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Friday, 18 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Friday, 18 December)
• Re: [admin] (Thursday, 17 December)
• Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Thursday, 17 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Thursday, 17 December)
• [paymentrequest] Combine API parameters into a single request object + options (#41) (Thursday, 17 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Thursday, 17 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Thursday, 17 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Wednesday, 16 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Wednesday, 16 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Wednesday, 16 December)
• Re: [webpayments] Abstract payment architecture (#11) (Monday, 14 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [Architecture] Updated wiki to address some comments (Friday, 11 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34) (Thursday, 10 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 10 December)
• Re: [webpayments] Abstract payment architecture (#11) (Thursday, 10 December)
• Re: [webpayments] Abstract payment architecture (#11) (Thursday, 10 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Thursday, 10 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Wednesday, 9 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Wednesday, 9 December)
• Re: [webpayments] How do organizations layer additional information in the core messages? (#18) (Wednesday, 9 December)
• Re: [webpayments] Is there an HTTP API based message flow? (#17) (Wednesday, 9 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Wednesday, 9 December)
• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Wednesday, 9 December)
• Re: [webpayments] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#29) (Wednesday, 9 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Wednesday, 9 December)
• Re: [webpayments] Minimum necessary information for merchant to process payment (#27) (Wednesday, 9 December)
• Re: [paymentrequest] Payment instrument installation is platform-dependent (#5) (Wednesday, 9 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Wednesday, 9 December)
• [Architecture] Updated wiki to address some comments (Wednesday, 9 December)
• Re: [webpayments] Machine readability of payment methods? (#30) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: Experimental glossary definitions added (Monday, 7 December)
• Re: [webpayments] Merge Payment Request Architecture with Capabilities Document (#22) (Monday, 7 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Monday, 7 December)
• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 2 December)
• Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki) (Tuesday, 1 December)

Anders Rundgren

• Re: [webpayments] How are third-party native wallets integrated? (#42) (Tuesday, 22 December)
• Re: [webpayments] How are third-party native wallets integrated? (#42) (Monday, 21 December)
• Re: [webpayments] How are third-party native wallets integrated? (#42) (Monday, 21 December)
• [webpayments] How are third-party native wallets integrated? (#42) (Saturday, 19 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Wednesday, 2 December)

Brad Hill

• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Friday, 11 December)

Cyril VIGNET

• Re: [webpayments] How are payment messages trusted? (#19) (Wednesday, 2 December)

Dave Longley

• Re: [webpayments] Expression of monetary amounts (#40) (Saturday, 19 December)
• Re: [admin] (Friday, 18 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Thursday, 17 December)
• Re: [webpayments] Is tracking payment request state necessary? (#35) (Thursday, 17 December)
• Re: [webpayments] Is there an HTTP API based message flow? (#17) (Thursday, 17 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Thursday, 17 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Thursday, 17 December)
• Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37) (Thursday, 17 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Thursday, 17 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Thursday, 17 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Thursday, 17 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Thursday, 17 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Wednesday, 16 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• Re: [webpayments] Should a payment request be just data, or a programmable object? (#36) (Wednesday, 16 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 10 December)
• Re: [webpayments] Abstract payment architecture (#11) (Thursday, 10 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Minimum necessary information for merchant to process payment (#27) (Monday, 7 December)
• Re: [webpayments] How do organizations layer additional information in the core messages? (#18) (Monday, 7 December)
• Re: [webpayments] Machine readability of payment methods? (#30) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Thursday, 3 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Thursday, 3 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Thursday, 3 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 3 December)

David Ezell

• RE: Agenda for tomorrow's call (Thursday, 17 December)
• RE: Experimental glossary definitions added (Monday, 7 December)

David I. Lehn

• Re: [webpayments] Expression of monetary amounts (#40) (Saturday, 19 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Wednesday, 16 December)

dezell

• Re: [webpayments] Expression of monetary amounts (#40) (Wednesday, 16 December)

Doug Schepers

• [admin] (Thursday, 17 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)

Erik Anderson

• [WPAY WG] Additional ANSI standards for Authentication(X9.122) added to WatchDox (Monday, 7 December)

fredMeignien

• Re: [webpayments] SDD one off e-mandate (#43) (Thursday, 24 December)
• [webpayments] SDD one off e-mandate (#43) (Monday, 21 December)

hober

• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 2 December)
• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 2 December)
• Re: [paymentrequest] API needs equivalent of the paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Tuesday, 1 December)
• [paymentrequest] API needs equivalent of the paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Tuesday, 1 December)
• Re: [paymentrequest] Payment instruments not supported by proposal (#10) (Tuesday, 1 December)

Ian Jacobs

• [Feb 2016 FTF meeting] Nearby hotels (Monday, 21 December)
• Scheduled: February 2016 Web Payments Working Group FTF (Wednesday, 9 December)
• Re: Linking the Wiki to the example Flows (Friday, 4 December)
• Re: Linking the Wiki to the example Flows (Friday, 4 December)
• Re: Linking the Wiki to the example Flows (Thursday, 3 December)
• Re: Linking the Wiki to the example Flows (Thursday, 3 December)
• [Minutes] 3 Dec 2015 WPWG meeting (Thursday, 3 December)
• Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki) (Tuesday, 1 December)

ianbjacobs

• Re: [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33) (Wednesday, 23 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• Re: [webpayments] Confining the definition of user agents to browsers (#34) (Wednesday, 16 December)
• Re: [paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34) (Thursday, 10 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 10 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 10 December)
• Re: [paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35) (Thursday, 10 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Wednesday, 9 December)
• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Wednesday, 9 December)
• Re: [paymentrequest] Payment instrument installation is platform-dependent (#5) (Wednesday, 9 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [webpayments] Merge Payment Request Architecture with Capabilities Document (#22) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23) (Monday, 7 December)
• Re: [webpayments] Machine readability of payment methods? (#30) (Monday, 7 December)
• Re: [webpayments] Machine readability of payment methods? (#30) (Sunday, 6 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Friday, 4 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Thursday, 3 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Wednesday, 2 December)
• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Wednesday, 2 December)

jayrenn

• [paymentrequest] Price breakdown (#25) (Tuesday, 8 December)

Jeff Burdges

• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Sunday, 20 December)
• Re: [webpayments] Should a payment request be just data, or a programmable object? (#36) (Sunday, 20 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Friday, 11 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)

Manu Sporny

• Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Thursday, 17 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Thursday, 17 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Wednesday, 16 December)
• [webpayments] Should we expose status change events in the browser API? (#41) (Wednesday, 16 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Wednesday, 16 December)
• [webpayments] Expression of monetary amounts (#40) (Wednesday, 16 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Wednesday, 16 December)
• [webpayments] What is the use case for the Payment Details object? (#38) (Wednesday, 16 December)
• Re: [webpayments] Should list of accepted payment methods be strings or objects? (#37) (Wednesday, 16 December)
• [webpayments] Should list of accepted payment methods be strings or objects? (#37) (Wednesday, 16 December)
• Re: [webpayments] Should a payment request be just data, or a programmable object? (#36) (Wednesday, 16 December)
• [webpayments] Should a payment request be just data, or a programmable object? (#36) (Wednesday, 16 December)
• [webpayments] Is tracking payment request state necessary? (#35) (Wednesday, 16 December)
• Re: [webpayments] Is there an HTTP API based message flow? (#17) (Wednesday, 16 December)
• Re: [webpayments] Confining the definition of user agents to browsers (#34) (Wednesday, 16 December)
• Re: [webpayments] Confining the definition of user agents to browsers (#34) (Wednesday, 16 December)
• [webpayments] Confining the definition of user agents to browsers (#34) (Wednesday, 16 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Friday, 11 December)
• Re: [Architecture] Updated wiki to address some comments (Friday, 11 December)
• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Wednesday, 9 December)
• Re: [paymentrequest] Overridng Common Payment Instruments (#21) (Tuesday, 8 December)
• Re: [webpayments] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#29) (Monday, 7 December)
• Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23) (Monday, 7 December)
• Re: Linking the Wiki to the example Flows (Monday, 7 December)
• Re: [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29) (Sunday, 6 December)
• Re: [webpayments] Machine readability of payment methods? (#30) (Sunday, 6 December)
• [webpayments] Machine readability of payment methods? (#30) (Sunday, 6 December)
• [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29) (Sunday, 6 December)
• Re: [webpayments] How do organizations layer additional information in the core messages? (#18) (Sunday, 6 December)
• Re: [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Sunday, 6 December)
• Re: [webpayments] How do organizations layer additional information in the core messages? (#18) (Sunday, 6 December)
• [webpayments] What gets registered - apps, wallets, or payment instruments? (#28) (Sunday, 6 December)
• Re: [webpayments] Minimum necessary information for merchant to process payment (#27) (Sunday, 6 December)
• [webpayments] Minimum necessary information for merchant to process payment (#27) (Sunday, 6 December)
• [webpayments] Splitting registration from payment (#26) (Sunday, 6 December)
• [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Sunday, 6 December)
• [webpayments] Document relationship diagrams? (#24) (Sunday, 6 December)
• Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23) (Sunday, 6 December)
• [webpayments] Payment Request Architecture glossary should include IG glossary (#23) (Sunday, 6 December)
• [webpayments] Merge Payment Request Architecture with Capabilities Document (#22) (Sunday, 6 December)
• New landing page for Google/Microsoft paymentRequest() API (Sunday, 6 December)
• Re: [paymentrequest] Update explainer.md (#7) (Sunday, 6 December)
• Re: [paymentrequest] Update explainer.md (#7) (Sunday, 6 December)
• Experimental glossary definitions added (Sunday, 6 December)
• Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24) (Sunday, 6 December)
• Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24) (Sunday, 6 December)
• Re: [webpayments] No proprietary binary files, please (#7) (Sunday, 6 December)
• Re: [webpayments] No proprietary binary files, please (#7) (Sunday, 6 December)
• Re: [webpayments] No proprietary binary files, please (#7) (Sunday, 6 December)
• Re: Linking the Wiki to the example Flows (Friday, 4 December)
• Re: Linking the Wiki to the example Flows (Thursday, 3 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Thursday, 3 December)
• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Thursday, 3 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Thursday, 3 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Thursday, 3 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Thursday, 3 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Thursday, 3 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Thursday, 3 December)
• Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki) (Wednesday, 2 December)
• Re: New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki) (Wednesday, 2 December)
• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Wednesday, 2 December)
• [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Wednesday, 2 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Wednesday, 2 December)
• [webpayments] How are payment messages trusted? (#19) (Wednesday, 2 December)
• Re: [webpayments] How do organizations layer additional information in the core messages? (#18) (Wednesday, 2 December)
• [webpayments] How do organizations layer additional information in the core messages? (#18) (Wednesday, 2 December)
• Re: [webpayments] Is there an HTTP API based message flow? (#17) (Wednesday, 2 December)
• [webpayments] Is there an HTTP API based message flow? (#17) (Wednesday, 2 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Wednesday, 2 December)
• [webpayments] How are cloud-based payment instruments supported? (#16) (Wednesday, 2 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Wednesday, 2 December)
• [webpayments] How are payment instruments shared between different browser brands? (#15) (Wednesday, 2 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Wednesday, 2 December)
• [webpayments] How are payment instruments registered? (#14) (Wednesday, 2 December)

Marcos Caceres

• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 2 December)

Matt Saxon

• RE: Linking the Wiki to the example Flows (Friday, 4 December)

mattsaxon

• [webpayments] Added Apple Pay (#44) (Wednesday, 30 December)
• Re: [webpayments] Added Apple Pay (#44) (Wednesday, 30 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Wednesday, 23 December)
• Re: [webpayments] SDD one off e-mandate (#43) (Wednesday, 23 December)
• Re: [webpayments] Should the payment request contain line item details? (#38) (Wednesday, 23 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Wednesday, 23 December)
• Re: [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33) (Wednesday, 23 December)
• [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33) (Friday, 11 December)
• Re: [webpayments] Refined SEPA Credit Transfer to add the web interactions (#33) (Friday, 11 December)
• Re: [webpayments] Abstract payment architecture (#11) (Friday, 11 December)
• Re: [webpayments] Added PSP Hosted Card Payment (#32) (Friday, 11 December)
• [webpayments] Added PSP Hosted Card Payment (#32) (Friday, 11 December)
• Re: [webpayments] Abstract payment architecture (#11) (Wednesday, 9 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Friday, 4 December)
• Re: [webpayments] Uploaded Credit Transfer files for Cyril (#21) (Friday, 4 December)
• [webpayments] Uploaded Credit Transfer files for Cyril (#21) (Friday, 4 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Friday, 4 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Friday, 4 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Friday, 4 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Wednesday, 2 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Wednesday, 2 December)
• Re: [webpayments] Is there an HTTP API based message flow? (#17) (Wednesday, 2 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Wednesday, 2 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Wednesday, 2 December)

mountainhippo

• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Wednesday, 16 December)
• Re: [paymentrequest] Clarity on Currency Conversion (#19) (Thursday, 3 December)
• Re: [webpayments] How are payment messages trusted? (#19) (Thursday, 3 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Thursday, 3 December)
• Re: [webpayments] Is there an HTTP API based message flow? (#17) (Thursday, 3 December)
• Re: [webpayments] How are payment instruments shared between different browser brands? (#15) (Thursday, 3 December)

mountielee

• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Thursday, 10 December)

Nick Telford-Reed

• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Thursday, 17 December)

Rouslan Solomakhin

• Re: [webpayments] How are third-party native wallets integrated? (#42) (Tuesday, 22 December)
• Re: [webpayments] How are third-party native wallets integrated? (#42) (Monday, 21 December)
• Re: [webpayments] How are third-party native wallets integrated? (#42) (Monday, 21 December)
• Re: [webpayments] How are third-party native wallets integrated? (#42) (Monday, 21 December)
• Re: [webpayments] How are payment instruments registered? (#14) (Wednesday, 2 December)
• Re: [webpayments] How are cloud-based payment instruments supported? (#16) (Wednesday, 2 December)

Shane McCarron

• Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31) (Tuesday, 8 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: Linking the Wiki to the example Flows (Monday, 7 December)
• Re: [webpayments] Should Payment Method Identifiers be a Linked Data Vocabulary? (#29) (Sunday, 6 December)
• Re: [webpayments] Machine readability of payment methods? (#30) (Sunday, 6 December)
• Re: [webpayments] Payment Request Architecture glossary should include IG glossary (#23) (Sunday, 6 December)
• Re: Linking the Wiki to the example Flows (Friday, 4 December)
• Re: Linking the Wiki to the example Flows (Thursday, 3 December)
• Linking the Wiki to the example Flows (Thursday, 3 December)
• Re: [webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20) (Wednesday, 2 December)

Telford-Reed, Nick

• Agenda for tomorrow's call (Wednesday, 16 December)
• Meeting 3rd December at 17:00 UTC (Wednesday, 2 December)

Vincent Kuntz

• Re: [webpayments] Should the payment request contain line item details? (#38) (Tuesday, 29 December)
• Re: [webpayments] Expression of monetary amounts (#40) (Tuesday, 29 December)

Web Payments Working Group Issue Tracker

• wpwg-ACTION-10: Integrate standard flow into web payments cg's browser api spec. (Thursday, 17 December)
• wpwg-ACTION-9: Share iso20022 glossary/terminology (Friday, 11 December)

Zach Koch

• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Thursday, 17 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Thursday, 17 December)
• Re: [paymentrequest] CurrencyAmount description has exponent sign wrong (#39) (Thursday, 17 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Thursday, 17 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• Re: [webpayments] What is the use case for the Payment Details object? (#38) (Wednesday, 16 December)
• Re: [webpayments] Should we expose status change events in the browser API? (#41) (Wednesday, 16 December)
• Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) (Wednesday, 16 December)
• Re: [paymentrequest] Second set of API refactoring changes (#37) (Friday, 11 December)
• Re: [paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30) (Wednesday, 9 December)
• Re: [paymentrequest] First set of API refactoring changes. (#26) (Wednesday, 9 December)
• Re: [paymentrequest] Overridng Common Payment Instruments (#21) (Tuesday, 8 December)
• Re: [paymentrequest] Payment instruments not supported by proposal (#10) (Tuesday, 8 December)
• Re: [paymentrequest] Payment instruments not supported by proposal (#10) (Tuesday, 8 December)
• Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25) (Monday, 7 December)
• Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24) (Sunday, 6 December)
• Re: [paymentrequest] Added initial spec drafts and architecture overview. (#24) (Sunday, 6 December)
• Re: [paymentrequest] Clarity on Currency Conversion (#19) (Thursday, 3 December)
• Re: [paymentrequest] Clarity on Currency Conversion (#19) (Thursday, 3 December)
• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 2 December)
• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Wednesday, 2 December)
• Re: [paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23) (Tuesday, 1 December)
• Re: [paymentrequest] Location of Authorisation in the flow (#22) (Tuesday, 1 December)

Last message date: Wednesday, 30 December 2015 14:28:57 UTC