public-payments-wg@w3.org from December 2015 by subject

[admin]

[Architecture] Updated wiki to address some comments

[Feb 2016 FTF meeting] Nearby hotels

[Minutes] 3 Dec 2015 WPWG meeting

[paymentrequest] Added initial spec drafts and architecture overview. (#24)

[paymentrequest] API needs equivalent of PassKit's paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)

[paymentrequest] API needs equivalent of the paymentAuthorizationViewController:didAuthorizePayment:completion: callback (#23)

[paymentrequest] Can we call out how this relates to other payment efforts? (#6)

[paymentrequest] Chain of trust between browser and merchant (#9)

[paymentrequest] Clarity on Currency Conversion (#19)

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

[paymentrequest] Could we design appropriate declarative models to go along with the API? (#13)

[paymentrequest] Currency Specification (#18)

[paymentrequest] CurrencyAmount description has exponent sign wrong (#39)

[paymentrequest] Do we need to support transactions that aren't finalised by the merchant in v1? (#3)

[paymentrequest] First set of API refactoring changes. (#26)

[paymentrequest] How do we think it will work with ServiceWorker? (#12)

[paymentrequest] Let merchant pass in arbitrary data to payment request? (#11)

[paymentrequest] Location of Authorisation in the flow (#22)

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

[paymentrequest] Overridng Common Payment Instruments (#21)

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

[paymentrequest] Payment instruments not supported by proposal (#10)

[paymentrequest] Payment methods registering to handle schemes / Interledger support (in the future) (#14)

[paymentrequest] Price breakdown (#25)

[paymentrequest] Reconsider the need to include shipping in this spec (#8)

[paymentrequest] Second set of API refactoring changes (#37)

[paymentrequest] Should the Payment Request API only be available in a secure context? (#29)

[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] Standardizing Common Payment Instruments (#20)

[paymentrequest] There should be a way for the merchant to indicate the instrumentResponse was a failure (#15)

[paymentrequest] UI for Payment Instrument (#17)

[paymentrequest] Update API document with missing details (#38)

[paymentrequest] Update explainer.md (#7)

[paymentrequest] Updated documents to ensure all issues notes link to issue in the repo. (#36)

[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 initial proposal for card payment method spec (#31)

[paymentrequest] Write-up initial proposal for payment app registration spec (#27)

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

[webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)

[webpayments] Abstract payment architecture (#11)

[webpayments] Added Apple Pay (#44)

[webpayments] Added PSP Hosted Card Payment (#32)

[webpayments] Confining the definition of user agents to browsers (#34)

[webpayments] Document relationship diagrams? (#24)

[webpayments] Expression of monetary amounts (#40)

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

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

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

[webpayments] How are payment messages trusted? (#19)

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

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

[webpayments] Is there an HTTP API based message flow? (#17)

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

[webpayments] Machine readability of payment methods? (#30)

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

[webpayments] Minimum necessary information for merchant to process payment (#27)

[webpayments] No proprietary binary files, please (#7)

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

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

[webpayments] Refined SEPA Credit Transfer to add the web interactions (#33)

[webpayments] SDD one off e-mandate (#43)

[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 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 Payment Method Identifiers be a Linked Data Vocabulary? (#29)

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

[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] Splitting registration from payment (#26)

[webpayments] Uploaded Credit Transfer files for Cyril (#21)

[webpayments] What gets registered - apps, wallets, or payment instruments? (#28)

[webpayments] What is the use case for the Payment Details object? (#38)

[WPAY WG] Additional ANSI standards for Authentication(X9.122) added to WatchDox

Agenda for tomorrow's call

Experimental glossary definitions added

Linking the Wiki to the example Flows

Meeting 3rd December at 17:00 UTC

New landing page for Google/Microsoft paymentRequest() API

New wiki article: TPAC 2015 issues list (was RE: wpwg-ACTION-8: Move google docs list of issues to github wiki)

Scheduled: February 2016 Web Payments Working Group FTF

wpwg-ACTION-10: Integrate standard flow into web payments cg's browser api spec.

wpwg-ACTION-9: Share iso20022 glossary/terminology

Last message date: Wednesday, 30 December 2015 14:28:57 UTC