public-webpayments-specs@w3.org from September 2017 by author

Adrian Hope-Bailie

• Re: [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) (Friday, 29 September)
• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) (Friday, 29 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Wednesday, 20 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Monday, 18 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Monday, 18 September)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 18 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Monday, 18 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Monday, 18 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)

AhsanEjaz

• [w3c/payment-request] Add support for crypto currencties (#627) (Tuesday, 19 September)

Anders Rundgren

• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)

Anne van Kesteren

• [w3c/payment-handler] Add [Exposed] to all interfaces (#215) (Friday, 15 September)

ashok

• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Friday, 22 September)

carinsuranceadvice

• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 27 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 27 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 27 September)

chaals

• Re: [w3c/payment-request] Section for A11Y Considerations (#450) (Tuesday, 12 September)

Chad Campbell

• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)

chinnagogulapati

• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) (Saturday, 30 September)

Dan Dascalescu

• [w3c/payment-request] onpaymentchange event to validate payment details (#634) (Friday, 29 September)
• Re: [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) (Friday, 8 September)
• [w3c/payment-request] Pre-calculate shipping costs for available addresses (#615) (Thursday, 7 September)
• [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) (Thursday, 7 September)

Dave Longley

• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)

Denis Ah-Kang

• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) (Friday, 15 September)
• [w3c/payment-method-id] Auto publication no longer needed (#51) (Friday, 15 September)
• [w3c/payment-request] Auto publication no longer needed (#621) (Friday, 15 September)

Domenic Denicola

• Re: [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) (Thursday, 21 September)
• [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Thursday, 21 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Thursday, 7 September)
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) (Thursday, 7 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Wednesday, 6 September)
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) (Tuesday, 5 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Tuesday, 5 September)
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) (Tuesday, 5 September)
• Re: [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) (Tuesday, 5 September)
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) (Tuesday, 5 September)

Fredrik Roubert

• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)

ianbjacobs

• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Tuesday, 26 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Tuesday, 26 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) (Thursday, 21 September)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Thursday, 21 September)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 20 September)
• Re: [w3c/payment-request] Add support for crypto currencies (#627) (Tuesday, 19 September)
• Re: [w3c/payment-request] Add support for crypto currencies (#627) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Security addition (#214) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Security addition (#214) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Security addition (#214) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Removed section on instrument grouping with closure of issue 153 (#213) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Tuesday, 19 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Tuesday, 19 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 18 September)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 18 September)
• [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 18 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Monday, 18 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Monday, 18 September)
• [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Monday, 18 September)
• Re: [w3c/payment-handler] Add [Exposed] to all interfaces (#215) (Monday, 18 September)
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Monday, 18 September)
• [w3c/payment-request] Chore: Minor link fix (#619) (Wednesday, 13 September)
• [w3c/payment-request] Editorial: removed extra "the" (#616) (Friday, 8 September)
• Re: [w3c/payment-request] 'Pull' Payment Bias in API spec (#499) (Friday, 8 September)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Security addition (#214) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Security addition (#214) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Security addition (#214) (Wednesday, 6 September)
• [w3c/payment-handler] Security addition (#214) (Tuesday, 5 September)
• [w3c/payment-handler] Removed section on instrument grouping with closure of issue 153 (#213) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Ability to set default instrument for given handler (#173) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Add userHint to PaymentManager (#206) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Clarify empty instrument key meaning. (#208) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• Re: [w3c/payment-request] editorial: Clarify wording to not imply 'pull' only payments (#474) (Friday, 1 September)
• [w3c/payment-request] Less pull centric (#599) (Friday, 1 September)
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)
• Re: [w3c/payment-method-id] Clarify CR exit requirements (#50) (Friday, 1 September)

Jinho Bang

• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Wednesday, 20 September)
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Monday, 18 September)
• [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Monday, 18 September)
• Re: [w3c/payment-handler] Define PaymentRequestEvent.respondWith() behavior. (#194) (Monday, 4 September)

KJM

• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Relation between merchant order of payment methods and payment app order of instruments (#116) (Wednesday, 6 September)

Krystian Czesak

• [w3c/payment-handler] Allow Payment instrument to respond with user data (#218) (Friday, 29 September)

Lukasz Olejnik

• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Thursday, 21 September)

Marcos Cáceres

• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) (Friday, 29 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Tuesday, 26 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Tuesday, 26 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Tuesday, 26 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Tuesday, 26 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Tuesday, 26 September)
• Re: [w3c/payment-request] After CR, evaluate if paymentRequest.id being a UUID is a must (#588) (Monday, 25 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Monday, 25 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Monday, 25 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Monday, 25 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Monday, 25 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Monday, 25 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Monday, 25 September)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Monday, 25 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Friday, 22 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Friday, 22 September)
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] UAs should not alter value string (addresses #624) (#631) (Friday, 22 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)
• [w3c/payment-request] 404 on some tests (#630) (Thursday, 21 September)
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Propose text about why the api can reduce need; without any recommendations (#16) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Thursday, 21 September)
• Re: [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) (Thursday, 21 September)
• Re: [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) (Thursday, 21 September)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Thursday, 21 September)
• Re: [w3c/payment-request] "Exposing available payment methods" is confusing given the existence of canMakePayment() (#629) (Thursday, 21 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• [w3c/payment-method-basic-card] Things needed to publish as note (#43) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Gather default test data values (#41) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] PaymentResponse missing filters (#28) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add text about why the api can reduce need to store credit card information (#18) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add text about why the api can reduce need to store credit card information (#18) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Wednesday, 20 September)
• [w3c/payment-method-basic-card] Editorial: use Adam's text as intro (#42) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Relationship to PaymentRequest (#40) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Leave Off Unneeded Information (#5) (Wednesday, 20 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 20 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 20 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Wednesday, 20 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Tuesday, 19 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 19 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 19 September)
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Tuesday, 19 September)
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) (Tuesday, 19 September)
• [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Tuesday, 19 September)
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) (Tuesday, 19 September)
• [w3c/payment-request] Move to an incremental feature release model (#625) (Tuesday, 19 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Tuesday, 19 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Tuesday, 19 September)
• Re: [w3c/payment-request] Should user agent validate currency? (#490) (Tuesday, 19 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Tuesday, 19 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Tuesday, 19 September)
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) (Monday, 18 September)
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) (Monday, 18 September)
• Re: [w3c/payment-request] Typo fix (#623) (Monday, 18 September)
• Re: [w3c/payment-request] Typo fix (#623) (Monday, 18 September)
• Re: [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) (Monday, 18 September)
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) (Monday, 18 September)
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) (Monday, 18 September)
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) (Friday, 15 September)
• Re: [w3c/payment-method-id] Auto publication no longer needed (#51) (Friday, 15 September)
• Re: [w3c/payment-request] Auto publication no longer needed (#621) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] Processing note should be normative text (#34) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] Clarify this specification is intended to become a W3C Note (#27) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] Clarify the required behaviour for options parameters (#26) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] list/registry of approved card network identifiers should be listed in references section (#32) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• Re: [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• [w3c/payment-method-basic-card] Standardize `environment` member (#41) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] .updateWith() example says "throws" (#620) (Thursday, 14 September)
• Re: [w3c/payment-request] .updateWith() example says "throws" (#620) (Thursday, 14 September)
• [w3c/payment-request] .updateWith() example says "throws" (#620) (Thursday, 14 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] Chore: Minor link fix (#619) (Wednesday, 13 September)
• Re: [w3c/payment-request] Chore: Minor link fix (#619) (Wednesday, 13 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Wednesday, 13 September)
• [w3c/payment-request] Candidate Recommendation (Tuesday, 12 September)
• [w3c/payment-request] Make iframe allowpaymentrequest normative (#618) (Tuesday, 12 September)
• [w3c/payment-request] Decide on currencySystem (#617) (Monday, 11 September)
• Re: [w3c/payment-request] Editorial: removed extra "the" (#616) (Friday, 8 September)
• Re: [w3c/payment-request] Editorial: removed extra "the" (#616) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] shippingOption description is misleading (#534) (Friday, 8 September)
• Re: [w3c/payment-request] shippingOption description is misleading (#534) (Friday, 8 September)
• Re: [w3c/payment-request] 'Pull' Payment Bias in API spec (#499) (Friday, 8 September)
• Re: [w3c/payment-request] 'Pull' Payment Bias in API spec (#499) (Friday, 8 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Friday, 8 September)
• Re: [w3c/payment-request] Creation and assignment of PaymentAddress is underspecified (#603) (Friday, 8 September)
• Re: [w3c/payment-request] .updateWith() should only be callable if event was canceled (#589) (Friday, 8 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 8 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 8 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Friday, 8 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Friday, 8 September)
• Re: [w3c/payment-request] Pre-filter shipping addresses, e.g. by country (#614) (Friday, 8 September)
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) (Friday, 8 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Friday, 8 September)
• Re: [w3c/payment-request] Do not show payment requests for non-fully-active documents (#579) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) (Thursday, 7 September)
• Re: [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) (Thursday, 7 September)
• Re: [w3c/payment-method-id] Clarify CR exit requirements (#50) (Thursday, 7 September)
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Thursday, 7 September)
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) (Thursday, 7 September)
• Re: [w3c/payment-request] Add Exposed= to IDL interfaces (#611) (Thursday, 7 September)
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) (Thursday, 7 September)
• Re: [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) (Thursday, 7 September)
• [w3c/payment-request] Editorial: explicitly Expose=Window IDL interface (#612) (Thursday, 7 September)
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Wednesday, 6 September)
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Wednesday, 6 September)
• [w3c/payment-request] Add Exposed= to IDL interfaces (#611) (Wednesday, 6 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Wednesday, 6 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Wednesday, 6 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Wednesday, 6 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Security addition (#214) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Security addition (#214) (Wednesday, 6 September)
• Re: [w3c/payment-handler] Security addition (#214) (Wednesday, 6 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Wednesday, 6 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Wednesday, 6 September)
• Re: [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Wednesday, 6 September)
• Re: [w3c/payment-request] Implementation examples of PaymentAddress.languageCode (#608) (Wednesday, 6 September)
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Tuesday, 5 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• [w3c/payment-request] Only select shippingOption if asked to (closes #609) (#610) (Tuesday, 5 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• [w3c/payment-request] Implementation examples of PaymentAddress.languageCode (#608) (Tuesday, 5 September)
• [w3c/payment-request] Construct and set attrs on PaymentAddress (#607) (Tuesday, 5 September)
• Re: [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• Re: [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) (Tuesday, 5 September)
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) (Tuesday, 5 September)
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress.languageCode lacking canonical form (#602) (Tuesday, 5 September)
• Re: [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) (Tuesday, 5 September)
• [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Tuesday, 5 September)
• [w3c/payment-request] Canonicalize PaymentAddress.languageCode (closes #602) (#605) (Tuesday, 5 September)
• [w3c/payment-request] Fix PaymentAddress attr definition (closes #601) (#604) (Tuesday, 5 September)
• [w3c/payment-request] Creation and assignment of PaymentAddress is underspecified (#603) (Tuesday, 5 September)
• [w3c/payment-request] PaymentAddress.languageCode lacking canonical form (#602) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Tuesday, 5 September)
• Re: [w3c/payment-request] Duplicate shippingOptions lead to inconsistent `updateWith()` - should throw! (#594) (Monday, 4 September)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) (Monday, 4 September)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) (Monday, 4 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Monday, 4 September)
• Re: [w3c/payment-request] Populate implementation report (#560) (Monday, 4 September)
• Re: [w3c/payment-request] CR check list (#520) (Monday, 4 September)
• Re: [w3c/payment-request] CR check list (#520) (Monday, 4 September)
• Re: [w3c/payment-method-basic-card] Define processing model (#39) (Monday, 4 September)
• [w3c/payment-request] Integration with Feature Policy (#600) (Monday, 4 September)
• Re: [w3c/payment-request] Less pull centric (#599) (Friday, 1 September)
• Re: [w3c/payment-request] Less pull centric (#599) (Friday, 1 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 1 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 1 September)
• Re: [w3c/payment-request] Dont block UI if .updateWith() not called (closes #589) (#591) (Friday, 1 September)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) (Friday, 1 September)
• Re: [w3c/payment-request] editorial: Clarify wording to not imply 'pull' only payments (#474) (Friday, 1 September)
• Re: [w3c/payment-request] editorial: Clarify wording to not imply 'pull' only payments (#474) (Friday, 1 September)
• Re: [w3c/payment-request] Throw on dup shippingOptions ids (#596) (Friday, 1 September)
• [w3c/payment-method-id] Clarify CR exit requirements (#50) (Friday, 1 September)
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)
• [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)

Mark Richards

• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Wednesday, 27 September)
• Re: [w3c/payment-request] Regulatory Compliance Support (#632) (Monday, 25 September)
• [w3c/payment-request] Regulatory Compliance Support (#632) (Saturday, 23 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Friday, 22 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Thursday, 21 September)
• Re: [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Wednesday, 20 September)
• [w3c/payment-request] Suggested emphasis of privacy protections (#628) (Tuesday, 19 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 19 September)

Mathieu Perreault

• [w3c/payment-handler] Clarification of "instrumentKey" language (#212) (Tuesday, 5 September)

Michael[tm] Smith

• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)
• Re: [w3c/payment-request] Clarify CR exit requirements (#598) (Friday, 1 September)

Rouslan Solomakhin

• Re: [w3c/payment-request] onpaymentchange event to validate payment details (#634) (Friday, 29 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Thursday, 28 September)
• Re: [w3c/payment-request] Feature Request - Pre Authorization (#633) (Wednesday, 27 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-method-basic-card] Add an excludedFields BasicCardRequest parameter (#29) (Wednesday, 20 September)
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Make explicit which origin to use in conjunction with payment method manifest. (#209) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Security addition (#214) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Removed section on instrument grouping with closure of issue 153 (#213) (Tuesday, 19 September)
• Re: [w3c/payment-request] Clarify the `displayItems` are not shared with payment handler (#626) (Tuesday, 19 September)
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) (Tuesday, 19 September)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 18 September)
• Re: [w3c/payment-handler] Return origin of payment app in PaymentHandlerResponse data? (#217) (Monday, 18 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Monday, 18 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Monday, 18 September)
• Re: [w3c/payment-request] Are integer values for PaymentCurrencyAmount.value left as integers? (#624) (Monday, 18 September)
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Monday, 18 September)
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Monday, 18 September)
• Re: [w3c/payment-handler] Add [Exposed] to PaymentInstruments interface. (#216) (Monday, 18 September)
• Re: [w3c/payment-request] Implementation of PaymentAddress.languageCode (#608) (Monday, 18 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 14 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Friday, 8 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Wednesday, 6 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Wednesday, 6 September)
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Suggestion: replace `PaymentWallets` with a property on `PaymentInstrument` (#153) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Clarification of "instrumentKey" language (#212) (Tuesday, 5 September)
• Re: [w3c/payment-handler] Clarification of "instrumentKey" language (#212) (Tuesday, 5 September)
• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Tuesday, 5 September)
• Re: [w3c/payment-request] Implementation examples of PaymentAddress.languageCode (#608) (Tuesday, 5 September)
• Re: [w3c/payment-request] If requestShipping is false, pr.shippingOption should be null (#609) (Tuesday, 5 September)
• Re: [w3c/payment-request] PaymentAddress attribute definition is wrong (#601) (Tuesday, 5 September)

sabrinatseng

• Re: [w3c/payment-request] Pay method for testing environment (#613) (Monday, 18 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Friday, 15 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• Re: [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)
• [w3c/payment-request] Pay method for testing environment (#613) (Thursday, 7 September)

Terence Eden

• [w3c/payment-request] Typo fix (#623) (Monday, 18 September)
• [w3c/payment-request] Documentation error? 55 + 5 = 65 (#622) (Monday, 18 September)

Zach Koch

• Re: [w3c/payment-request] PayerAddress.phone and PayerResponse.payerPhone (#606) (Wednesday, 6 September)

Last message date: Saturday, 30 September 2017 17:49:53 UTC