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

Adam Solove

• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 30 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 30 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] Token properties? (#25) (Tuesday, 16 January)

Addison Phillips

• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Wednesday, 24 January)

Adrian Hope-Bailie

• Re: [w3c/payment-request] How are digital signatures supported for Payment Requests? (#291) (Saturday, 27 January)
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Saturday, 20 January)
• Re: [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) (Saturday, 20 January)
• [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) (Wednesday, 17 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 17 January)
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Wednesday, 17 January)

aestes

• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) (Tuesday, 23 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Monday, 22 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Friday, 19 January)

Anders Rundgren

• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Monday, 22 January)

Domenic Denicola

• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Monday, 29 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Monday, 29 January)
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) (Wednesday, 24 January)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Wednesday, 24 January)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) (Wednesday, 24 January)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 24 January)
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) (Wednesday, 24 January)
• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Monday, 22 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Friday, 19 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Friday, 19 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Friday, 19 January)
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) (Friday, 19 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Friday, 19 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Friday, 19 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Friday, 19 January)
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) (Friday, 19 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Friday, 19 January)
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) (Friday, 19 January)
• Re: [w3c/payment-request] Make paymentRequest.id a UUID a must (#588) (Friday, 19 January)
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) (Friday, 19 January)
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) (Friday, 19 January)
• Re: [w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16) (Friday, 19 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Thursday, 4 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Thursday, 4 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Thursday, 4 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Tuesday, 2 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Tuesday, 2 January)

Dominique Hazael-Massieux

• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)

Gildas Le Louarn

• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 30 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 30 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Thursday, 25 January)
• [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 22 January)

gogerald

• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Thursday, 4 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Thursday, 4 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Thursday, 4 January)

ianbjacobs

• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Tuesday, 30 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] What is purpose of mention of "out-of-band provisioning"? (#32) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] Key provider registration details lacking (#31) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] What public key formats are acceptable, and any constraints? (#33) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] What public key formats are acceptable, and any constraints? (#33) (Tuesday, 30 January)
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Monday, 29 January)
• [w3c/payment-request] Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] Call out payment handlers in abort() (#678) (Monday, 29 January)
• Re: [w3c/payment-request] Call out payment handlers in abort() (#678) (Monday, 29 January)
• [w3c/payment-request] Call out payment handlers in abort() (#678) (Monday, 29 January)
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] Document threat model (#36) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] Relationship between TokenizedCard and EncryptedTokenizedCard needs clarification (#35) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] What public key formats are acceptable, and any constraints? (#33) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] What is purpose of mention of "out-of-band provisioning"? (#32) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] Key provider registration details lacking (#31) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29) (Friday, 26 January)
• [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) (Friday, 26 January)
• Re: [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) (Friday, 26 January)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 25 January)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 25 January)
• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Monday, 22 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Monday, 22 January)
• Re: [w3c/payment-request] privacy: dont share line items (#670) (Monday, 22 January)
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Friday, 19 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Wednesday, 17 January)
• Re: [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) (Wednesday, 17 January)
• [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) (Monday, 15 January)
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) (Monday, 15 January)
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) (Monday, 15 January)
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) (Thursday, 11 January)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Thursday, 11 January)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Thursday, 11 January)
• Re: [w3c/payment-handler] Open Window Algorithm (#115) (Thursday, 11 January)
• Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) (Thursday, 11 January)
• Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) (Thursday, 11 January)
• Re: [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) (Monday, 8 January)
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) (Monday, 8 January)
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) (Sunday, 7 January)
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) (Friday, 5 January)
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) (Wednesday, 3 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Wednesday, 3 January)

Jinho Bang

• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Wednesday, 31 January)

KJM

• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) (Monday, 8 January)

Manu Sporny

• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) (Sunday, 7 January)

Marcos Cáceres

• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Wednesday, 31 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Tuesday, 30 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Tuesday, 30 January)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Tuesday, 30 January)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Tuesday, 30 January)
• Re: [w3c/payment-request] Editorial: Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] Editorial: Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) (Monday, 29 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Monday, 29 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Monday, 29 January)
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) (Monday, 29 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 29 January)
• [w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48) (Monday, 29 January)
• Re: [w3c/payment-method-basic-card] fix: correct links to tests (#47) (Monday, 29 January)
• Re: [w3c/payment-method-basic-card] fix: correct links to tests (#47) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) (Monday, 29 January)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Thursday, 25 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Thursday, 25 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Thursday, 25 January)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Wednesday, 24 January)
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Wednesday, 24 January)
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) (Wednesday, 24 January)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent constructor (#543) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) (Wednesday, 24 January)
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) (Wednesday, 24 January)
• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• [w3c/payment-request] Document privacy and security mitigations (#675) (Wednesday, 24 January)
• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] Authors are not conformance classes (#440) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Wednesday, 24 January)
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] Editorial fixes (#673) (Wednesday, 24 January)
• Re: [w3c/payment-request] Move to an incremental feature release model (#625) (Tuesday, 23 January)
• Re: [w3c/payment-request] Move to an incremental feature release model (#625) (Tuesday, 23 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Tuesday, 23 January)
• [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) (Tuesday, 23 January)
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) (Tuesday, 23 January)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Tuesday, 23 January)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Tuesday, 23 January)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 23 January)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 23 January)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Tuesday, 23 January)
• [w3c/payment-request] Editorial fixes (#673) (Tuesday, 23 January)
• Re: [w3c/payment-request] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Tuesday, 23 January)
• Re: [w3c/payment-request] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) (Tuesday, 23 January)
• Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) (Tuesday, 23 January)
• Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) (Tuesday, 23 January)
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) (Tuesday, 23 January)
• Re: [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) (Tuesday, 23 January)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Tuesday, 23 January)
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Tuesday, 23 January)
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) (Tuesday, 23 January)
• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Tuesday, 23 January)
• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) (Tuesday, 23 January)
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) (Tuesday, 23 January)
• Re: [w3c/payment-request] Use HTML's (or infra) definition of “valid decimal monetary value”, once available (#301) (Tuesday, 23 January)
• Re: [w3c/payment-request] Use HTML's (or infra) definition of “valid decimal monetary value”, once available (#301) (Tuesday, 23 January)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Tuesday, 23 January)
• Re: [w3c/payment-request] How do the payer and payee agree on the payment obligation as part of the flow? (#113) (Tuesday, 23 January)
• Re: [w3c/payment-request] How are digital signatures supported for Payment Requests? (#291) (Tuesday, 23 January)
• Re: [w3c/payment-request] How are digital signatures supported for Payment Requests? (#291) (Tuesday, 23 January)
• Re: [w3c/payment-request] Should the web page be able to provide status information before calling complete() (#5) (Tuesday, 23 January)
• Re: [w3c/payment-request] Should the web page be able to provide status information before calling complete() (#5) (Tuesday, 23 January)
• Re: [w3c/payment-request] API Data Integrity (#31) (Tuesday, 23 January)
• Re: [w3c/payment-request] API Data Integrity (#31) (Tuesday, 23 January)
• Re: [w3c/payment-request] Should the API support field validation? (#225) (Tuesday, 23 January)
• Re: [w3c/payment-request] Should the API support field validation? (#225) (Tuesday, 23 January)
• Re: [w3c/payment-request] show() method lacks developer guidance (#461) (Tuesday, 23 January)
• Re: [w3c/payment-request] show() method lacks developer guidance (#461) (Tuesday, 23 January)
• [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Tuesday, 23 January)
• [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) (Tuesday, 23 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Tuesday, 23 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Tuesday, 23 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Monday, 22 January)
• Re: [w3c/payment-request] Editors to figure out text on line items (#477) (Monday, 22 January)
• Re: [w3c/payment-request] privacy: dont share line items (#670) (Monday, 22 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 22 January)
• [w3c/payment-method-basic-card] Add "store" card support (#46) (Monday, 22 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Monday, 22 January)
• [w3c/payment-request] privacy: dont share line items (#670) (Monday, 22 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Monday, 22 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Monday, 22 January)
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) (Monday, 22 January)
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) (Monday, 22 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Monday, 22 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Monday, 22 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Monday, 22 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Monday, 22 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Monday, 22 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Monday, 22 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Monday, 22 January)
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Monday, 22 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Monday, 22 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Monday, 22 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Monday, 22 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Monday, 22 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Monday, 22 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Friday, 19 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Friday, 19 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Friday, 19 January)
• Re: [w3c/payment-request] Request: designated receiver for Payment Response (#660) (Friday, 19 January)
• Re: [w3c/payment-request] Request: designated receiver for Payment Response (#660) (Friday, 19 January)
• Re: [w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16) (Friday, 19 January)
• Re: [w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16) (Friday, 19 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Friday, 19 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Friday, 19 January)
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) (Friday, 19 January)
• [w3c/payment-request] Spread on update (#669) (Friday, 19 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Friday, 19 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Friday, 19 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Thursday, 18 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Thursday, 18 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Thursday, 18 January)
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) (Thursday, 18 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Thursday, 18 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Thursday, 18 January)
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) (Thursday, 18 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Thursday, 18 January)
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Thursday, 18 January)
• Re: [w3c/payment-request] wip: allow show to take optional promise (#668) (Wednesday, 17 January)
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Wednesday, 17 January)
• [w3c/payment-request] wip: allow show to take optional promise (#668) (Wednesday, 17 January)
• [w3c/payment-request] Editorial: fixup updateWith() example (#667) (Wednesday, 17 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 17 January)
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) (Wednesday, 17 January)
• Re: [w3c/payment-request] Request: designated receiver for Payment Response (#660) (Wednesday, 17 January)
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) (Wednesday, 17 January)
• [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 17 January)
• [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) (Wednesday, 17 January)
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) (Monday, 15 January)
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) (Monday, 15 January)
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) (Friday, 12 January)
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) (Thursday, 11 January)

Matt Giuca

• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Wednesday, 31 January)

Matt N.

• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Friday, 26 January)
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) (Thursday, 25 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 17 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 17 January)

michelle

• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) (Wednesday, 24 January)

Peter Saint-Andre

• Re: [w3c/webpayments-methods-tokenization] Document threat model (#36) (Tuesday, 30 January)
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) (Tuesday, 30 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 29 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Monday, 29 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Monday, 29 January)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Monday, 29 January)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Friday, 26 January)
• Re: [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 25 January)
• [w3c/payment-request] Add latitude and longitude to PaymentAddress interface? (#677) (Thursday, 25 January)
• [w3c/payment-request] Clarify addressLine definition (#676) (Thursday, 25 January)
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) (Thursday, 25 January)
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) (Thursday, 25 January)
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) (Thursday, 25 January)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Wednesday, 24 January)
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) (Wednesday, 24 January)
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) (Wednesday, 24 January)
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) (Wednesday, 24 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Wednesday, 24 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Wednesday, 24 January)
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) (Wednesday, 24 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Thursday, 18 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Wednesday, 17 January)
• [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) (Tuesday, 16 January)

Rouslan Solomakhin

• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Wednesday, 31 January)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Wednesday, 31 January)
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Tuesday, 30 January)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Tuesday, 30 January)
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Tuesday, 30 January)
• [w3c/payment-handler] Proposal: Remove requestPermission() (#246) (Tuesday, 30 January)
• Re: [w3c/payment-handler] User consent and permissions (#239) (Tuesday, 30 January)
• Re: [w3c/payment-handler] User consent and permissions (#239) (Tuesday, 30 January)
• Re: [w3c/payment-handler] User consent and permissions (#239) (Monday, 29 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Monday, 29 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Monday, 29 January)
• Re: [w3c/payment-request] Standardize phone number format (#652) (Thursday, 25 January)
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) (Wednesday, 24 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Wednesday, 3 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Tuesday, 2 January)
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) (Tuesday, 2 January)

Sachin Ahuja

• [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) (Sunday, 7 January)

Sebsg

• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Friday, 26 January)

Thaddée Tyl

• [w3c/payment-method-basic-card] fix: correct links to tests (#47) (Thursday, 25 January)

TSMatthews

• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) (Friday, 26 January)

Zach Koch

• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) (Tuesday, 30 January)

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