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

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

[w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244)

[w3c/payment-handler] Does payment instrument registration imply a display order? (#243)

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

[w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242)

[w3c/payment-handler] Just-in-time payment handler install (#240)

[w3c/payment-handler] Open Window Algorithm (#115)

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

[w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116)

[w3c/payment-handler] User consent and permissions (#239)

[w3c/payment-method-basic-card] Add "store" card support (#46)

[w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48)

[w3c/payment-method-basic-card] fix: correct links to tests (#47)

[w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629)

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

[w3c/payment-request] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327)

[w3c/payment-request] Add latitude and longitude to PaymentAddress interface? (#677)

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

[w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480)

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

[w3c/payment-request] Adding support for private-label credit cards (#662)

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

[w3c/payment-request] API Data Integrity (#31)

[w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665)

[w3c/payment-request] Authors are not conformance classes (#440)

[w3c/payment-request] Call out payment handlers in abort() (#678)

[w3c/payment-request] Call out payment handlers in abort() (#679)

[w3c/payment-request] Clarify addressLine definition (#676)

[w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626)

[w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475)

[w3c/payment-request] Dealing with name as returned by the API (i18n) (#634)

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

[w3c/payment-request] Editorial fixes (#673)

[w3c/payment-request] Editorial: Call out payment handlers in abort() (#679)

[w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671)

[w3c/payment-request] Editorial: fixup updateWith() example (#667)

[w3c/payment-request] Editorial: PaymentRequestUpdateEvent constructor (#543)

[w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674)

[w3c/payment-request] Editors to figure out text on line items (#477)

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

[w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80)

[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] How are digital signatures supported for Payment Requests? (#291)

[w3c/payment-request] How do the payer and payee agree on the payment obligation as part of the flow? (#113)

[w3c/payment-request] Is browser support for PR API configurable? (#642)

[w3c/payment-request] Make paymentRequest.id a UUID a must (#588)

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

[w3c/payment-request] Move to an incremental feature release model (#625)

[w3c/payment-request] PaymentAddress 'region' inconsistencies (#663)

[w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614)

[w3c/payment-request] privacy: dont share line items (#670)

[w3c/payment-request] redact full shipping address from event until payment response (#648)

[w3c/payment-request] Request: designated receiver for Payment Response (#660)

[w3c/payment-request] Should PaymentItems have a type? (#163)

[w3c/payment-request] Should the API support field validation? (#225)

[w3c/payment-request] Should the web page be able to provide status information before calling complete() (#5)

[w3c/payment-request] show() method lacks developer guidance (#461)

[w3c/payment-request] Spread on update (#669)

[w3c/payment-request] Spread resolved `data` on updateWith() (#669)

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

[w3c/payment-request] Suggested emphasis of privacy protections (#628)

[w3c/payment-request] Unclear what happens when multiple PRs call show() (#462)

[w3c/payment-request] updateWith(data) should merge with request.data (#649)

[w3c/payment-request] Use HTML's (or infra) definition of “valid decimal monetary value”, once available (#301)

[w3c/payment-request] wip: allow show to take optional promise (#668)

[w3c/payment-request] wip: allow show() to take optional promise (#668)

[w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16)

[w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15)

[w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30)

[w3c/webpayments-methods-tokenization] Document threat model (#36)

[w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27)

[w3c/webpayments-methods-tokenization] Early Review Feedback (#26)

[w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22)

[w3c/webpayments-methods-tokenization] Key provider registration details lacking (#31)

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

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

[w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23)

[w3c/webpayments-methods-tokenization] Relationship between TokenizedCard and EncryptedTokenizedCard needs clarification (#35)

[w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4)

[w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12)

[w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14)

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

[w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24)

[w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29)

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

[w3c/webpayments-methods-tokenization] What is purpose of mention of "out-of-band provisioning"? (#32)

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

Last message date: Wednesday, 31 January 2018 14:37:35 UTC