public-webpayments-specs@w3.org from September 2016 by author

adamroach

• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/webpayments-payment-apps-api] Versioning (#45) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Tuesday, 20 September)
• Re: [w3c/webpayments-payment-apps-api] How can a Browser-based Payment App cancel the payment flow? (#37) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Add allowpaymentrequest attribute for iframe support (#268) (Sunday, 18 September)
• Re: [w3c/browser-payment-api] Add allowpaymentrequest attribute for iframe support (#268) (Sunday, 18 September)
• [w3c/webpayments-payment-apps-api] Added optionId field to PaymentAppRequestData dictionary (#44) (Saturday, 17 September)
• [w3c/webpayments-payment-apps-api] Proposed text for service-worker-based implementation of payment apps (#41) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 8 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 8 September)

Ade Bateman

• Re: [w3c/webpayments-methods-card] Update editor list (#15) (Wednesday, 28 September)
• Re: [w3c/webpayments-method-identifiers] Add github links (#14) (Wednesday, 28 September)
• Re: [w3c/webpayments-method-identifiers] Update editor list (#15) (Wednesday, 28 September)
• Re: [w3c/browser-payment-api] Update editor list (#288) (Wednesday, 28 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Friday, 23 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Thursday, 22 September)
• Re: [w3c/browser-payment-api] Describe risk of exposing available payment methods (#284) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] Should show() depend on a user action? (#283) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Tuesday, 20 September)
• [w3c/browser-payment-api] Fix shippingType to avoid TypeError (#285) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Fix shippingType to avoid TypeError (#285) (Monday, 19 September)
• Re: [w3c/browser-payment-api] There might be a conflict between 'shippingType' in PaymentOptions and WebIDL binding. (#271) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Expand Privacy Considerations Section (#228) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Expand Privacy Considerations Section (#228) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Monday, 19 September)
• [w3c/webpayments-methods-card] Remove flow diagram. (#14) (Monday, 19 September)
• Re: [w3c/webpayments-methods-card] Remove flow diagram. (#14) (Monday, 19 September)
• Re: [w3c/webpayments-methods-card] Editorial suggestions (#9) (Monday, 19 September)
• Re: [w3c/webpayments-methods-card] Editorial suggestions (#9) (Monday, 19 September)
• Re: [w3c/webpayments-methods-card] Added BasicCardRequest dictionary supporting specification of RequiredFields (#4) (Monday, 19 September)
• Re: [w3c/webpayments-methods-card] Added BasicCardRequest dictionary supporting specification of RequiredFields (#4) (Monday, 19 September)
• Re: [w3c/browser-payment-api] API flow (#177) (Monday, 19 September)
• Re: [w3c/browser-payment-api] API flow (#177) (Monday, 19 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Monday, 19 September)
• [w3c/browser-payment-api] Describe risk of exposing available payment methods (#284) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Should show() depend on a user action? (#283) (Monday, 19 September)
• Re: [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Monday, 19 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Added clarification about target of details (#282) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Remove must in complete() (#280) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Fixed typos (#281) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Add informative reference to CLDR (#277) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Make text active voice, present tense (#272) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Fixed a typo (#276) (Monday, 19 September)
• Re: [w3c/browser-payment-api] There might be a conflict between 'shippingType' in PaymentOptions and WebIDL binding. (#271) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Storing card information (#2) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Add Security Considerations and Privacy Considerations sections (#6) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Add Security Considerations and Privacy Considerations sections (#6) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Storing card information (#2) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Storing card information (#2) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Reference trademarks (#1) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Reference trademarks (#1) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Update references and issue markers (#3) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Update references and issue markers (#3) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Update the payment method identifier to "basic-card" (#12) (Sunday, 18 September)
• [w3c/webpayments-methods-card] Describe the payment method request data. (#13) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Describe the payment method request data. (#13) (Sunday, 18 September)
• [w3c/webpayments-methods-card] Update the payment method identifier to "basic-card" (#12) (Sunday, 18 September)
• [w3c/webpayments-methods-card] Update to use the PaymentAddress type for billing address. (#11) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Update to use the PaymentAddress type for billing address. (#11) (Sunday, 18 September)
• Re: [w3c/webpayments-methods-card] Remove PAYMENT-ARCH dependency and update links to new repo (#10) (Sunday, 18 September)
• [w3c/webpayments-methods-card] Remove PAYMENT-ARCH dependency and update links to new repo (#10) (Sunday, 18 September)
• Re: [w3c/browser-payment-api] Reducing the gap to Apple's API (#270) (Saturday, 17 September)
• [w3c/browser-payment-api] Reducing the gap to Apple's API (#270) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Remove issue markers for issues postponed past v1. (#269) (Saturday, 17 September)
• [w3c/browser-payment-api] Remove issue markers for issues postponed past v1. (#269) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Add allowpaymentrequest attribute for iframe support (#268) (Saturday, 17 September)
• [w3c/browser-payment-api] Add allowpaymentrequest attribute for iframe support (#268) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] What should happen when invalid data is provided? (#265) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] API flow (#177) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Should the API support field validation? (#225) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Add security text regarding payment apps and phishing (#233) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Add security text regarding payment apps and phishing (#233) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Expand Security Considerations Section (#231) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Expand Security Considerations Section (#231) (Saturday, 17 September)
• [w3c/browser-payment-api] Add support for currency system. (#267) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Add support for currency system. (#267) (Saturday, 17 September)
• Re: [w3c/browser-payment-api] Expand Privacy Considerations Section (#228) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Update Introduction to describe actors better (#121) (Friday, 16 September)
• [w3c/browser-payment-api] Remove explanation using "parties" (#266) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Remove explanation using "parties" (#266) (Friday, 16 September)
• Re: [w3c/browser-payment-api] What should happen when invalid data is provided? (#265) (Friday, 16 September)
• Re: [w3c/browser-payment-api] What should happen when invalid data is provided? (#265) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Payment Instrument clarification (#104) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Payment Instrument clarification (#104) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Update the issues links to exclude postponed issues that we don't pla… (#264) (Friday, 16 September)
• [w3c/browser-payment-api] Update the issues links to exclude postponed issues that we don't pla… (#264) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Payment app discovery (#155) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Payment app discovery (#155) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23) (Friday, 16 September)
• Re: [w3c/browser-payment-api] PR #259 and #262 updated the references (#263) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Ensure references are up-to-date (#20) (Friday, 16 September)
• [w3c/browser-payment-api] PR #259 and #262 updated the references (#263) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Update references to "Payment Transaction Message Specification" (#218) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Remove the dependency on PAYMENT-ARCH. (#262) (Friday, 16 September)
• [w3c/browser-payment-api] Remove the dependency on PAYMENT-ARCH. (#262) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Specify UA requirements if “value” field of PaymentCurrencyAmount does not match syntax requirements (#260) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Remove restriction that payment method identifier only appear once (#261) (Friday, 16 September)
• [w3c/browser-payment-api] Remove restriction that payment method identifier only appear once (#261) (Friday, 16 September)
• Re: [w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13) (Friday, 16 September)
• Re: [w3c/browser-payment-api] If a card payment fails, should we support exclusion of that card instrument from matching? (#237) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Unambiguously specify UA requirements for instances that are not valid (#235) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Unambiguously specify UA requirements for instances that are not valid (#235) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Specify UA requirements if “value” field of PaymentCurrencyAmount does not match syntax requirements (#260) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Updated WebIDL and Secure Contexts references (#259) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Normative References (#227) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Normative References (#227) (Friday, 16 September)
• [w3c/browser-payment-api] Updated WebIDL and Secure Contexts references (#259) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Friday, 16 September)
• [w3c/browser-payment-api] Remove careOf field and add note to recipient field. (#258) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Remove careOf field and add note to recipient field. (#258) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Fix typo in PaymentItem definition (#255) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Fix typo in PaymentItem definition (#255) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Add error message that can be provided as part of updateWith (#257) (Friday, 16 September)
• [w3c/browser-payment-api] Add error message that can be provided as part of updateWith (#257) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Cannot use 2119 terms in notes (#240) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Tidied up text in notes. (#254) (Friday, 16 September)
• [w3c/browser-payment-api] Tidied up text in notes. (#254) (Friday, 16 September)
• [w3c/browser-payment-api] Implementations may choose to implement a timeouts (#253) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Implementations may choose to implement a timeouts (#253) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Make response serializable. (#252) (Friday, 16 September)
• [w3c/browser-payment-api] Make response serializable. (#252) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Specify UA requirements if “id” field of PaymentShippingOption is not unique (#243) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Ignore shipping options if there are duplicate IDs. (#249) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Decorate all interfaces with [SecureContext] (#251) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Annotate all interfaces with SecureContext (#241) (Thursday, 15 September)
• [w3c/browser-payment-api] Decorate all interfaces with [SecureContext] (#251) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Clarify that HTTPS is required to use the API (#232) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] ISO4217 is informative. (#250) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Make ISO4217 an informative reference rather than normative (#242) (Thursday, 15 September)
• [w3c/browser-payment-api] ISO4217 is informative. (#250) (Thursday, 15 September)
• [w3c/browser-payment-api] Ignore shipping options if there are duplicate IDs. (#249) (Thursday, 15 September)
• Re: [w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13) (Monday, 12 September)
• Re: [w3c/browser-payment-api] Add note preferring GitHub issues over e-mail. (#245) (Friday, 2 September)
• Re: [w3c/browser-payment-api] Update Respec config. (#246) (Friday, 2 September)
• [w3c/browser-payment-api] Update Respec config. (#246) (Friday, 2 September)
• [w3c/browser-payment-api] Add note preferring GitHub issues over e-mail. (#245) (Friday, 2 September)

Adrian Hope-Bailie

• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Wednesday, 28 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Wednesday, 28 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Sunday, 25 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Sunday, 25 September)
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Friday, 23 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Friday, 23 September)
• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 23 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Friday, 23 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Wednesday, 21 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for Incognito Mode (#230) (Monday, 19 September)
• Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) (Monday, 19 September)
• Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) (Monday, 19 September)
• [w3c/browser-payment-api] Should show() depend on a user action? (#283) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Create failure-handling.md (#248) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13) (Monday, 12 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Implications from non registration (via AHB) (#40) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 12 September)
• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• [w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13) (Tuesday, 6 September)

Andy Staudacher

• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Tuesday, 13 September)
• [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Friday, 2 September)

Anne van Kesteren

• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 13 September)

Arthur Gautier

• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Monday, 19 September)
• [w3c/browser-payment-api] Detecting payment method support (#247) (Saturday, 10 September)

Dave Longley

• Re: [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Tuesday, 27 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 8 September)

ianbjacobs

• Re: [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) (Thursday, 29 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for Incognito Mode (#230) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] add parens for clause (#58) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] change 'promise' to 'Promise' (#57) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] Cleanup wording (#55) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] Fixed grammar (#53) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] Fix run-on sentence (#54) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] Use 'user agent' all the time (#51) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) (Wednesday, 28 September)
• [w3c/webpayments-payment-apps-api] Editorial tweaks after Rouslan edits (#62) (Wednesday, 28 September)
• Re: [w3c/webpayments-payment-apps-api] Native payment app support and others changes. (#46) (Wednesday, 28 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Tuesday, 27 September)
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Tuesday, 27 September)
• Re: [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Tuesday, 27 September)
• Re: [w3c/webpayments-payment-apps-api] Remove duplicate item (#60) (Monday, 26 September)
• Re: [w3c/webpayments-payment-apps-api] Fixed duplicate wording (#61) (Monday, 26 September)
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Monday, 26 September)
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Friday, 23 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for Incognito Mode (#230) (Monday, 19 September)
• Re: [w3c/webpayments-payment-apps-api] Added optionId field to PaymentAppRequestData dictionary (#44) (Saturday, 17 September)
• Re: [w3c/webpayments-payment-apps-api] Removed <a> until I figure out how to get rid of entry from imported glossary (#43) (Saturday, 17 September)
• [w3c/webpayments-payment-apps-api] Removed <a> until I figure out how to get rid of entry from imported glossary (#43) (Saturday, 17 September)
• [w3c/webpayments-payment-apps-api] Editorial fixes (#42) (Saturday, 17 September)
• Re: [w3c/webpayments-payment-apps-api] Editorial fixes (#42) (Saturday, 17 September)
• Re: [w3c/webpayments-payment-apps-api] Proposed text for service-worker-based implementation of payment apps (#41) (Saturday, 17 September)
• Re: [w3c/webpayments-payment-apps-api] How is registration information updated? (#36) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] How is registration information updated? (#36) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] What is the process for rendering the payment app UI (#4) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] What is the process for rendering the payment app UI (#4) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] “Security Error” on different origins (#9) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] “Security Error” on different origins (#9) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] Extending invocation of payment apps with other techniques than HTTP (#10) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] Should the browser pass user data it has collected (email etc) to the payment app? (#13) (Friday, 16 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 15 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Thursday, 15 September)
• Re: [w3c/webpayments-payment-apps-api] What is matching and display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] “Security Error” on different origins (#9) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Require secure contexts for web-based payment apps (#24) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Should we distinguish the identifier for a payment app from the identifier for the app server that processes payments? (#20) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Should we distinguish the identifier for a payment app from the identifier for the app server that processes payments? (#20) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] How is registration information updated? (#36) (Wednesday, 14 September)
• Re: [w3c/webpayments-method-identifiers] Schema.org PaymentMethod as namespace for short strings (#13) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Implications from non registration (via AHB) (#40) (Monday, 12 September)
• [w3c/webpayments-payment-apps-api] Implications from non registration (via AHB) (#40) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) (Monday, 12 September)
• Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) (Monday, 12 September)
• Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) (Monday, 12 September)
• Re: [w3c/browser-payment-api] Should the payment mediator pass all payment method data to the payment app or just relevant data? (#157) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Monday, 12 September)
• [w3c/webpayments-payment-apps-api] Numerous changes based on Rouslan review and issue migration (#39) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• [w3c/webpayments-payment-apps-api] What is display behavior for various scenarios of recommended apps, enabled apps, non-enabled apps, etc.? (#38) (Thursday, 8 September)
• [w3c/webpayments-payment-apps-api] How can a Web Based Payment App cancel the payment flow? (#37) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Should we allow payment providers to issue queries about their installed payment apps (match on origin) (#6) (Thursday, 8 September)
• [w3c/webpayments-payment-apps-api] How is registration information updated? (#36) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Should payment instrument details be included at registration? (#12) (Thursday, 8 September)
• Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23) (Thursday, 8 September)
• Re: [w3c/browser-payment-api] Can the merchant influence order of presentation of payment apps to the user (#23) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)

Jake Archibald

• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 14 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Sunday, 11 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)

Jeff Burdges

• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Monday, 26 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Friday, 23 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Wednesday, 21 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] Should show() depend on a user action? (#283) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Tuesday, 20 September)
• Re: [w3c/browser-payment-api] "Incognito mode" notes (#238) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for User Consent (#229) (Monday, 19 September)
• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Monday, 19 September)

Jinho Bang

• [w3c/browser-payment-api] There might be a conflict between 'shippingType' in PaymentOptions and WebIDL binding. (#271) (Sunday, 18 September)

Manu Sporny

• [w3c/browser-payment-api] PaymentRequest constructor errors should be properly annotated (#290) (Thursday, 29 September)

Marcos Cáceres

• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Tuesday, 13 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 12 September)

mattsaxon

• [w3c/webpayments-payment-apps-api] Versioning (#45) (Tuesday, 20 September)

maxpassion

• Re: [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Tuesday, 27 September)

Michael[tm] Smith

• Re: [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• [w3c/browser-payment-api] Specify UA requirements if “value” field of PaymentCurrencyAmount does not match syntax requirements (#260) (Friday, 16 September)
• [w3c/browser-payment-api] Make UAs throw for invalid monetary amounts (#256) (Friday, 16 September)
• [w3c/browser-payment-api] Fix typo in PaymentItem definition (#255) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Monday, 5 September)

Nick Shearer

• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)

Rouslan Solomakhin

• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Tuesday, 27 September)
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Monday, 26 September)
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Monday, 26 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Friday, 23 September)
• [w3c/webpayments-payment-apps-api] Payment app identifier to manifest filename mapping (#48) (Friday, 23 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Friday, 23 September)
• [w3c/webpayments-payment-apps-api] Native payment app support and others changes. (#46) (Thursday, 22 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 21 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Wednesday, 21 September)
• Re: [w3c/browser-payment-api] What should happen when invalid data is provided? (#265) (Friday, 16 September)
• [w3c/browser-payment-api] What should happen when invalid data is provided? (#265) (Friday, 16 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Sunday, 11 September)
• Re: [w3c/browser-payment-api] Detecting payment method support (#247) (Saturday, 10 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Friday, 9 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• [w3c/webpayments-payment-apps-api] Payment apps and methods, are they the same? (#35) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Thursday, 8 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• [w3c/webpayments-payment-apps-api] Thoughts on the current spec (#34) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)

rvm4

• [w3c/webpayments-methods-card] Update editor list (#15) (Monday, 26 September)
• [w3c/webpayments-method-identifiers] Update editor list (#15) (Monday, 26 September)
• [w3c/browser-payment-api] Update editor list (#288) (Monday, 26 September)
• Re: [w3c/browser-payment-api] Create failure-handling.md (#248) (Wednesday, 14 September)
• [w3c/browser-payment-api] Create failure-handling.md (#248) (Wednesday, 14 September)
• Re: [w3c/browser-payment-api] Add Guidance Text for Incognito Mode (#230) (Thursday, 1 September)

Shane McCarron

• Re: [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Tuesday, 27 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Tuesday, 27 September)
• Re: [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Tuesday, 27 September)
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Tuesday, 27 September)
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Tuesday, 27 September)
• Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Fixed duplicate wording (#61) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Remove duplicate item (#60) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59) (Monday, 26 September)
• Re: [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] add parens for clause (#58) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] change 'promise' to 'Promise' (#57) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Section 6 steps 1-5 seem to avoid selecting a payment option / payment method (#56) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Cleanup wording (#55) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Fix run-on sentence (#54) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Fixed grammar (#53) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Cleaned up text (#52) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Use 'user agent' all the time (#51) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Links to terms and common terminology (#50) (Monday, 26 September)
• [w3c/webpayments-payment-apps-api] Pictures would help! (#49) (Monday, 26 September)
• Re: [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Friday, 23 September)
• Re: [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• [w3c/webpayments-payment-apps-api] Pass along a Transaction ID (#47) (Friday, 23 September)
• [w3c/browser-payment-api] PaymentDetails should include a transaction ID (#287) (Friday, 23 September)
• [w3c/browser-payment-api] notifying the payment app when a payment is complete (#286) (Friday, 23 September)
• [w3c/browser-payment-api] Added clarification about target of details (#282) (Monday, 19 September)
• [w3c/browser-payment-api] Fixed typos (#281) (Monday, 19 September)
• [w3c/browser-payment-api] Remove must in complete() (#280) (Monday, 19 September)
• [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Monday, 19 September)
• [w3c/browser-payment-api] What does it mean to "accept the payment"? (#278) (Monday, 19 September)
• [w3c/browser-payment-api] Add informative reference to CLDR (#277) (Monday, 19 September)
• [w3c/browser-payment-api] Fixed a typo (#276) (Monday, 19 September)
• [w3c/browser-payment-api] Throwing exceptions rather than permitting broken usage (#275) (Monday, 19 September)
• [w3c/browser-payment-api] Examples in the spec (#274) (Monday, 19 September)
• [w3c/browser-payment-api] How can a user agent not accept a payment method? (#273) (Monday, 19 September)
• [w3c/browser-payment-api] Make text active voice, present tense (#272) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Add allowpaymentrequest attribute for iframe support (#268) (Sunday, 18 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)
• [w3c/webpayments-method-identifiers] Add github links (#14) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)

Tab Atkins Jr.

• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 12 September)

Yoav Weiss

• Re: [w3c/browser-payment-api] Fix two minor typos. (#220) (Friday, 23 September)

Yongsta

• [w3c/browser-payment-api] Dynamic Currency Conversion requirements (#289) (Thursday, 29 September)

Zach Koch

• Re: [w3c/browser-payment-api] What if the user refuses to supply a shipping address (#279) (Monday, 19 September)
• Re: [w3c/browser-payment-api] Request to remove 'careOf' field from the PaymentAddress interface (#244) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Tuesday, 13 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Monday, 12 September)
• Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) (Monday, 12 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 12 September)
• Re: [w3c/webpayments-method-identifiers] Why URLs? (#9) (Monday, 12 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)
• Re: [w3c/webpayments-payment-apps-api] The relationship between payment apps and service workers (#33) (Wednesday, 7 September)

Last message date: Thursday, 29 September 2016 15:22:51 UTC