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

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

[w3c/payment-handler] Add support for PaymentValidationErrors (#306)

[w3c/payment-handler] ImageObjects can now reference ImageResource (#238)

[w3c/payment-handler] Need normative text for checking the origin of the SW scope against "supported_origins". (#309)

[w3c/payment-handler] Payment Handler window `.focused` field (#307)

[w3c/payment-handler] What mechanism allows enforcing payment handler authenticity? (#308)

[w3c/payment-handler] What should payees validate? (#310)

[w3c/payment-method-basic-card] add BasicCardErrorFields (#58)

[w3c/payment-method-id] What can I do with a URL-based payment method identifier? (#52)

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

[w3c/payment-request] Add [NewObject] annotations to methods (#746)

[w3c/payment-request] Add ability to request payer's address (#749)

[w3c/payment-request] Add error member to PaymentValidationErrors (#747)

[w3c/payment-request] Add error reporting for payer address (#750)

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

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

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

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

[w3c/payment-request] Add support for merchant validation (#646)

[w3c/payment-request] Add support for merchant validation (#751)

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

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

[w3c/payment-request] Check doc fully active during response.complete() (#748)

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

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

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

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

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

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

[w3c/payment-request] Drop prefixes, suffixes from error field members (#745)

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

[w3c/payment-request] Editorial: fix grammatical error (#756)

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

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

[w3c/payment-request] Fix grammatical error (#756)

[w3c/payment-request] fix: state was not closed (#754)

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

[w3c/payment-request] Merchantvalidation (#751)

[w3c/payment-request] Modifiers and [[serializedMethodData]] not actually used anywhere. (#753)

[w3c/payment-request] Modifiers and [[serializedModifierData]] not actually used anywhere. (#753)

[w3c/payment-request] Providing an `AbortSignal` instead of calling .abort() (#757)

[w3c/payment-request] Rename AddressErrorFields -> AddressErrors (#755)

[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] Support fine-grained errors for payment methods (#752)

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

[w3c/webpayments-methods-tokenization] Should there be an option to provide key (instead of keyProviderURL)? (#45)

Last message date: Tuesday, 31 July 2018 12:31:44 UTC