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

[w3c/3ds] 3DS response data above and beyond token data (#3) ianbjacobs (Wednesday, 28 February)

Re: [w3c/payment-request] Feat: add exclusionList for PaymentAddress (#654) Marcos Cáceres (Wednesday, 28 February)

[w3c/payment-request] test: link to shipping option test (#688) Marcos Cáceres (Wednesday, 28 February)

Re: [w3c/payment-request] Add type to PaymentItem (#163) Marcos Cáceres (Tuesday, 27 February)

Re: [w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654) Marcos Cáceres (Tuesday, 27 February)

Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres (Tuesday, 27 February)

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

Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres (Thursday, 22 February)

[w3c/payment-request] Add contact info / support URL to show() method? (#687) Peter Saint-Andre (Thursday, 22 February)

[w3c/payment-request] Unknown currencySystem should throw (#686) Marcos Cáceres (Tuesday, 20 February)

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

Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres (Thursday, 15 February)

Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres (Thursday, 15 February)

Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres (Thursday, 15 February)

[w3c/webpayments-crypto] Consider Cleartext JWS (#5) Adrian Hope-Bailie (Thursday, 15 February)

Re: [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) ianbjacobs (Wednesday, 14 February)

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

Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) ianbjacobs (Tuesday, 13 February)

Re: [w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16) Peter Saint-Andre (Tuesday, 13 February)

[w3c/payment-request] FR: 3DS (#685) hemanth.hm (Tuesday, 13 February)

Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres (Tuesday, 13 February)

[w3c/payment-request] Define handling of multiple applicable modifiers (#684) Matt N. (Monday, 12 February)

[w3c/payment-request] Editorial to address #675 (#683) ianbjacobs (Monday, 12 February)

Re: [w3c/payment-request] canMakePayment() needs to match .show() (#535) ianbjacobs (Monday, 12 February)

Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) ianbjacobs (Monday, 12 February)

[w3c/payment-request] Align show() and canMakePayment() language #535 (#682) ianbjacobs (Monday, 12 February)

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

Re: [w3c/webpayments-methods-tokenization] Payment Method declaration may show duplicate card descriptions (#9) ianbjacobs (Thursday, 8 February)

Re: [w3c/webpayments-methods-tokenization] Need for environment parameter (#19) ianbjacobs (Thursday, 8 February)

Re: [w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21) ianbjacobs (Thursday, 8 February)

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

[w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681) Marcos Cáceres (Wednesday, 7 February)

[w3c/payment-handler] Use payment method manifest for registration-time validation? (#248) ianbjacobs (Tuesday, 6 February)

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

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

Re: [w3c/payment-handler] Only allows instrument.set() in active service worker (#224) Marcos Cáceres (Tuesday, 6 February)

Re: [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) Marcos Cáceres (Tuesday, 6 February)

[w3c/payment-request] Guidance on shipping options (mostly for devs) (#680) Marcos Cáceres (Tuesday, 6 February)

[w3c/webpayments-crypto] Add reference to RFC 7516 (#4) Peter Saint-Andre (Tuesday, 6 February)

[w3c/webpayments-crypto] More detailed encryption workflow (#3) Peter Saint-Andre (Tuesday, 6 February)

[w3c/webpayments-crypto] Required or recommended encryption algorithms (#2) Peter Saint-Andre (Monday, 5 February)

Re: [w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1) Peter Saint-Andre (Monday, 5 February)

Re: [w3c/payment-request] Document privacy and security mitigations (#675) ianbjacobs (Monday, 5 February)

Re: [w3c/payment-request] Is paypment request gated behind https? (#658) ianbjacobs (Monday, 5 February)

[w3c/payment-handler] work in progress: simplification of various things (#247) Marcos Cáceres (Monday, 5 February)

Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Jinho Bang (Sunday, 4 February)

[w3c/3ds] Some high-level issues to discuss (#2) Adam Solove (Thursday, 1 February)

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

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