Agenda 20160121
Pages 87
- Home
- A Payments Initiation Architecture for the Web
- Adoption2017
- Agenda 12th November 2015 at 1700 UTC
- Agenda 17th December 2015 at 1700 UTC
- Agenda 19th November 2015 at 1700 UTC
- Agenda 20160107
- Agenda 20160121
- Agenda 20160128
- Agenda 20160204
- Agenda 20160211
- Agenda 20160310
- Agenda 20160317
- Agenda 20160331
- Agenda 20160407
- Agenda 20160414
- Agenda 20160421
- Agenda 20160428
- Agenda 20160505
- Agenda 20160512
- Agenda 20160519
- Agenda 20160526
- Agenda 20160602
- Agenda 20160609
- Agenda 20160616
- Agenda 20160623
- Agenda 20160728
- Agenda 20160804
- Agenda 20160811
- Agenda 20160818
- Agenda 20160825
- Agenda 20160901
- Agenda 20160908
- Agenda 20160915
- Agenda 20161006
- Agenda 20161020
- Agenda 20161027
- Agenda 20161103
- Agenda 20161110
- Agenda 20161117
- Agenda 20161201
- Agenda 20161208
- Agenda 20161215
- Agenda 20170105
- Agenda 20170112
- Agenda 20170119
- Agenda 20170126
- Agenda 20170202
- Agenda 20170209
- Agenda 20170216
- Agenda 3rd December 2015 at 1700 UTC
- Agenda for 3rd March telco
- All in the Browser
- Browser with remote Payment Apps
- Call for Consensus FPWD
- CFC_20140412
- Checkout API
- Components
- DeploymentExamples
- Extensibility_Notes
- F2F Agenda
- FTF March2017
- FTF Sep2016
- How it Works
- How the Working Group works
- Issue Summary
- MagWebinar
- Meeting Proposal 20161128
- Meetings
- Mobile Platform
- Networks List
- PaymentApp_Notes
- PaymentRequestFAQ
- PMI_Notes
- Proposed F2F Day 2 agenda
- RegistrationTypes
- Security and Privacy Considerations
- Spec_Notes
- Support for multi price and currency
- Synchronizing Github Issues with W3C Mailing Lists
- TestSuite
- TPAC 2015 issues list
- Web Payment Deployment Examples
- Web Payments Working Group FTF Meeting (July 2016)
- Web Payments Working Group Plan
- WPWG FTF Feb 2016
- WPWG FTF Feb 2016 Requirements
- Show 72 more pages…
Mailing list archives
Issues
- General
- Payment Request API
- Payment Method Identifiers
- Basic Card Payment
- Payment Apps API
- HTTP API and Messages
Tests
Adoption
Previous Topics
Clone this wiki locally
Update from the flows task force (Matt)
Update on the work being done to prepare a vocabulary based on ISO20022 (Vincent/Laurent)
Update on wiki changes (Doug)
Update on request for input from the TAG (Adrian)
Preparation for the FTF (Ian)
Explanation of process for bringing proposals to calls to resolve issues (Adrian)
-
Current proposals
PROPOSAL: Hold WG meetings every week until further notice. (Adrian)
https://github.com/w3c/webpayments/issues/58PROPOSAL: Use strings to represent currency and amount per ISO20022 (Adrian)
https://github.com/w3c/webpayments/issues/57PROPOSAL: Adopt ISO20022 terminology for payer and payee and use synonyms as appropriate (Adrian)
https://github.com/w3c/webpayments/issues/62PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (Manu)
https://github.com/w3c/webpayments/issues/63PROPOSAL: The PaymentRequest object will not have code attached to it. It will be a pure data object. (Manu)
https://github.com/w3c/webpayments/issues/64
AOB
Please review the two proposals tabled before the meeting if possible to save time in getting up to speed. If you are unable to make the call you may express your support or not for the proposals by providing a +1 (or -1) in the comments on GitHub (or via email reply to the proposal) beforehand.