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

Friday, 30 March 2018

• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) ianbjacobs
• [w3c/payment-request] support of VAT (#699) repalogic
• Re: [w3c/payment-request] A distinct invoice address should be supported (#550) repalogic
• Re: [w3c/payment-handler] How would iDeal work? (#251) Bart

Thursday, 29 March 2018

• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) ianbjacobs
• Re: [w3c/payment-handler] How would iDeal work? (#251) ianbjacobs
• Re: [w3c/payment-request] Document privacy and security mitigations (#675) Peter Saint-Andre
• Re: [w3c/3ds] Value proposition (#4) Gildas Le Louarn
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Marcos Cáceres
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Marcos Cáceres
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Marcos Cáceres
• Re: [w3c/3ds] Value proposition (#4) ianbjacobs
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Rouslan Solomakhin

Wednesday, 28 March 2018

• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) ianbjacobs
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) ianbjacobs
• Re: [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) ianbjacobs
• Re: [w3c/payment-handler] Remove requestPermission() (#277) Rouslan Solomakhin
• [w3c/payment-handler] Remove requestPermission() (#277) Rouslan Solomakhin
• [w3c/payment-handler] Replace 'enabledMethods' array with 'method' string. (#276) Rouslan Solomakhin
• Re: [w3c/payment-handler] Move normative requirements on PaymentRequestEvent to the processing model (#262) Jinho Bang
• Re: [w3c/payment-handler] Use the correct origin serialization (#260) Rouslan Solomakhin
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) Rouslan Solomakhin
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) Rouslan Solomakhin
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) Domenic Denicola
• Re: [w3c/payment-handler] Use the correct origin serialization (#275) Rouslan Solomakhin
• [w3c/payment-handler] Use the correct origin serialization (#275) Jinho Bang
• [w3c/payment-handler] chore: tidy up (#274) Jinho Bang
• Re: [w3c/payment-handler] chore: tidy up (#274) Rouslan Solomakhin
• Re: [w3c/payment-handler] chore: tidy up (#274) Rouslan Solomakhin
• Re: [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Rouslan Solomakhin
• [w3c/payment-request] Disable Payment Request API in CSP/iframe sandbox (#698) Jun
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) ianbjacobs
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres

Tuesday, 27 March 2018

• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) Peter Saint-Andre
• Re: [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) ianbjacobs
• [w3c/webpayments-methods-tokenization] Inconsistencies in response example (#37) Peter Saint-Andre
• Re: [w3c/payment-handler] How would iDeal work? (#251) Gildas Le Louarn
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/3ds] Value proposition (#4) Gildas Le Louarn
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Adrian Hope-Bailie
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Adrian Hope-Bailie
• Re: [w3c/payment-method-basic-card] dummy change to trigger travis (#51) Denis Ah-Kang
• Re: [w3c/payment-method-basic-card] dummy change to trigger travis (#51) Denis Ah-Kang
• Re: [w3c/payment-method-basic-card] dummy change to trigger travis (#51) Denis Ah-Kang
• [w3c/payment-method-basic-card] dummy change to trigger travis (#51) Denis Ah-Kang
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Marcos Cáceres

Monday, 26 March 2018

• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Peter Saint-Andre
• [w3c/payment-method-basic-card] Connecting to payment handler. (#50) Rouslan Solomakhin
• [w3c/3ds] Value proposition (#4) Adam Solove
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) gogerald
• Re: [w3c/payment-request] remove currencySystem member (#694) Peter Saint-Andre
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Adrian Hope-Bailie
• Re: [w3c/payment-request] remove currencySystem member (#694) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Inconsistent DOMException styles (#267) ianbjacobs
• Re: [w3c/payment-handler] Editorial: Fix inconsistent DOMException styles (#271) ianbjacobs
• Re: [w3c/payment-handler] Incorrect destructing in example (#254) Marcos Cáceres
• Re: [w3c/payment-handler] Fix incorrect destructing in example (#272) Marcos Cáceres
• Re: [w3c/payment-handler] Fix incorrect destructing in example (#272) Marcos Cáceres
• Re: [w3c/payment-handler] Fix incorrect destructing in example (#272) Marcos Cáceres
• Re: [w3c/payment-handler] Fix inconsistent DOMException styles (#271) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) ianbjacobs
• [w3c/payment-handler] Review userHint (#273) ianbjacobs
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Domenic Denicola
• Re: [w3c/payment-request] remove currencySystem member (#694) Adrian Hope-Bailie
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres

Sunday, 25 March 2018

• [w3c/payment-handler] Fix incorrect destructing in example (#272) Jinho Bang
• [w3c/payment-handler] Fix inconsistent DOMException styles (#271) Jinho Bang

Saturday, 24 March 2018

• Re: [w3c/payment-request] remove currencySystem member (#694) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) majaybabu
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) majaybabu

Friday, 23 March 2018

• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Adrian Hope-Bailie
• Re: [w3c/payment-request] remove currencySystem member (#694) Adrian Hope-Bailie
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) majaybabupayment
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) Rouslan Solomakhin
• Re: [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) ianbjacobs
• [w3c/payment-handler] Payment manifest supporting multiple payments apps from different providers? (#270) arisc097
• [w3c/payment-request] Add link to SecureContext test (#697) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Rouslan Solomakhin
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Marcos Cáceres
• Re: [w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696) Marcos Cáceres
• Re: [w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696) Marcos Cáceres
• [w3c/payment-request] PaymentOptions.shippingType definition should link to PaymentShippingType, not to itself (#696) L. David Baron

Thursday, 22 March 2018

• Re: [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] remove currencySystem member (#694) ianbjacobs
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Rouslan Solomakhin
• Re: [w3c/payment-request] remove currencySystem member (#694) Adrian Hope-Bailie
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Marcos Cáceres
• Re: [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Rouslan Solomakhin
• Re: [w3c/payment-request] Add regionCode attribute (#690) Rouslan Solomakhin
• Re: [w3c/payment-request] Decide on currencySystem (#617) ianbjacobs
• [w3c/payment-request] WIP: add paymentmethodchanged event (#695) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Decide on currencySystem (#617) Marcos Cáceres

Wednesday, 21 March 2018

• Re: [w3c/payment-request] test: show() triggered by user activation (#693) Marcos Cáceres
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) ianbjacobs
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) Marcos Cáceres

Tuesday, 20 March 2018

• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) ianbjacobs
• Re: [w3c/webpayments-crypto] Add reference to RFC 7516 (#4) Peter Saint-Andre

Monday, 19 March 2018

• Re: [w3c/payment-handler] How would iDeal work? (#251) ianbjacobs
• Re: [w3c/payment-method-basic-card] Brand selection (#49) ianbjacobs
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Adrian Hope-Bailie
• Re: [w3c/payment-handler] work in progress: simplification of various things (#247) Marcos Cáceres
• Re: [w3c/payment-handler] work in progress: simplification of various things (#247) Marcos Cáceres
• Re: [w3c/payment-handler] work in progress: simplification of various things (#247) Rouslan Solomakhin
• [w3c/payment-request] remove currencySystem member (#694) Marcos Cáceres
• Re: [w3c/payment-request] test: show() triggered by user activation (#693) Marcos Cáceres
• [w3c/payment-request] test: show() triggered by user activation (#693) Marcos Cáceres

Friday, 16 March 2018

• Re: [w3c/payment-handler] PaymentManager behavior unclear (#253) Rouslan Solomakhin
• Re: [w3c/payment-handler] topLevelOrigin is a weird name (#259) Rouslan Solomakhin
• Re: [w3c/payment-handler] Origin definitions are imprecise (#263) Rouslan Solomakhin
• Re: [w3c/payment-handler] Normative MUSTs inside a non-normative note (#268) Rouslan Solomakhin
• Re: [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) Rouslan Solomakhin
• Re: [w3c/payment-request] Add regionCode attribute (#690) Rouslan Solomakhin
• Re: [w3c/payment-request] Add regionCode attribute (#690) Rouslan Solomakhin
• Re: [w3c/payment-handler] Image fetching does not seem to be defined (#237) Anne van Kesteren
• Re: [w3c/payment-handler] Image fetching does not seem to be defined (#237) Anne van Kesteren
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Matt N.
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Matt N.
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Matt N.
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Domenic Denicola
• Re: [w3c/payment-request] Add regionCode attribute (#690) Domenic Denicola
• Re: [w3c/payment-request] Unknown currencySystem should throw (#686) Marcos Cáceres
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) Marcos Cáceres
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) Domenic Denicola
• Re: [w3c/payment-request] Add regionCode attribute (#690) Marcos Cáceres
• [w3c/payment-handler] Consider explaining the connection with payment method manifests sooner (#269) Domenic Denicola
• [w3c/payment-handler] Normative MUSTs inside a non-normative note (#268) Domenic Denicola
• [w3c/payment-handler] Inconsistent DOMException styles (#267) Domenic Denicola
• [w3c/payment-handler] "Dispatch e to global" should link (#266) Domenic Denicola
• [w3c/payment-handler] Structured clone usage seems wrong (#265) Domenic Denicola
• Re: [w3c/payment-handler] Editorial tweaks to " MethodData Population Algorithm" (#264) Domenic Denicola
• [w3c/payment-handler] Editorial tweaks to " MethodData Population Algorithm" (#264) Domenic Denicola
• [w3c/payment-handler] Origin definitions are imprecise (#263) Domenic Denicola
• [w3c/payment-handler] Move normative requirements on PaymentRequestEvent to the processing model (#262) Domenic Denicola
• [w3c/payment-handler] Get rid of normative requirements inside dictionary member definitions (#261) Domenic Denicola
• [w3c/payment-handler] Use the correct origin serialization (#260) Domenic Denicola
• [w3c/payment-handler] topLevelOrigin is a weird name (#259) Domenic Denicola
• [w3c/payment-handler] Integrate better with the payment request spec (#258) Domenic Denicola
• [w3c/payment-handler] Do not use "context object" (#257) Domenic Denicola
• Re: [w3c/payment-handler] Image fetching does not seem to be defined (#237) Domenic Denicola
• [w3c/payment-handler] PaymentInstruments internal storage could be clearer (#256) Domenic Denicola
• [w3c/payment-handler] PaymentInstruments is missing values() and entries() (#255) Domenic Denicola
• [w3c/payment-handler] Incorrect destructing in example (#254) Domenic Denicola
• [w3c/payment-handler] PaymentManager behavior unclear (#253) Domenic Denicola
• Re: [w3c/payment-handler] ImageObjects can now reference ImageResource (#238) Domenic Denicola

Thursday, 15 March 2018

• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Michael Stillwell
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-request] 404 on some tests (#630) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Domenic Denicola
• Re: [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) Marcos Cáceres
• Re: [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) Marcos Cáceres
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Marcos Cáceres
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Marcos Cáceres
• Re: [w3c/payment-request] Make Payment Address construction into its own sub algorithm (#643) Marcos Cáceres
• Re: [w3c/payment-request] Make Payment Address construction into its own sub algorithm (#643) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Domenic Denicola
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres

Wednesday, 14 March 2018

• Re: [w3c/payment-handler] How would iDeal work? (#251) Adrian Hope-Bailie
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) ianbjacobs
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Domenic Denicola
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] Require user gesture when `.show()` is called (#651) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres

Tuesday, 13 March 2018

• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-handler] How would iDeal work? (#251) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Adrian Hope-Bailie
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-handler] How would iDeal work? (#251) arisc097

Monday, 12 March 2018

• Re: [w3c/payment-handler] How would iDeal work? (#251) Rouslan Solomakhin
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252) Rouslan Solomakhin
• Re: [w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• [w3c/payment-handler] chore(PULL_REQUEST_TEMPLATE): add pull request template (#252) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn
• Re: [w3c/payment-method-basic-card] Brand selection (#49) Marcos Cáceres
• [w3c/payment-method-basic-card] Brand selection (#49) Gildas Le Louarn

Saturday, 10 March 2018

• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres

Friday, 9 March 2018

• Re: [w3c/payment-handler] How would iDeal work? (#251) Bart
• Re: [w3c/payment-handler] How would iDeal work? (#251) Rouslan Solomakhin
• [w3c/payment-handler] How would iDeal work? (#251) Bart

Thursday, 8 March 2018

• Re: [w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6) Peter Saint-Andre
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] assure request+response use same shippingAddress (9dd14c3) Marcos Cáceres
• Re: [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) Henri Sivonen
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Marcos Cáceres
• [w3c/payment-request] When "pay" happens, PaymentAddress request and response should match. (#692) Marcos Cáceres
• Re: [w3c/webpayments-crypto] More detailed encryption workflow (#3) Peter Saint-Andre
• [w3c/webpayments-crypto] Encrypting to multiple parties (#8) Peter Saint-Andre
• Re: [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) Peter Saint-Andre
• [w3c/webpayments-crypto] Partial vs. full encryption of response data (#7) Peter Saint-Andre
• Re: [w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1) Peter Saint-Andre
• [w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6) Peter Saint-Andre

Wednesday, 7 March 2018

• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Domenic Denicola
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres

Tuesday, 6 March 2018

• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Rouslan Solomakhin
• Re: [w3c/payment-handler] Add CanMakePaymentEvent. (#170) Rouslan Solomakhin
• Re: [w3c/payment-request] Describe how to implement PaymentAddress.languageCode (#608) Rouslan Solomakhin
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Simon Pieters
• Re: [w3c/payment-request] add redactList for PaymentAddress (Part 1) (#654) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• [w3c/payment-request] editorial: fix links to tests (#691) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Marcos Cáceres
• Re: [w3c/payment-request] add exclusionList for PaymentAddress (Part 1) (#654) Marcos Cáceres

Monday, 5 March 2018

• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) ianbjacobs
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Peter Saint-Andre
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Peter Saint-Andre
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Rouslan Solomakhin
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Peter Saint-Andre
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Rouslan Solomakhin
• Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27) Peter Saint-Andre

Friday, 2 March 2018

• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Peter Saint-Andre
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) ianbjacobs
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) Peter Saint-Andre
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Rouslan Solomakhin
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Marcos Cáceres

Thursday, 1 March 2018

• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) Peter Saint-Andre
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) ianbjacobs
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Sebsg
• Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) ianbjacobs
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Rouslan Solomakhin
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Rouslan Solomakhin
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Marcos Cáceres
• Re: [w3c/payment-request] Add regionCode attribute (Part 2) (#690) Marcos Cáceres
• [w3c/payment-request] Add region code (Part 2) (#690) Marcos Cáceres
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Marcos Cáceres
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) Marcos Cáceres
• Re: [w3c/payment-request] fix: unknown currencySystem throws (#689) Marcos Cáceres
• [w3c/payment-request] fix: unknown currencySystem throws (#689) Marcos Cáceres
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres
• Re: [w3c/payment-request] show() must be triggered by user activation (#655) Marcos Cáceres

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