public-payments-wg@w3.org from March 2016 by subject

[Agenda] 10 March WPWG teleconference

[Agenda] 31 March WPWG teleconference

[Minutes] 10 March teleconference

[Minutes] 17 March 2016 WPWG Teleconference

[Minutes] 31 March 2016 WPWG Teleconference

[paymentrequest] At the time complete() is called, your ability to say success (true) or failure (false) may depend on the payment method (#67)

[paymentrequest] boolean arguments are an anti-pattern; consider separate methods for complete() (#54)

[paymentrequest] Clarity on Currency Conversion (#19)

[paymentrequest] Combine API parameters into a single request object + options (#41)

[paymentrequest] Conflation of manifest + payments seem unnecessary (#70)

[paymentrequest] Constructor should not include "total" in list of items (#68)

[paymentrequest] Merchant requesting arbitrary data from the UA (#16)

[paymentrequest] No mention of non-decimal currencies (#40)

[paymentrequest] Overridng Common Payment Instruments (#21)

[paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66)

[paymentrequest] Payment instrument installation is platform-dependent (#5)

[paymentrequest] Redirect specs to the Web Payments WG versions (#69)

[paymentrequest] Should the Payment Request API only be available in a top-level browsing context? (#30)

[paymentrequest] Should the web page be able to provide status information before calling complete() (#32)

[paymentrequest] Should we support a delegated state for PaymentRequest? (#33)

[paymentrequest] Should well-known identifiers be used for ubiquitous payment methods (#35)

[paymentrequest] Spec references are all pretty outdated (#57)

[paymentrequest] Standardizing Common Payment Instruments (#20)

[paymentrequest] Support for "enrollment" use of API (#43)

[paymentrequest] Use [SecureContext] instead of manually checking inside the PaymentRequest constructor (#58)

[paymentrequest] Use navigator.payments rather than creating a new object instance (#42)

[paymentrequest] What is the format for payment method identifiers for distributed extensibility (#34)

[paymentrequest] Write-up proposal for shipping address fields (#28)

[webpayments] ACTION: Summarize arguments for/against shipping address capture (#72)

[webpayments] Adding registration proposal (#113)

[webpayments] Gh pages (#109)

[webpayments] How are cloud-based payment apps supported? (#16)

[webpayments] How are payment apps registered? (#14)

[webpayments] How are payment apps shared between different browser brands? (#15)

[webpayments] How are third-party native wallets integrated? (#42)

[webpayments] How can the API support enrollment (future payment) use cases? (#65)

[webpayments] How do organizations layer additional information in the core messages? (#18)

[webpayments] How do we ensure that the payment request from the merchant is not tampered with before it gets to the payment app? (#19)

[webpayments] How do we protect certain data in the messages from certain parties in the flow as the use case requires? (#78)

[webpayments] How should the message schemas for the payment request and response be defined? What is the extensibility story for the messages? (#27)

[webpayments] Is tracking payment request state necessary? (#35)

[webpayments] Merge Payment Request Architecture with Capabilities Document (#22)

[webpayments] Multilingual Support for human-readable labels (#84)

[webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)

[webpayments] Payment Request Architecture glossary should include IG glossary (#23)

[webpayments] Registration: App supports method but user has no instrument for that method (#110)

[webpayments] Registration: How is registration information updated? (#111)

[webpayments] Registration: Should we support payee knowing user has payee-controlled payment app? (#112)

[webpayments] Should a payment method identifier (URL) resolve to a machine readable resource that describes the payment method? (#30)

[webpayments] Should a Payment Request API have shipping address APIs? (#39)

[webpayments] Should a payment request be just data, or a programmable object? (#36)

[webpayments] Should a website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#66)

[webpayments] Should list of accepted payment methods be strings or objects? (#37)

[webpayments] Should Payment Method Identifiers and Messages be expressed using a Linked Data Vocabulary? (#29)

[webpayments] Should the payment request contain line item details? (#38)

[webpayments] Should the payment request support multiple pricing options? (#79)

[webpayments] Should we be concerned about the use of the Browser API in a non-HTTPS environment? (#20)

[webpayments] Should we expose status change events in the browser API? (#41)

[webpayments] Should we have separate specifications for payment and registration of payment apps? (#26)

[webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76)

[webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95)

[webpayments] Taler flows (#106)

[webpayments] What are the WPWG February 2016 face-to-face prioritized issues (#89)

[webpayments] What is the appropriate conversational pattern for the API? (#55)

Blog post on WPWG meeting and next steps

Call for consensus update

Final editors' draft

Important telecon on Thursday 17th March at 16h00 UTC (12pm EDT, 9am PDT, 4pm GMT,

Issue updates based on WPWG FTF discussion - please be sure to add any others you have in mind

New list: public-webpayments-specs@w3.org to mirror spec repo notifications

Telcon 3rd March 17h00 UTC

The Web Browser API Incubation Anti-Pattern

Update on getting to a Call for Consensus

Updates to "Payment Request API Architecture"

wpwg-ACTION-13: Create poll for f2f days at tpac 2016

wpwg-ACTION-14: Look at dates when worldpay could host a meeting

wpwg-ACTION-15: Review payment request api spec by march 15th 2016 (and attempt to do the other ones as well).

wpwg-ACTION-16: Reach out to wg participants to secure reviews

wpwg-ACTION-17: Submit a pr for http api into the proposals folder for the wpwg repo.

Last message date: Thursday, 31 March 2016 19:35:37 UTC