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

[w3c/3ds] 3DS 2.0 specificities by schema (#1)

[w3c/3ds] 3DS response data above and beyond token data (#3)

[w3c/3ds] Some high-level issues to discuss (#2)

[w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245)

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

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

[w3c/payment-handler] Only allows instrument.set() in active service worker (#224)

[w3c/payment-handler] PaymentInstruments .set() and icons (#233)

[w3c/payment-handler] Proposal: Remove requestPermission() (#246)

[w3c/payment-handler] Use payment method manifest for registration-time validation? (#248)

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

[w3c/payment-handler] work in progress: simplification of various things (#247)

[w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476)

[w3c/payment-request] Add contact info / support URL to show() method? (#687)

[w3c/payment-request] Add localization hint for payment sheet (#656)

[w3c/payment-request] Add type to PaymentItem (#163)

[w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645)

[w3c/payment-request] Align show() and canMakePayment() language #535 (#682)

[w3c/payment-request] Allow locale to be specified by the developer. (#650)

[w3c/payment-request] canMakePayment() needs to match .show() (#535)

[w3c/payment-request] Define handling of multiple applicable modifiers (#684)

[w3c/payment-request] Document privacy and security mitigations (#675)

[w3c/payment-request] Editorial to address #675 (#683)

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

[w3c/payment-request] Feat: add constructor to PaymentAddress (#654)

[w3c/payment-request] Feat: add exclusionList for PaymentAddress (#654)

[w3c/payment-request] Feat: add regionCode and exclusionList to PaymentAddress (#654)

[w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666)

[w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672)

[w3c/payment-request] FR: 3DS (#685)

[w3c/payment-request] Guidance on shipping options (mostly for devs) (#680)

[w3c/payment-request] Is paypment request gated behind https? (#658)

[w3c/payment-request] Merchant-specified default shipping address (#653)

[w3c/payment-request] PaymentShippingOption as a subclass of DisplayItem (#681)

[w3c/payment-request] Standardize phone number format (#652)

[w3c/payment-request] test: link to shipping option test (#688)

[w3c/payment-request] Unknown currencySystem should throw (#686)

[w3c/webpayments-crypto] Add reference to RFC 7516 (#4)

[w3c/webpayments-crypto] Consider Cleartext JWS (#5)

[w3c/webpayments-crypto] More detailed encryption workflow (#3)

[w3c/webpayments-crypto] Required or recommended encryption algorithms (#2)

[w3c/webpayments-crypto] What public key formats are acceptable, and any constraints? (#1)

[w3c/webpayments-methods-tokenization] Need for environment parameter (#19)

[w3c/webpayments-methods-tokenization] Payment Method declaration may show duplicate card descriptions (#9)

[w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34)

[w3c/webpayments-methods-tokenization] Token properties? (#25)

[w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28)

[w3c/webpayments-methods-tokenization] What to do if tokenized data looks like basic card data? (#21)

[w3c/webpayments-methods-tokenization] Where does tokenisation occur in the the flow - and do we care (#16)

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