Agenda 20160602
Adrian Hope-Bailie edited this page Jun 2, 2016
·
3 revisions
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
Face to face
GitHub
- All specs now in own repos
- Post issues to appropriate list
- Same labels, milestones etc
Specifications
- Payment Method Identifiers - https://github.com/w3c/webpayments-method-identifiers
- Payment Request API - https://github.com/w3c/browser-payment-api/
- HTTP API - https://github.com/w3c/webpayments-http-api
- Payments Core Messages - https://github.com/w3c/webpayments-core-messages
Payment Method Specifications
- Card - https://github.com/w3c/webpayments-methods-card
- Credit Transfer and Direct Debit - https://github.com/w3c/webpayments-methods-credit-transfer-direct-debit
Proposed Specifications
Question
- Where to put architecture ED?
Issues
Payment Methods (Identifiers and Payment Method Specific Data)
- A use case for pricing per payment method - @mattsaxon
- The need for grouping semantics in payment methods and therefor the data
- The UX challenge (users select a payment app not a payment method)
- Browser API Issue #4 Should it be possible to vary amounts depending on payment method?
- Browser API Issue #3 Should it be possible to provide amounts in more than one currency?
- Browser API Issue #157 Should the payment mediator pass all payment method data to the payment app or just relevant data?
- PMI Issue #1 Should we define nesting/grouping semantics for payment method identifier matching?
- PMI Issue #2 PROPOSAL: Use query string parameters for PMI matching