public-webpayments-specs@w3.org from March 2018 by author

Adam Solove

• [w3c/3ds] Value proposition (#4) (Monday, 26 March)

Adrian Hope-Bailie

• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Monday, 26 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Friday, 23 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Thursday, 22 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 19 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Wednesday, 14 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Tuesday, 13 March)

Anne van Kesteren

• Re: [w3c/payment-handler] Image fetching does not seem to be defined (#237) (Friday, 16 March)
• Re: [w3c/payment-handler] Image fetching does not seem to be defined (#237) (Friday, 16 March)

arisc097

• [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Tuesday, 13 March)

Bart

• Re: [w3c/payment-handler] How would iDeal work? (#251) (Friday, 30 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Friday, 9 March)
• [w3c/payment-handler] How would iDeal work? (#251) (Friday, 9 March)

Denis Ah-Kang

• Re: [w3c/payment-method-basic-card] dummy change to trigger travis (#51) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] dummy change to trigger travis (#51) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] dummy change to trigger travis (#51) (Tuesday, 27 March)
• [w3c/payment-method-basic-card] dummy change to trigger travis (#51) (Tuesday, 27 March)

Domenic Denicola

• Re: [w3c/payment-handler] Use the correct origin serialization (#275) (Wednesday, 28 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) (Friday, 16 March)
• [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) (Friday, 16 March)
• [w3c/payment-handler] Normative MUSTs inside a non-normative note (#268) (Friday, 16 March)
• [w3c/payment-handler] Inconsistent DOMException styles (#267) (Friday, 16 March)
• [w3c/payment-handler] "Dispatch e to global" should link (#266) (Friday, 16 March)
• [w3c/payment-handler] Structured clone usage seems wrong (#265) (Friday, 16 March)
• Re: [w3c/payment-handler] Editorial tweaks to " MethodData Population Algorithm" (#264) (Friday, 16 March)
• [w3c/payment-handler] Editorial tweaks to " MethodData Population Algorithm" (#264) (Friday, 16 March)
• [w3c/payment-handler] Origin definitions are imprecise (#263) (Friday, 16 March)
• [w3c/payment-handler] Move normative requirements on PaymentRequestEvent to the processing model (#262) (Friday, 16 March)
• [w3c/payment-handler] Get rid of normative requirements inside dictionary member definitions (#261) (Friday, 16 March)
• [w3c/payment-handler] Use the correct origin serialization (#260) (Friday, 16 March)
• [w3c/payment-handler] topLevelOrigin is a weird name (#259) (Friday, 16 March)
• [w3c/payment-handler] Integrate better with the payment request spec (#258) (Friday, 16 March)
• [w3c/payment-handler] Do not use "context object" (#257) (Friday, 16 March)
• Re: [w3c/payment-handler] Image fetching does not seem to be defined (#237) (Friday, 16 March)
• [w3c/payment-handler] PaymentInstruments internal storage could be clearer (#256) (Friday, 16 March)
• [w3c/payment-handler] PaymentInstruments is missing values() and entries() (#255) (Friday, 16 March)
• [w3c/payment-handler] Incorrect destructing in example (#254) (Friday, 16 March)
• [w3c/payment-handler] PaymentManager behavior unclear (#253) (Friday, 16 March)
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Wednesday, 14 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Wednesday, 7 March)

Gildas Le Louarn

• Re: [w3c/3ds] Value proposition (#4) (Thursday, 29 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Tuesday, 27 March)
• Re: [w3c/3ds] Value proposition (#4) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Thursday, 15 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Thursday, 15 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Tuesday, 13 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)

gogerald

• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Monday, 26 March)

Henri Sivonen

• Re: [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) (Thursday, 8 March)

ianbjacobs

• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) (Friday, 30 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Thursday, 29 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Thursday, 29 March)
• Re: [w3c/3ds] Value proposition (#4) (Thursday, 29 March)
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Wednesday, 28 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Tuesday, 27 March)
• Re: [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) (Tuesday, 27 March)
• Re: [w3c/payment-handler] Inconsistent DOMException styles (#267) (Monday, 26 March)
• Re: [w3c/payment-handler] Editorial: Fix inconsistent DOMException styles (#271) (Monday, 26 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 26 March)
• [w3c/payment-handler] Review userHint (#273) (Monday, 26 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Friday, 23 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Thursday, 22 March)
• Re: [w3c/payment-request] Decide on currencySystem (#617) (Thursday, 22 March)
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) (Wednesday, 21 March)
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Tuesday, 20 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Monday, 19 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 19 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Wednesday, 14 March)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 5 March)
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Friday, 2 March)
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Thursday, 1 March)
• Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) (Thursday, 1 March)
• Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) (Thursday, 1 March)

Jinho Bang

• Re: [w3c/payment-handler] Move normative requirements on PaymentRequestEvent to the processing model (#262) (Wednesday, 28 March)
• [w3c/payment-handler] Use the correct origin serialization (#275) (Wednesday, 28 March)
• [w3c/payment-handler] chore: tidy up (#274) (Wednesday, 28 March)
• [w3c/payment-handler] Fix incorrect destructing in example (#272) (Sunday, 25 March)
• [w3c/payment-handler] Fix inconsistent DOMException styles (#271) (Sunday, 25 March)

Jun

• [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Wednesday, 28 March)

L. David Baron

• [w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696) (Friday, 23 March)

majaybabu

• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Saturday, 24 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Saturday, 24 March)

majaybabupayment

• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)

Marcos Cáceres

• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Thursday, 29 March)
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) (Thursday, 29 March)
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Thursday, 29 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Wednesday, 28 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• Re: [w3c/payment-handler] Incorrect destructing in example (#254) (Monday, 26 March)
• Re: [w3c/payment-handler] Fix incorrect destructing in example (#272) (Monday, 26 March)
• Re: [w3c/payment-handler] Fix incorrect destructing in example (#272) (Monday, 26 March)
• Re: [w3c/payment-handler] Fix incorrect destructing in example (#272) (Monday, 26 March)
• Re: [w3c/payment-handler] Fix inconsistent DOMException styles (#271) (Monday, 26 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 26 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 26 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• [w3c/payment-request] Add link to SecureContext test (#697) (Friday, 23 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 23 March)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Friday, 23 March)
• Re: [w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696) (Friday, 23 March)
• Re: [w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696) (Friday, 23 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Thursday, 22 March)
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) (Thursday, 22 March)
• [w3c/payment-request] WIP: add paymentmethodchanged event (#695) (Thursday, 22 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Thursday, 22 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Thursday, 22 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Thursday, 22 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Thursday, 22 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Thursday, 22 March)
• Re: [w3c/payment-request] Decide on currencySystem (#617) (Thursday, 22 March)
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) (Wednesday, 21 March)
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) (Wednesday, 21 March)
• Re: [w3c/payment-handler] work in progress: simplification of various things (#247) (Monday, 19 March)
• Re: [w3c/payment-handler] work in progress: simplification of various things (#247) (Monday, 19 March)
• [w3c/payment-request] remove currencySystem member (#694) (Monday, 19 March)
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) (Monday, 19 March)
• [w3c/payment-request] test: show() triggered by user activation (#693) (Monday, 19 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Unknown currencySystem should throw (#686) (Friday, 16 March)
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) (Friday, 16 March)
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Thursday, 15 March)
• Re: [w3c/payment-request] 404 on some tests (#630) (Thursday, 15 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Thursday, 15 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Thursday, 15 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Thursday, 15 March)
• Re: [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) (Thursday, 15 March)
• Re: [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) (Thursday, 15 March)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 15 March)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 15 March)
• Re: [w3c/payment-request] Make Payment Address construction into its own sub algorithm (#643) (Thursday, 15 March)
• Re: [w3c/payment-request] Make Payment Address construction into its own sub algorithm (#643) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 15 March)
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 15 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Wednesday, 14 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Wednesday, 14 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Wednesday, 14 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Wednesday, 14 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Wednesday, 14 March)
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) (Wednesday, 14 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Wednesday, 14 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Wednesday, 14 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Wednesday, 14 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Tuesday, 13 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Tuesday, 13 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Tuesday, 13 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Tuesday, 13 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Tuesday, 13 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Tuesday, 13 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 13 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Tuesday, 13 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• [w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Monday, 12 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Saturday, 10 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 8 March)
• Re: [w3c/payment-request] assure request+response use same shippingAddress (9dd14c3) (Thursday, 8 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 8 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 8 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 8 March)
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) (Thursday, 8 March)
• [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) (Thursday, 8 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Wednesday, 7 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Wednesday, 7 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Tuesday, 6 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Tuesday, 6 March)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 6 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Tuesday, 6 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Tuesday, 6 March)
• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Tuesday, 6 March)
• [w3c/payment-request] editorial: fix links to tests (#691) (Tuesday, 6 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Tuesday, 6 March)
• Re: [w3c/payment-request] add exclusionList for PaymentAddress (Part 1) (#654) (Tuesday, 6 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Friday, 2 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Thursday, 1 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Thursday, 1 March)
• [w3c/payment-request] Add region code (Part 2) (#690) (Thursday, 1 March)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 1 March)
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) (Thursday, 1 March)
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) (Thursday, 1 March)
• [w3c/payment-request] fix: unknown currencySystem throws (#689) (Thursday, 1 March)
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Thursday, 1 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Thursday, 1 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Thursday, 1 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Thursday, 1 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Thursday, 1 March)

Matt N.

• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)

Michael Stillwell

• Re: [w3c/payment-method-basic-card] Brand selection (#49) (Thursday, 15 March)

Peter Saint-Andre

• Re: [w3c/payment-request] Document privacy and security mitigations (#675) (Thursday, 29 March)
• Re: [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) (Tuesday, 27 March)
• [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Monday, 26 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Monday, 26 March)
• Re: [w3c/webpayments-crypto] Add reference to RFC 7516 (#4) (Tuesday, 20 March)
• Re: [w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6) (Thursday, 8 March)
• Re: [w3c/webpayments-crypto] More detailed encryption workflow (#3) (Thursday, 8 March)
• [w3c/webpayments-crypto] Encrypting to multiple parties (#8) (Thursday, 8 March)
• Re: [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) (Thursday, 8 March)
• [w3c/webpayments-crypto] Partial vs. full encryption of response data (#7) (Thursday, 8 March)
• Re: [w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1) (Thursday, 8 March)
• [w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6) (Thursday, 8 March)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Monday, 5 March)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 5 March)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 5 March)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 5 March)
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Friday, 2 March)
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Friday, 2 March)
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Thursday, 1 March)

repalogic

• [w3c/payment-request] support of VAT (#699) (Friday, 30 March)
• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) (Friday, 30 March)

Rouslan Solomakhin

• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Thursday, 29 March)
• Re: [w3c/payment-handler] Remove requestPermission() (#277) (Wednesday, 28 March)
• [w3c/payment-handler] Remove requestPermission() (#277) (Wednesday, 28 March)
• [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Use the correct origin serialization (#260) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) (Wednesday, 28 March)
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) (Wednesday, 28 March)
• Re: [w3c/payment-handler] chore: tidy up (#274) (Wednesday, 28 March)
• Re: [w3c/payment-handler] chore: tidy up (#274) (Wednesday, 28 March)
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) (Wednesday, 28 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Tuesday, 27 March)
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Monday, 26 March)
• [w3c/payment-method-basic-card] Connecting to payment handler. (#50) (Monday, 26 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 26 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 26 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Monday, 26 March)
• Re: [w3c/payment-request] remove currencySystem member (#694) (Saturday, 24 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Saturday, 24 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) (Friday, 23 March)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Friday, 23 March)
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) (Thursday, 22 March)
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) (Thursday, 22 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Thursday, 22 March)
• Re: [w3c/payment-handler] work in progress: simplification of various things (#247) (Monday, 19 March)
• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) (Friday, 16 March)
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) (Friday, 16 March)
• Re: [w3c/payment-handler] Origin definitions are imprecise (#263) (Friday, 16 March)
• Re: [w3c/payment-handler] Normative MUSTs inside a non-normative note (#268) (Friday, 16 March)
• Re: [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] Add regionCode attribute (#690) (Friday, 16 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Thursday, 15 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Wednesday, 14 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Wednesday, 14 March)
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) (Wednesday, 14 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Tuesday, 13 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 13 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 13 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 13 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 13 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Tuesday, 13 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Monday, 12 March)
• Re: [w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252) (Monday, 12 March)
• Re: [w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252) (Monday, 12 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 12 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 12 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 12 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Monday, 12 March)
• Re: [w3c/payment-handler] How would iDeal work? (#251) (Friday, 9 March)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Tuesday, 6 March)
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) (Tuesday, 6 March)
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) (Tuesday, 6 March)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 5 March)
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) (Monday, 5 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Friday, 2 March)
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Thursday, 1 March)
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) (Thursday, 1 March)

Sebsg

• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) (Thursday, 1 March)

Simon Pieters

• Re: [w3c/payment-request] editorial: fix links to tests (#691) (Tuesday, 6 March)

Last message date: Friday, 30 March 2018 12:07:41 UTC