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

Wednesday, 31 January 2018

• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Jinho Bang
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Marcos Cáceres
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Matt Giuca

Tuesday, 30 January 2018

• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) ianbjacobs
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Rouslan Solomakhin
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Zach Koch
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) ianbjacobs
• Re: [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
• [w3c/payment-handler] Proposal: Remove requestPermission() (#246) Rouslan Solomakhin
• Re: [w3c/webpayments-methods-tokenization] What is purpose of mention of "out-of-band provisioning"? (#32) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Key provider registration details lacking (#31) ianbjacobs
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] What public key formats are acceptable, and any constraints? (#33) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] What public key formats are acceptable, and any constraints? (#33) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Document threat model (#36) Peter Saint-Andre
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) Peter Saint-Andre
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Adam Solove
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Gildas Le Louarn
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Adam Solove
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Gildas Le Louarn
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Marcos Cáceres
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Marcos Cáceres
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Marcos Cáceres

Monday, 29 January 2018

• Re: [w3c/payment-request] Editorial: Call out payment handlers in abort() (#679) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: Call out payment handlers in abort() (#679) Marcos Cáceres
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) ianbjacobs
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) Marcos Cáceres
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) Marcos Cáceres
• Re: [w3c/payment-request] Call out payment handlers in abort() (#679) ianbjacobs
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Peter Saint-Andre
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) ianbjacobs
• [w3c/payment-request] Call out payment handlers in abort() (#679) ianbjacobs
• Re: [w3c/payment-request] Call out payment handlers in abort() (#678) ianbjacobs
• Re: [w3c/payment-request] Call out payment handlers in abort() (#678) ianbjacobs
• [w3c/payment-request] Call out payment handlers in abort() (#678) ianbjacobs
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Peter Saint-Andre
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Peter Saint-Andre
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Domenic Denicola
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Peter Saint-Andre
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Domenic Denicola
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Peter Saint-Andre
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Peter Saint-Andre
• Re: [w3c/payment-handler] User consent and permissions (#239) Rouslan Solomakhin
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) Marcos Cáceres
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Domenic Denicola
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Marcos Cáceres
• [w3c/payment-method-basic-card] Broken link basiccardresponse-member-formats-manual.https.html (#48) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] fix: correct links to tests (#47) Marcos Cáceres
• Re: [w3c/payment-method-basic-card] fix: correct links to tests (#47) Marcos Cáceres
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) Marcos Cáceres
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Marcos Cáceres
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres

Saturday, 27 January 2018

• Re: [w3c/payment-request] How are digital signatures supported for Payment Requests? (#291) Adrian Hope-Bailie

Friday, 26 January 2018

• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) Adrian Hope-Bailie
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Matt N.
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Linkage to BasicCard Spec (#17) ianbjacobs
• [w3c/webpayments-methods-tokenization] Document threat model (#36) ianbjacobs
• [w3c/webpayments-methods-tokenization] Relationship between TokenizedCard and EncryptedTokenizedCard needs clarification (#35) ianbjacobs
• [w3c/webpayments-methods-tokenization] Please include example of TokenizedCardResponse (#34) ianbjacobs
• [w3c/webpayments-methods-tokenization] What public key formats are acceptable, and any constraints? (#33) ianbjacobs
• [w3c/webpayments-methods-tokenization] What is purpose of mention of "out-of-band provisioning"? (#32) ianbjacobs
• [w3c/webpayments-methods-tokenization] Key provider registration details lacking (#31) ianbjacobs
• [w3c/webpayments-methods-tokenization] Details about encryption expectations lacking (#30) ianbjacobs
• [w3c/webpayments-methods-tokenization] What does "BasicCard-like payment request flow" mean? (#29) ianbjacobs
• [w3c/webpayments-methods-tokenization] What does "EMV-like security" mean? (#28) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Proposal for dealing with Signed and Unsigned data (#23) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] change field name of oneTimeUse to singleUse (#15) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Should the tokenization task force standardize an interface between payment apps and tokenization service providers? (#14) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Should the response data include an "expires" field? (#12) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Replace usage of 'last4' with 'suffix' (#4) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) ianbjacobs
• Re: [w3c/payment-request] Standardize phone number format (#652) Peter Saint-Andre
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Sebsg
• Re: [w3c/payment-request] Standardize phone number format (#652) Adam Solove
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) TSMatthews

Thursday, 25 January 2018

• Re: [w3c/payment-request] Clarify addressLine definition (#676) ianbjacobs
• Re: [w3c/payment-request] Clarify addressLine definition (#676) Peter Saint-Andre
• Re: [w3c/payment-request] Clarify addressLine definition (#676) ianbjacobs
• [w3c/payment-request] Add latitude and longitude to PaymentAddress interface? (#677) Peter Saint-Andre
• [w3c/payment-request] Clarify addressLine definition (#676) Peter Saint-Andre
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Peter Saint-Andre
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) Peter Saint-Andre
• Re: [w3c/payment-request] Feat: add regionCode attribute and member (ab1ba80) Peter Saint-Andre
• Re: [w3c/payment-request] Standardize phone number format (#652) Rouslan Solomakhin
• [w3c/payment-method-basic-card] fix: correct links to tests (#47) Thaddée Tyl
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Gildas Le Louarn
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Matt N.
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
• Re: [w3c/payment-request] Standardize phone number format (#652) Marcos Cáceres
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres

Wednesday, 24 January 2018

• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) Peter Saint-Andre
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Peter Saint-Andre
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) Addison Phillips
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) Peter Saint-Andre
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Peter Saint-Andre
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Peter Saint-Andre
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Peter Saint-Andre
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Peter Saint-Andre
• Re: [w3c/payment-request] Authors are not conformance classes (#440) Dominique Hazael-Massieux
• Re: [w3c/payment-request] Authors are not conformance classes (#440) ianbjacobs
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Rouslan Solomakhin
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) michelle
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent constructor (#543) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) Domenic Denicola
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) Marcos Cáceres
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Domenic Denicola
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Domenic Denicola
• Re: [w3c/payment-request] Authors are not conformance classes (#440) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) Domenic Denicola
• Re: [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Domenic Denicola
• Re: [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres
• [w3c/payment-request] Document privacy and security mitigations (#675) Marcos Cáceres
• Re: [w3c/payment-request] Authors are not conformance classes (#440) Marcos Cáceres
• Re: [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres
• Re: [w3c/payment-request] Clarity required in section 21.2 regarding privacy (#475) Marcos Cáceres
• Re: [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) Domenic Denicola
• Re: [w3c/payment-request] Authors are not conformance classes (#440) Domenic Denicola
• Re: [w3c/payment-request] Authors are not conformance classes (#440) Marcos Cáceres
• Re: [w3c/payment-request] Editorial fixes (#673) Domenic Denicola
• Re: [w3c/payment-request] Editorial fixes (#673) Domenic Denicola
• Re: [w3c/payment-request] Authors are not conformance classes (#440) Domenic Denicola
• Re: [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres
• Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663) Marcos Cáceres
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) Marcos Cáceres
• Re: [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres
• Re: [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres

Tuesday, 23 January 2018

• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) ianbjacobs
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) aestes
• Re: [w3c/payment-request] Editorial fixes (#673) ianbjacobs
• Re: [w3c/payment-request] Move to an incremental feature release model (#625) Marcos Cáceres
• Re: [w3c/payment-request] Move to an incremental feature release model (#625) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Marcos Cáceres
• [w3c/payment-request] Editorial: PaymentRequestUpdateEvent ctor algo (#674) Marcos Cáceres
• Re: [w3c/payment-request] redact full shipping address from event until payment response (#648) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Marcos Cáceres
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Marcos Cáceres
• [w3c/payment-request] Editorial fixes (#673) Marcos Cáceres
• Re: [w3c/payment-request] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Marcos Cáceres
• Re: [w3c/payment-request] Add dir/lang member on dictionaries whose content is displayed in browser UI (#327) Marcos Cáceres
• Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) Marcos Cáceres
• Re: [w3c/payment-request] Unclear what happens when multiple PRs call show() (#462) Marcos Cáceres
• Re: [w3c/payment-request] "User accepts the payment request algorithm" needs to clarify where Payment Handlers are invoked (#476) Marcos Cáceres
• Re: [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) Marcos Cáceres
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) Marcos Cáceres
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Marcos Cáceres
• Re: [w3c/payment-request] Dealing with name as returned by the API (i18n) (#634) Marcos Cáceres
• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Marcos Cáceres
• Re: [w3c/payment-request] Is browser support for PR API configurable? (#642) Marcos Cáceres
• Re: [w3c/payment-request] Merchant-specified default shipping address (#653) Marcos Cáceres
• Re: [w3c/payment-request] Use HTML's (or infra) definition of “valid decimal monetary value”, once available (#301) Marcos Cáceres
• Re: [w3c/payment-request] Use HTML's (or infra) definition of “valid decimal monetary value”, once available (#301) Marcos Cáceres
• Re: [w3c/payment-request] Add payerGivenName + payerFamilyName to PaymentAddress (#480) Marcos Cáceres
• Re: [w3c/payment-request] How do the payer and payee agree on the payment obligation as part of the flow? (#113) Marcos Cáceres
• Re: [w3c/payment-request] How are digital signatures supported for Payment Requests? (#291) Marcos Cáceres
• Re: [w3c/payment-request] How are digital signatures supported for Payment Requests? (#291) Marcos Cáceres
• Re: [w3c/payment-request] Should the web page be able to provide status information before calling complete() (#5) Marcos Cáceres
• Re: [w3c/payment-request] Should the web page be able to provide status information before calling complete() (#5) Marcos Cáceres
• Re: [w3c/payment-request] API Data Integrity (#31) Marcos Cáceres
• Re: [w3c/payment-request] API Data Integrity (#31) Marcos Cáceres
• Re: [w3c/payment-request] Should the API support field validation? (#225) Marcos Cáceres
• Re: [w3c/payment-request] Should the API support field validation? (#225) Marcos Cáceres
• Re: [w3c/payment-request] show() method lacks developer guidance (#461) Marcos Cáceres
• Re: [w3c/payment-request] show() method lacks developer guidance (#461) Marcos Cáceres
• [w3c/payment-request] Feat: allow show() to take optional detailsPromise (#672) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) ianbjacobs
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) ianbjacobs
• Re: [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) Marcos Cáceres
• [w3c/payment-request] Editorial: define update a PaymentRequest's details algo (#671) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres

Monday, 22 January 2018

• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) ianbjacobs
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) Marcos Cáceres
• Re: [w3c/payment-request] Editors to figure out text on line items (#477) Marcos Cáceres
• Re: [w3c/payment-request] privacy: dont share line items (#670) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) ianbjacobs
• Re: [w3c/payment-request] privacy: dont share line items (#670) ianbjacobs
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) aestes
• Re: [w3c/3ds] 3DS 2.0 specificities by schema (#1) Marcos Cáceres
• [w3c/3ds] 3DS 2.0 specificities by schema (#1) Gildas Le Louarn
• [w3c/payment-method-basic-card] Add "store" card support (#46) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Marcos Cáceres
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) Anders Rundgren
• [w3c/payment-request] privacy: dont share line items (#670) Marcos Cáceres
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Marcos Cáceres
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Marcos Cáceres
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) Marcos Cáceres
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Marcos Cáceres
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Domenic Denicola
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres

Saturday, 20 January 2018

• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) Adrian Hope-Bailie
• Re: [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) Adrian Hope-Bailie

Friday, 19 January 2018

• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Domenic Denicola
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Domenic Denicola
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Marcos Cáceres
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Domenic Denicola
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Marcos Cáceres
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) Domenic Denicola
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Marcos Cáceres
• Re: [w3c/payment-request] updateWith(data) should merge with request.data (#649) Domenic Denicola
• Re: [w3c/payment-request] Feat: add constructor to PaymentAddress (#654) Domenic Denicola
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Domenic Denicola
• Re: [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) ianbjacobs
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Domenic Denicola
• Re: [w3c/payment-request] Add localization hint for payment sheet (#656) Domenic Denicola
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) Domenic Denicola
• Re: [w3c/payment-request] Make paymentRequest.id a UUID a must (#588) Domenic Denicola
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) Domenic Denicola
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) Domenic Denicola
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) aestes
• Re: [w3c/payment-request] Request: designated receiver for Payment Response (#660) Marcos Cáceres
• Re: [w3c/payment-request] Request: designated receiver for Payment Response (#660) Marcos Cáceres
• Re: [w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16) Marcos Cáceres
• Re: [w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16) Domenic Denicola
• Re: [w3c/payment-request] wip: support partial data updates (closes #649) (fc5ea16) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Spread resolved `data` on updateWith() (#669) Marcos Cáceres
• [w3c/payment-request] Spread on update (#669) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Adding support for private-label credit cards (#662) Marcos Cáceres

Thursday, 18 January 2018

• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Peter Saint-Andre
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] wip: allow show() to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) Marcos Cáceres
• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) Marcos Cáceres

Wednesday, 17 January 2018

• Re: [w3c/payment-request] Editorial: fixup updateWith() example (#667) ianbjacobs
• Re: [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) ianbjacobs
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Peter Saint-Andre
• [w3c/webpayments-methods-tokenization] Drop the word 'card' from this payment method (#27) Adrian Hope-Bailie
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Adrian Hope-Bailie
• Re: [w3c/webpayments-methods-tokenization] Token properties? (#25) Adrian Hope-Bailie
• Re: [w3c/payment-request] wip: allow show to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] Add way to update `total` and `displayItems` after `.show()` but before user interaction (#645) Marcos Cáceres
• [w3c/payment-request] wip: allow show to take optional promise (#668) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Matt N.
• [w3c/payment-request] Editorial: fixup updateWith() example (#667) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• Re: [w3c/payment-request] Allow locale to be specified by the developer. (#650) Marcos Cáceres
• Re: [w3c/payment-request] Request: designated receiver for Payment Response (#660) Marcos Cáceres
• Re: [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Matt N.
• Re: [w3c/payment-request] Should PaymentItems have a type? (#163) Marcos Cáceres
• [w3c/payment-request] Feat: adds PaymentItemType enum and PaymentItem.type (#666) Marcos Cáceres
• [w3c/payment-request] Assure PaymentRequest.id is a UUID (closes #588) (#665) Marcos Cáceres

Tuesday, 16 January 2018

• [w3c/webpayments-methods-tokenization] Early Review Feedback (#26) Peter Saint-Andre
• [w3c/webpayments-methods-tokenization] Token properties? (#25) Adam Solove

Monday, 15 January 2018

• [w3c/payment-handler] Editorial: Replace site with origin; mark as informative (#245) ianbjacobs
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Marcos Cáceres
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) ianbjacobs
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) ianbjacobs

Friday, 12 January 2018

• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) Marcos Cáceres

Thursday, 11 January 2018

• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) ianbjacobs
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) ianbjacobs
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) ianbjacobs
• Re: [w3c/payment-handler] Open Window Algorithm (#115) ianbjacobs
• Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) ianbjacobs
• Re: [w3c/payment-handler] Does payment instrument registration imply a display order? (#243) ianbjacobs
• Re: [w3c/payment-handler] add a "public computing" section to security/privacy considerations (#244) Marcos Cáceres

Monday, 8 January 2018

• Re: [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) ianbjacobs
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) KJM

Sunday, 7 January 2018

• [w3c/webpayments-methods-tokenization] Tokenized Card Spec Review (#24) Sachin Ahuja
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) ianbjacobs
• Re: [w3c/payment-handler] Edits regarding ordering based on 7 Dec WG teleconf (#242) Manu Sporny

Friday, 5 January 2018

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

Thursday, 4 January 2018

• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Domenic Denicola
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) gogerald
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Domenic Denicola
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) gogerald
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Domenic Denicola
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) gogerald

Wednesday, 3 January 2018

• Re: [w3c/webpayments-methods-tokenization] Generalisation of Encrypted Card (#22) ianbjacobs
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) ianbjacobs

Tuesday, 2 January 2018

• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Domenic Denicola
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Domenic Denicola
• Re: [w3c/payment-handler] Just-in-time payment handler install (#240) Rouslan Solomakhin

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