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

Wednesday, 28 February 2018

[w3c/3ds] 3DS response data above and beyond token data (#3) ianbjacobs
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) ianbjacobs
Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) ianbjacobs
Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) Rouslan Solomakhin
Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) Adrian Hope-Bailie
Re: [w3c/payment-request] Feat: add exclusionList for PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Marcos Cáceres
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
Re: [w3c/payment-request] test: link to shipping option test (#688) Marcos Cáceres
Re: [w3c/payment-request] test: link to shipping option test (#688) Matt N.
[w3c/payment-request] test: link to shipping option test (#688) Marcos Cáceres
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres

Tuesday, 27 February 2018

Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) Peter Saint-Andre
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Rouslan Solomakhin
Re: [w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) ianbjacobs
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Add type to PaymentItem (#163) Marcos Cáceres
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Add type to PaymentItem (#163) Marcos Cáceres
Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres

Monday, 26 February 2018

[w3c/payment-handler] Indicate to the payment handler whether the user agent showed payment sheet? (#250) Rouslan Solomakhin

Thursday, 22 February 2018

Re: [w3c/payment-request] Add contact info / support URL to show() method? (#687) Rouslan Solomakhin
Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) ianbjacobs
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
[w3c/payment-request] Add contact info / support URL to show() method? (#687) Peter Saint-Andre

Wednesday, 21 February 2018

Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Peter Saint-Andre
Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Peter Saint-Andre

Tuesday, 20 February 2018

[w3c/payment-request] Unknown currencySystem should throw (#686) Marcos Cáceres
Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres
Re: [w3c/payment-request] Merchant-specified default shipping address (#653) ianbjacobs
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) ianbjacobs
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) ianbjacobs

Friday, 16 February 2018

Re: [w3c/payment-handler] What happens when clearing site data? (#236) Rouslan Solomakhin
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Rouslan Solomakhin
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
Re: [w3c/payment-handler] What happens when clearing site data? (#236) ianbjacobs
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
Re: [w3c/payment-handler] What happens when clearing site data? (#236) ianbjacobs
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Anne van Kesteren
Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres

Thursday, 15 February 2018

Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Ade Bateman
Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres
Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) Peter Saint-Andre
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Peter Saint-Andre
Re: [w3c/webpayments-crypto] Consider Cleartext JWS (#5) Manu Sporny
Re: [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) Manu Sporny
Re: [w3c/3ds] Some high-level issues to discuss (#2) Adrian Hope-Bailie
Re: [w3c/3ds] Some high-level issues to discuss (#2) Adrian Hope-Bailie
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Marcos Cáceres
[w3c/webpayments-crypto] Consider Cleartext JWS (#5) Adrian Hope-Bailie
Re: [w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) Adrian Hope-Bailie
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Jinho Bang
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Jinho Bang
Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) Adrian Hope-Bailie
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Adrian Hope-Bailie
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Domenic Denicola
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Marcos Cáceres
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Matt N.
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Matt N.
Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Matt N.
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Domenic Denicola

Wednesday, 14 February 2018

Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Domenic Denicola
Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) ianbjacobs
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) ianbjacobs
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Rouslan Solomakhin
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Adrian Hope-Bailie

Tuesday, 13 February 2018

Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre

Wednesday, 14 February 2018

Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Marcos Cáceres
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Marcos Cáceres

Tuesday, 13 February 2018

Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre

Wednesday, 14 February 2018

[w3c/payment-handler] interaction with payment methods doesn't appear to be defined (#249) L. David Baron
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres

Tuesday, 13 February 2018

Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) ianbjacobs
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Peter Saint-Andre
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Matt N.
Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) Peter Saint-Andre
Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) Peter Saint-Andre
Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) ianbjacobs
Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) ianbjacobs
Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) ianbjacobs
Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) Peter Saint-Andre
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Marcos Cáceres
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) Marcos Cáceres
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) ianbjacobs
Re: [w3c/payment-request] Define handling of multiple applicable modifiers (#684) ianbjacobs
Re: [w3c/payment-request] Align show() and canMakePayment() language #535 (#682) Marcos Cáceres
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] FR: 3DS (#685) hemanth.hm
Re: [w3c/payment-request] FR: 3DS (#685) Marcos Cáceres
Re: [w3c/payment-request] FR: 3DS (#685) Marcos Cáceres
[w3c/payment-request] FR: 3DS (#685) hemanth.hm
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] Editorial: describe security mitigations #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] Editorial to address #675 (#683) Marcos Cáceres
Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres

Monday, 12 February 2018

[w3c/payment-request] Define handling of multiple applicable modifiers (#684) Matt N.
Re: [w3c/3ds] Some high-level issues to discuss (#2) Peter Saint-Andre
Re: [w3c/3ds] Some high-level issues to discuss (#2) Adam Solove
Re: [w3c/3ds] Some high-level issues to discuss (#2) Peter Saint-Andre
[w3c/payment-request] Editorial to address #675 (#683) ianbjacobs
Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) ianbjacobs
Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) ianbjacobs
[w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) ianbjacobs
Re: [w3c/payment-handler] What happens when clearing site data? (#236) Marcos Cáceres

Friday, 9 February 2018

Re: [w3c/payment-handler] What happens when clearing site data? (#236) Rouslan Solomakhin

Thursday, 8 February 2018

Wednesday, 7 February 2018

Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Marcos Cáceres
Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Marcos Cáceres
Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) Rouslan Solomakhin
Re: [w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Domenic Denicola
[w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Marcos Cáceres
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres
Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) ianbjacobs
Re: [w3c/3ds] Some high-level issues to discuss (#2) Peter Saint-Andre

Tuesday, 6 February 2018

Re: [w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) Rouslan Solomakhin
[w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) ianbjacobs
Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) aestes
Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) clintonrallen
Re: [w3c/3ds] Some high-level issues to discuss (#2) Adrian Hope-Bailie
Re: [w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Rouslan Solomakhin
Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) ianbjacobs
Re: [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) ianbjacobs
Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Marcos Cáceres
Re: [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) Marcos Cáceres
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Marcos Cáceres
[w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres
Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Marcos Cáceres
Re: [w3c/payment-request] Document privacy and security mitigations (#675) Marcos Cáceres
[w3c/webpayments-crypto] Add reference to RFC 7516 (#4) Peter Saint-Andre
[w3c/webpayments-crypto] More detailed encryption workflow (#3) Peter Saint-Andre

Monday, 5 February 2018

[w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) Peter Saint-Andre
Re: [w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1) Peter Saint-Andre
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) ianbjacobs
Re: [w3c/3ds] Some high-level issues to discuss (#2) Peter Saint-Andre
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) Rouslan Solomakhin
Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) ianbjacobs
Re: [w3c/3ds] Some high-level issues to discuss (#2) Adam Solove
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Peter Saint-Andre
Re: [w3c/payment-request] Document privacy and security mitigations (#675) ianbjacobs
Re: [w3c/payment-request] Is paypment request gated behind https? (#658) ianbjacobs
[w3c/payment-handler] work in progress: simplification of various things (#247) Marcos Cáceres
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Gildas Le Louarn
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Marcos Cáceres
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Gildas Le Louarn
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Marcos Cáceres

Sunday, 4 February 2018

Re: [w3c/3ds] Some high-level issues to discuss (#2) ianbjacobs
Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Jinho Bang

Thursday, 1 February 2018

[w3c/3ds] Some high-level issues to discuss (#2) Adam Solove
Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Matt Giuca

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