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

[w3c/3ds] Change `requestLevel` in response to sheet data changes (#6)

[w3c/3ds] User preference for strong authentication (#7)

[w3c/payment-handler] Just in time installation of Payment Handler (#303)

[w3c/payment-handler] Simplifying functional event handling (#305)

[w3c/payment-method-basic-card] Signaling payment handler details errors (#57)

[w3c/payment-request] [NewObject] annotation (#743)

[w3c/payment-request] Add equivalent of applepaypaymentmethodchanged (#662)

[w3c/payment-request] Add explicit extension point to matching algo (#470)

[w3c/payment-request] Add generic `error` member for `.retry()` (#729)

[w3c/payment-request] add paymentmethodchange event (#695)

[w3c/payment-request] Add PaymentResponse.onpayerdetailchange (#724)

[w3c/payment-request] Add PaymentResponse.prototype.onpayerdetailchange (#724)

[w3c/payment-request] Add secure origin section to security considerations (#742)

[w3c/payment-request] Added canMakePayment() section to privacy considerations (#739)

[w3c/payment-request] Added information about redactList to privacy consideration (#738)

[w3c/payment-request] Always requiring CVV? (#730)

[w3c/payment-request] chore(PULL_REQUEST_TEMPLATE.md): note impact on payment handler (#722)

[w3c/payment-request] Define PaymentResponse.prototype.retry() method (#720)

[w3c/payment-request] Define PaymentResponse.retry() method (#715)

[w3c/payment-request] define PaymentResponse.retry() method (#720)

[w3c/payment-request] Do we need "doc is fully active" checks on `response.complete()`? (#731)

[w3c/payment-request] document show() protections under security considerations (#740)

[w3c/payment-request] Drop `*Error` from error things (#736)

[w3c/payment-request] editorial: add retry() state (#734)

[w3c/payment-request] editorial: add retry() to state diagram (#734)

[w3c/payment-request] Editorial: complete() returns rejected promise (#732)

[w3c/payment-request] Editorial: use internal slots (#726)

[w3c/payment-request] EventTarget is used by never linked to (#744)

[w3c/payment-request] Fine grained error recovery for fields (#647)

[w3c/payment-request] fine-grained errors reporting for PaymentAddress (#712)

[w3c/payment-request] Fix a small bug in `abort`'s error handling. (#733)

[w3c/payment-request] fix: complete() returns rejected promise (#732)

[w3c/payment-request] Follow up on APA Comments on Web Payments FPWDs (#735)

[w3c/payment-request] iframe usage security subsection (#741)

[w3c/payment-request] payment modifier brings error (#637)

[w3c/payment-request] Response timeout could leave page/user in confused state. (#737)

[w3c/payment-request] Retry request abort the update (#723)

[w3c/payment-request] Retrying a payment (#705)

[w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)

[w3c/payment-request] Signaling payment handler details errors (#727)

[w3c/payment-request] Teach retry() about payerErrors (#716)

[w3c/payment-request] teach retry() about payerErrors (#721)

[w3c/payment-request] Update state diagram to include retry() (#728)

[w3c/payment-request] Update test-plan.md after web-platform-tests repo move (#725)

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

[w3c/webpayments-crypto] Fixes for key definitions and examples (#14)

[w3c/webpayments-crypto] Machine-readable identification of sensitive data to be encrypted? (#11)

[w3c/webpayments-crypto] Mapping between claims and response data elements (#13)

[w3c/webpayments-crypto] Partial vs. full encryption of response data (#7)

[w3c/webpayments-crypto] restructured into steps performed by payment handler and merchant (#16)

[w3c/webpayments-crypto] Should we allow keys or only certificates? (#15)

[w3c/webpayments-crypto] Where to communicate responseEncryptionKey (#6)

[w3c/webpayments-methods-tokenization] Add PAR to response data? (#38)

[w3c/webpayments-methods-tokenization] How are future card on file transactions supported through dynamic data? (#44)

[w3c/webpayments-methods-tokenization] How/whether to handle token sharing use cases (#41)

[w3c/webpayments-methods-tokenization] Is billing address required? (#40)

[w3c/webpayments-methods-tokenization] Is cardholderName required? (#42)

[w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17)

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

[w3c/webpayments-methods-tokenization] What are various errors related to keys? (#43)

Last message date: Saturday, 30 June 2018 16:42:21 UTC