Agenda 20160211
Adrian Hope-Bailie edited this page Feb 11, 2016
·
2 revisions
Pages 55
- Home
- A Payments Initiation Architecture for the Web
- 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 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
- How it Works
- How the Working Group works
- Issue Summary
- MagWebinar
- Meetings
- Mobile Platform
- PaymentApp_Notes
- PaymentRequestFAQ
- PMI_Notes
- RegistrationTypes
- Spec_Notes
- Support for multi price and currency
- Synchronizing Github Issues with W3C Mailing Lists
- 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 40 more pages…
Mailing list archives
Current Work
Issues
Clone this wiki locally
Our proposed agenda for the call on 11th February 2016 at 17h00 UTC
Flows update [Matt Saxon]
Checkout API [Dave Longley/Manu Sporny]
-
PROPOSAL: Include an extensibility section in the browser API spec with an ISSUE marker indicating WIP.
https://github.com/w3c/webpayments/issues/83
Email threadPROPOSAL: Pass the list of supported payment methods and the method-specific data in a single object
https://github.com/w3c/webpayments/issues/77PROPOSAL: 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.
https://github.com/w3c/webpayments/issues/64
Update on upcoming F2F [Ian Jacobs]