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

Adam Solove

• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Monday, 12 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Thursday, 8 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Thursday, 8 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Monday, 5 February)
• [w3c/3ds] Some high-level issues to discuss (#2) (Thursday, 1 February)

Ade Bateman

• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Thursday, 15 February)

Adrian Hope-Bailie

• Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) (Wednesday, 28 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Thursday, 15 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Thursday, 15 February)
• [w3c/webpayments-crypto] Consider Cleartext JWS (#5) (Thursday, 15 February)
• Re: [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) (Thursday, 15 February)
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 14 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Tuesday, 6 February)

aestes

• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Tuesday, 6 February)

Anne van Kesteren

• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)

clintonrallen

• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Tuesday, 6 February)

Domenic Denicola

• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Thursday, 15 February)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Thursday, 15 February)
• Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) (Wednesday, 14 February)
• Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) (Wednesday, 7 February)

Eiji Kitamura

• Re: [w3c/payment-handler] PaymentInstruments .set() and icons (#233) (Thursday, 8 February)

Gildas Le Louarn

• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 5 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 5 February)

hemanth.hm

• Re: [w3c/payment-request] FR: 3DS (#685) (Tuesday, 13 February)
• [w3c/payment-request] FR: 3DS (#685) (Tuesday, 13 February)

ianbjacobs

• [w3c/3ds] 3DS response data above and beyond token data (#3) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 28 February)
• Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) (Wednesday, 28 February)
• Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Thursday, 22 February)
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 20 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 20 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) (Wednesday, 14 February)
• Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) (Wednesday, 14 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) (Tuesday, 13 February)
• Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) (Tuesday, 13 February)
• Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) (Tuesday, 13 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Tuesday, 13 February)
• [w3c/payment-request] Editorial to address #675 (#683) (Monday, 12 February)
• Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) (Monday, 12 February)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 12 February)
• [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Monday, 12 February)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Monday, 12 February)
• Re: [w3c/webpayments-methods-tokenization] Payment Method declaration may show duplicate card descriptions (#9) (Thursday, 8 February)
• Re: [w3c/webpayments-methods-tokenization] Payment Method declaration may show duplicate card descriptions (#9) (Thursday, 8 February)
• Re: [w3c/webpayments-methods-tokenization] Need for environment parameter (#19) (Thursday, 8 February)
• Re: [w3c/webpayments-methods-tokenization] Need for environment parameter (#19) (Thursday, 8 February)
• Re: [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21) (Thursday, 8 February)
• Re: [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21) (Thursday, 8 February)
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Wednesday, 7 February)
• [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Tuesday, 6 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 6 February)
• Re: [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) (Tuesday, 6 February)
• Re: [w3c/payment-request] Is paypment request gated behind https? (#658) (Monday, 5 February)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Monday, 5 February)
• Re: [w3c/payment-request] Document privacy and security mitigations (#675) (Monday, 5 February)
• Re: [w3c/payment-request] Is paypment request gated behind https? (#658) (Monday, 5 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Sunday, 4 February)

Jinho Bang

• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Thursday, 15 February)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Thursday, 15 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Sunday, 4 February)

L. David Baron

• [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) (Wednesday, 14 February)

Manu Sporny

• Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) (Thursday, 15 February)
• Re: [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) (Thursday, 15 February)

Marcos Cáceres

• Re: [w3c/payment-request] Feat: add exclusionList for PaymentAddress (#654) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 28 February)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 28 February)
• Re: [w3c/payment-request] test: link to shipping option test (#688) (Wednesday, 28 February)
• [w3c/payment-request] test: link to shipping option test (#688) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Tuesday, 27 February)
• Re: [w3c/payment-request] Add type to PaymentItem (#163) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Tuesday, 27 February)
• Re: [w3c/payment-request] Add type to PaymentItem (#163) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Tuesday, 27 February)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Tuesday, 27 February)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Tuesday, 27 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Thursday, 22 February)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Thursday, 22 February)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 21 February)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 21 February)
• [w3c/payment-request] Unknown currencySystem should throw (#686) (Tuesday, 20 February)
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 20 February)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Friday, 16 February)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Thursday, 15 February)
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) (Thursday, 15 February)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Thursday, 15 February)
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) (Thursday, 15 February)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Thursday, 15 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Thursday, 15 February)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Thursday, 15 February)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 14 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 14 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Wednesday, 14 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Tuesday, 13 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Tuesday, 13 February)
• Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] FR: 3DS (#685) (Tuesday, 13 February)
• Re: [w3c/payment-request] FR: 3DS (#685) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial to address #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Tuesday, 13 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Monday, 12 February)
• Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) (Wednesday, 7 February)
• Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) (Wednesday, 7 February)
• [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) (Wednesday, 7 February)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Wednesday, 7 February)
• Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) (Tuesday, 6 February)
• Re: [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) (Tuesday, 6 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 6 February)
• [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Tuesday, 6 February)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Tuesday, 6 February)
• Re: [w3c/payment-request] Document privacy and security mitigations (#675) (Tuesday, 6 February)
• [w3c/payment-handler] work in progress: simplification of various things (#247) (Monday, 5 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 5 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 5 February)

Matt Giuca

• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Thursday, 1 February)

Matt N.

• Re: [w3c/payment-request] test: link to shipping option test (#688) (Wednesday, 28 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Thursday, 15 February)
• Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Tuesday, 13 February)
• [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Monday, 12 February)

Peter Saint-Andre

• Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) (Tuesday, 27 February)
• [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Thursday, 22 February)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 21 February)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 21 February)
• Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) (Tuesday, 13 February)
• Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) (Tuesday, 13 February)
• Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) (Tuesday, 13 February)
• Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) (Tuesday, 13 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Monday, 12 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Monday, 12 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Wednesday, 7 February)
• [w3c/webpayments-crypto] Add reference to RFC 7516 (#4) (Tuesday, 6 February)
• [w3c/webpayments-crypto] More detailed encryption workflow (#3) (Tuesday, 6 February)
• [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) (Monday, 5 February)
• Re: [w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1) (Monday, 5 February)
• Re: [w3c/3ds] Some high-level issues to discuss (#2) (Monday, 5 February)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 5 February)

Rouslan Solomakhin

• Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) (Wednesday, 28 February)
• Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) (Tuesday, 27 February)
• [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) (Monday, 26 February)
• Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) (Thursday, 22 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 16 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Thursday, 15 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 14 February)
• Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) (Wednesday, 14 February)
• Re: [w3c/payment-handler] What happens when clearing site data? (#236) (Friday, 9 February)
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Wednesday, 7 February)
• Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) (Tuesday, 6 February)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Tuesday, 6 February)
• Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) (Tuesday, 6 February)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Tuesday, 6 February)
• Re: [w3c/payment-request] Is paypment request gated behind https? (#658) (Monday, 5 February)

Last message date: Wednesday, 28 February 2018 16:22:35 UTC