public-webpayments-specs@w3.org from June 2016 by author

adamroach

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Friday, 24 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 23 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 23 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 23 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Update promise rejection (#187) (Wednesday, 1 June)

Ade Bateman

Re: [w3c/browser-payment-api] Fix two minor typos. (#220) (Monday, 27 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] Should it be possible to provide amounts in more than one currency (#3) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Remove totalAmount per telcon resolution. (#219) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 16 June)
[w3c/browser-payment-api] Remove totalAmount per telcon resolution. (#219) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Add shippingOption to response (#217) (Wednesday, 15 June)
[w3c/browser-payment-api] Add shippingOption to response (#217) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Update promise rejection (#187) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Update promise rejection (#187) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should it be possible to vary amounts depending on payment method (#4) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Remove unnecessary clause about validation. (#213) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Spec prohibits currency validation but doesn't define what it is (#175) (Wednesday, 15 June)
[w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Removing notes for closed issues. (#214) (Thursday, 9 June)
[w3c/browser-payment-api] Removing notes for closed issues. (#214) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Should we support a delegated state for PaymentRequest? (#7) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Should we support a delegated state for PaymentRequest? (#7) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)
[w3c/browser-payment-api] Remove unnecessary clause about validation. (#213) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Simple editorial fixes. (#212) (Wednesday, 8 June)
[w3c/browser-payment-api] Simple editorial fixes. (#212) (Wednesday, 8 June)
[w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)
[w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) (Wednesday, 8 June)
[w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Move PMI and Card specs out of repo (#207) (Tuesday, 7 June)
[w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208) (Wednesday, 1 June)

Adrian Hope-Bailie

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Wednesday, 29 June)
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Saturday, 25 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 23 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) (Monday, 20 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Monday, 20 June)
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) (Monday, 20 June)
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) (Monday, 20 June)
Re: [w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) (Monday, 20 June)
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) (Monday, 20 June)
Re: [w3c/browser-payment-api] Add section on internationalization (#53) (Monday, 20 June)
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) (Monday, 20 June)
Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) (Monday, 20 June)
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Payment Instrument clarification (#104) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] What is the extensibility mechanism for the payment request and response messages? (#146) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Write-up initial proposal for payment app registration spec (#12) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should the browser pass user data it has collected (email etc) to the payment app? (#194) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should the browser pass user data it has collected (email etc) to the payment app? (#194) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#45) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should the payment API be more conversational or less conversational? (#51) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Add section on internationalization (#53) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] What component does the payment method intersection? (#103) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#109) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Dynamic Currency Conversion (DCC) Support (#178) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Update "user accepts the payment request algorithm" to include interaction with payment app (#192) (Wednesday, 15 June)
[w3c/browser-payment-api] Update references to "Payment Transaction Message Specification" (#218) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] What about billing address (#216) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] What about billing address (#216) (Wednesday, 15 June)
Re: [w3c/webpayments-method-identifiers] PROPOSAL: Use query string parameters for PMI matching (#2) (Monday, 13 June)
Re: [w3c/webpayments-method-identifiers] PROPOSAL: Use query string parameters for PMI matching (#2) (Monday, 13 June)
[w3c/webpayments-method-identifiers] PROPOSAL: PMI identifies payment method specification, constraints for additional granularity (#5) (Monday, 13 June)
Re: [w3c/browser-payment-api] Removing notes for closed issues. (#214) (Friday, 10 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Friday, 10 June)
Re: [w3c/browser-payment-api] Remove unnecessary clause about validation. (#213) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Simple editorial fixes. (#212) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Rename remaining types so that all begin Payment* (#208) (Thursday, 2 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 2 June)
Re: [w3c/browser-payment-api] Update promise rejection (#187) (Wednesday, 1 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 1 June)
Re: [w3c/browser-payment-api] Update promise rejection (#187) (Wednesday, 1 June)

Ajay Kapur

Re: [w3c/browser-payment-api] Support for gift cards and discount codes (#145) (Thursday, 23 June)

Anders Rundgren

Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) (Thursday, 16 June)

Barış Güler

[w3c/browser-payment-api] What about billing address (#216) (Wednesday, 15 June)

Dave Longley

Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)

ianbjacobs

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 23 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) (Wednesday, 22 June)
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Add section on internationalization (#53) (Thursday, 16 June)
Re: [w3c/browser-payment-api] What about billing address (#216) (Wednesday, 15 June)
Re: [w3c/webpayments-method-identifiers] PROPOSAL: PMI identifies payment method specification, use meta-data for additional granularity (#5) (Monday, 13 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Friday, 10 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Remove unnecessary clause about validation. (#213) (Thursday, 9 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) (Wednesday, 8 June)

Jinho Bang

[w3c/browser-payment-api] Fix a minor typo in PaymentRequest constructor description. (#221) (Tuesday, 28 June)
[w3c/browser-payment-api] Fix two minor typos. (#220) (Tuesday, 21 June)

Manu Sporny

Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Thursday, 23 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/browser-payment-api] Should PaymentResponse include totalAmount and if so must it be one of the supplied totals (#215) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are payment requests and responses passed between the browser and third-party native wallets? (#50) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How are web-based payment apps supported? (#39) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Specifying Mandatory Data (#97) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Add section on Extensibility (#44) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Combine API parameters into a single request object + options (#15) (Thursday, 16 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Any plan to allow this API to be called by non-merchants? (#35) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Merge Payment Request Architecture with Capabilities Document (#42) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Add section on internationalization (#53) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Should show() be renamed? (#127) (Thursday, 16 June)
Re: [w3c/browser-payment-api] Is it neccessary to distinguish the origin of data provided in the payment response, and how would we do it? (#173) (Thursday, 16 June)

mattsaxon

Michael[tm] Smith

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Tuesday, 28 June)

Rouslan Solomakhin

Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) (Wednesday, 22 June)
Re: [w3c/webpayments-method-identifiers] Should we define nesting/grouping semantics for payment method identifier matching? (#1) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Update Introduction to describe actors better (#121) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Propose a payment method specification that includes an example of field level security (#141) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 22 June)
Re: [w3c/browser-payment-api] How will the spec address versioning / feature detection? (#33) (Monday, 20 June)
Re: [w3c/webpayments-methods-card] Added BasicCardRequest dictionary supporting specification of RequiredFields (#4) (Saturday, 18 June)
Re: [w3c/browser-payment-api] Add shippingOption to response (#217) (Wednesday, 15 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Proposal to abort if updateWith promise is rejected (#209) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Remove special case handling for single shipping option. (#210) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Support different amounts per payment method. (#211) (Wednesday, 8 June)
Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) (Friday, 3 June)
Re: [w3c/browser-payment-api] Terms and conditions next to "Pay" button (#195) (Friday, 3 June)
Re: [w3c/browser-payment-api] Currency Types and Rendering (#185) (Wednesday, 1 June)

Tri Nguyen

Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8) (Wednesday, 15 June)

Zach Koch

Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Wednesday, 29 June)
Re: [w3c/browser-payment-api] Should the Payment Request API only be available in a top-level browsing context? (#2) (Monday, 27 June)

Last message date: Wednesday, 29 June 2016 12:03:56 UTC