from February 2016 by subject

[Minutes] 18 Feb WPWG call

[Minutes] 23-24 February face-to-face meeting

[Minutes] 4 Feb 2016 WPWG teleconference

[paymentrequest] "JSON object" is confusing; consider "JSON-serializable object" (#59)

[paymentrequest] Add link to registration explainer to index page. (#65)

[paymentrequest] Add rationale and update document locations (#62)

[paymentrequest] Add registration explainer (#64)

[paymentrequest] Add skeleton of basic card spec and tidy-up API spec (#63)

[paymentrequest] Algorithm for complete(success) does not use its argument (#55)

[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] Change the PaymentRequestUpdateEvent model to better match FetchEvent (#50)

[paymentrequest] Clarify that decimal separator is optional to match regex. (#49)

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

[paymentrequest] Consider allowing a web site to provide a label for the "Buy" or "Checkout" button (#46)

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

[paymentrequest] Don't have a <dfn> for "user agent" (#60)

[paymentrequest] Error types used are weird and excessive (#56)

[paymentrequest] Example 1 typo: payment.complete(true) should be paymentResponse.complete(true) (#53)

[paymentrequest] Fix spec nits based on implementation experience. (#51)

[paymentrequest] Need a "really closed" event (#45)

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

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

[paymentrequest] Proposal to move the complete() method to the PaymentResponse interface (#48)

[paymentrequest] Shipping: should merchant supply supported destinations (#2)

[paymentrequest] Spec correctness updates based on review feedback (#47)

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

[paymentrequest] State in each class's definition which internal slots it has (#61)

[paymentrequest] Tidy-up per discussion (#52)

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

[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)

[web-payments-browser-api] Use of "MUST" in sentence might cause confusion (#6)

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

[webpayments] Added Credit Transfer clarifications (#98)

[webpayments] Changes based on discussion with Ian Jacobs (#85)

[webpayments] Consolidate updated from Freed into single file (#86)

[webpayments] Consolidate updated from Freed into single file (#87)

[webpayments] Consolidate updated from Freed into single file (#88)

[webpayments] Expression of monetary amounts (#40)

[webpayments] Fix typos (#91)

[webpayments] Flow terminology (#92)

[webpayments] Gh pages (#101)

[webpayments] Gh pages (#105)

[webpayments] Gh pages (#107)

[webpayments] Gh pages (#108)

[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 we prevent keyboard hooking during payment? (#90)

[webpayments] How do we protect certian 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? (#27)

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

[webpayments] ISO20022 terminology adoption (#93)

[webpayments] Minor Changes (#104)

[webpayments] Minor fixes/annoatations (#96)

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

[webpayments] PISP under PSD2_SCT flows_Merchant PISP.pml (#97)

[webpayments] PISP under PSD2_SCT flows_Shopper PISP (#99)

[webpayments] PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP. (#83)

[webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77)

[webpayments] PROPOSAL: The PaymentRequest object SHOULD NOT expose internal state information to the developer. Any design that requires developers to manage or understand the request state is a compromise in the API design that should be avoided where possible. (#64)

[webpayments] PROPOSAL: Use strings to represent currency and amount per ISO20022 (#57)

[webpayments] PSD2 about Payment Initiation 4 Feb 2016 (#82)

[webpayments] Removed Spaces From File Name (#102)

[webpayments] Repo my apps (#103)

[webpayments] Returned Skin to default, moved target flows out of directory structure, removed partial flows for SEPA Credit Transfer (#80)

[webpayments] Review: UPI - a method and standard that went BETA in India (#100)

[webpayments] Security and Privacy Self-Review (#61)

[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 website be able to provide a label for the "Buy" or "Checkout" button displayed in the payment app? (#66)

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

[webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60)

[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] Some amendmends (#75)

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

[webpayments] Taler flows (#106)

[webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59)

[webpayments] Transition and Adoption (#94)

[webpayments] Updated card participants for ISO20022 (#81)

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

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

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

ACTION STRONGLY ENCOURAGED: Flows ready for wider review

AGENDA for our call February 11th 2016 at 17h00

CHANGE OF VENUE: Sunday dinner now at La Mar Cebichería Peruana at 7:30pm

Checkout API

Checkout API spec published

Comments on 3DS Flow

Comments on MasterPass flow

Comments on Payment Request API

Concerns around Web Payments HTTP API de-prioritization

Dinner at Croqueta on Sunday at 7pm in San Francisco

Draft of PaymentRequest Registration Doc Available

Draft requirements for discussion at the WPWG FTF meeting

Face to face - some important reading

interested in JSON-LD

JSON signatures for "node.js"

JSON Signatures for Financial Messaging

Meeting today

New PaymentRequest Doc

PROPOSAL regarding JSON-LD material

Question about I18N comment [Was: Checkout API spec published]

Registration for ILP Workshop is OPEN

Sanity check on API using flows from Flows Task Force

Some things that might help with PROPOSAL regarding JSON-LD material

Telecon 4th February 2016 at 17:00 UTC

The Open Banking Standard (HTTP API)

Under W3C Member Review: Hardware Security Working Group Charter (until 1 April)

Web Authentication Working Group Launched

Last message date: Monday, 29 February 2016 21:50:31 UTC