Payment Method Identifiers
[Minutes] 28 April WPWG teleconference
Fwd: Spec-Ops comments on Web Payments HTTP API 1.0
Fwd: Spec-Ops Comments on Web Payments Core Messages 1.0
Call for reviews of HTTP API and Core Messages proposals
Notes on Payment Apps (registration, etc.)
Proposed agenda for our call tomorrow (28th April at 16h00 UTC)
- Priorities (was: Re: Proposed agenda for our call tomorrow (28th April at 16h00 UTC))
- Re: Proposed agenda for our call tomorrow (28th April at 16h00 UTC)
Heads up on HTTP API and Core Messages chats
[w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
- Re: [w3c/webpayments] How can a Web Based Payment App cancel the payment flow? (#128)
Call for Participation - making it a little easier to contribute
Updates to work process
Three Web Payments FPWDs published
Call for Exclusions: Payment Request API; Payment Method Identifiers
Review of Payment Apps Proposal
- Re: Review of Payment Apps Proposal
[w3c/webpayments] Fix section indents on Arch proposal (#127)
[w3c/webpayments] Minor HTML typo on Arch proposal (#126)
[w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
- Re: [w3c/webpayments] New Architecture Proposal (#125)
WPWG Priorities
[Agenda] 21 April 2016 WPWG teleconference
Communications plans and activities you can do around FPWDs on 21 April
[w3c/webpayments] Payment Methods vs Payment Instruments (#124)
- Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)
- Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)
- Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)
- Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)
- Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)
- Re: [w3c/webpayments] Payment Methods vs Payment Instruments (#124)
Fwd: Transition Request for 3 Payments Specifications
- RE: Transition Request for 3 Payments Specifications
- Re: Transition Request for 3 Payments Specifications
[w3c/webpayments] Proposals should be marked as unofficial (#123)
- Re: [w3c/webpayments] Proposals should be marked as unofficial (#123)
- Re: [w3c/webpayments] Proposals should be marked as unofficial (#123)
[w3c/webpayments] Proposals should be marked as unofficial (#122)
[w3c/webpayments] Proposals should be marked as unofficial (#121)
- Re: [w3c/webpayments] Proposals should be marked as unofficial (#121)
- Re: [w3c/webpayments] Proposals should be marked as unofficial (#121)
[Minutes] 14 April 2016 WPWG teleconference
wpwg-ACTION-19: Review the extensibility wiki by 21 april
wpwg-ACTION-18: Review extensibility wiki by april 20th.
Call to Review - Get involved
API complexity
[w3c/webpayments] Apply review comments by Ian Jacobs to HTTP API. (#120)
Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
- Re: [w3c/webpayments] Registration: App supports method but user has no instrument for that method (#110)
[w3c/webpayments] Add Web Payments Core Messages spec to proposals. (#119)
- Re: [w3c/webpayments] Add Web Payments Core Messages spec to proposals. (#119)
- Re: [w3c/webpayments] Add Web Payments Core Messages spec to proposals. (#119)
- Re: [w3c/webpayments] Add Web Payments Core Messages spec to proposals. (#119)
Comments on Web Payments HTTP API 1.0
[Agenda] 14 April 2016 WPWG teleconference
Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
- Re: [w3c/webpayments] How do we transition users and merchants from the current system to using the new API and apps? (#94)
Re: [w3c/webpayments] Review: UPI - a method and standard that went BETA in India (#100)
Re: [w3c/webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95)
- Re: [w3c/webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95)
- Re: [w3c/webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95)
- Re: [w3c/webpayments] Synonym Mapping from Web Environment Terminology to ISO 20022 Terminonogy (#95)
Re: [w3c/webpayments] ACTION: Refactor flows to use common terminology and entry/exit points (#49)
- Re: [w3c/webpayments] ACTION: Refactor flows to use common terminology and entry/exit points (#49)
- Re: [w3c/webpayments] ACTION: Refactor flows to use common terminology and entry/exit points (#49)
Re: [w3c/webpayments] Document relationship diagrams? (#24)
Re: [w3c/webpayments] Confusion over payment flow (#10)
- Re: [w3c/webpayments] Confusion over payment flow (#10)
- Re: [w3c/webpayments] Confusion over payment flow (#10)
Re: [w3c/webpayments] How do we prevent keyboard hooking during payment? (#90)
Re: [w3c/webpayments] Transition and Adoption (#94)
Re: [w3c/webpayments] Should we be publishing a specification for an HTTP API? (#17)
Re: [w3c/webpayments] PROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object (#77)
Re: [w3c/webpayments] Should the Web Payments API cater for the invoicing part of the full web purchase flow ? (#60)
Re: [w3c/webpayments] What is the appropriate conversational pattern for the API? (#55)
Re: [w3c/webpayments] Should we standardise a callback mechanism for payment apps to communicate to 3rd parties? (#76)
Re: [w3c/webpayments] How do we protect certain data in the messages from certain parties in the flow as the use case requires? (#78)
Call for Review: Proposals for discussion on 21 April
[w3c/webpayments] Gh pages (#118)
Draft FAQ to accompany FPWDs - comments welcome
[w3c/webpayments] Update reference labels to match other docs (#117)
[Minutes] 7 April 2016 WPWG teleconference
Two high-level comments on "Payment Apps" draft
Basic CT-DD Payment.doc
Payment logic in the Browser (was Re: CfC to publish documents as FPWD of the Web Payments WG)
Agenda for Thursday 7 April WG call
[w3c/webpayments] Proposal for a Payment Apps spec (#116)
Updated "How the Working Group works"
CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- RE: CfC to publish documents as FPWD of the Web Payments WG
- Security of the solution. Re: CfC to publish documents as FPWD of the Web Payments WG
- RE: CfC to publish documents as FPWD of the Web Payments WG
- RE: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- RE: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
- Re: CfC to publish documents as FPWD of the Web Payments WG
Re: [w3c/webpayments] ACTION: Summarize arguments for/against shipping address capture (#72)
Re: Update on getting to a Call for Consensus
Update of CfC - Negative amounts
[w3c/webpayments] Add Web Payments CG HTTP API specification to list of proposals. (#115)
[w3c/webpayments] Create an FAQ (#114)
- Re: [w3c/webpayments] Create an FAQ (#114)
- Re: [w3c/webpayments] Create an FAQ (#114)
- Re: [w3c/webpayments] Create an FAQ (#114)