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

[Agenda] 14 April 2016 WPWG teleconference

[Agenda] 21 April 2016 WPWG teleconference

[Minutes] 14 April 2016 WPWG teleconference

[Minutes] 28 April WPWG teleconference

[Minutes] 7 April 2016 WPWG teleconference

[w3c/webpayments] ACTION: Refactor flows to use common terminology and entry/exit points (#49)

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

[w3c/webpayments] Add Web Payments CG HTTP API specification to list of proposals. (#115)

[w3c/webpayments] Add Web Payments Core Messages spec to proposals. (#119)

[w3c/webpayments] Apply review comments by Ian Jacobs to HTTP API. (#120)

[w3c/webpayments] Confusion over payment flow (#10)

[w3c/webpayments] Create an FAQ (#114)

[w3c/webpayments] Document relationship diagrams? (#24)

[w3c/webpayments] Fix section indents on Arch proposal (#127)

[w3c/webpayments] Gh pages (#118)

[w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)

[w3c/webpayments] How do we prevent keyboard hooking during payment? (#90)

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

[w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)

[w3c/webpayments] Minor HTML typo on Arch proposal (#126)

[w3c/webpayments] New Architecture Proposal (#125)

[w3c/webpayments] Payment Methods vs Payment Instruments (#124)

[w3c/webpayments] Proposal for a Payment Apps spec (#116)

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

[w3c/webpayments] Proposals should be marked as unofficial (#121)

[w3c/webpayments] Proposals should be marked as unofficial (#122)

[w3c/webpayments] Proposals should be marked as unofficial (#123)

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

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

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

[w3c/webpayments] Should we be publishing a specification for an HTTP API? (#17)

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

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

[w3c/webpayments] Transition and Adoption (#94)

[w3c/webpayments] Update reference labels to match other docs (#117)

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

Agenda for Thursday 7 April WG call

API complexity

Basic CT-DD Payment.doc

Call for Exclusions: Payment Request API; Payment Method Identifiers

Call for Participation - making it a little easier to contribute

Call for Review: Proposals for discussion on 21 April

Call for reviews of HTTP API and Core Messages proposals

Call to Review - Get involved

CfC to publish documents as FPWD of the Web Payments WG

Comments on Web Payments HTTP API 1.0

Communications plans and activities you can do around FPWDs on 21 April

Decision [Was: CfC to publish documents as FPWD of the Web Payments WG]

Draft FAQ to accompany FPWDs - comments welcome

Face to face

Fwd: Spec-Ops Comments on Web Payments Core Messages 1.0

Fwd: Spec-Ops comments on Web Payments HTTP API 1.0

Fwd: Transition Request for 3 Payments Specifications

Heads up on HTTP API and Core Messages chats

Notes on Payment Apps (registration, etc.)

On Three Addresses [Was: CfC to publish documents as FPWD of the Web Payments WG]

Payment logic in the Browser (was Re: CfC to publish documents as FPWD of the Web Payments WG)

Payment Method Identifiers

Priorities (was: Re: Proposed agenda for our call tomorrow (28th April at 16h00 UTC))

Proposed agenda for our call tomorrow (28th April at 16h00 UTC)

Reminder: Deadline today at 1pm ET [Was: CfC to publish documents as FPWD of the Web Payments WG]

RES: CfC to publish documents as FPWD of the Web Payments WG

Review of Payment Apps Proposal

Security of the solution. Re: CfC to publish documents as FPWD of the Web Payments WG

Three Web Payments FPWDs published

Transition Request for 3 Payments Specifications

Two high-level comments on "Payment Apps" draft

Update of CfC - Negative amounts

Update on getting to a Call for Consensus

Updated "How the Working Group works"

Updates to work process

WPWG Priorities

wpwg-ACTION-18: Review extensibility wiki by april 20th.

wpwg-ACTION-19: Review the extensibility wiki by 21 april

答复: CfC to publish documents as FPWD of the Web Payments WG

Last message date: Friday, 29 April 2016 14:30:59 UTC