Agenda 20161006 - w3c/webpayments GitHub Wiki
- Priorities following TPAC for next 4-5 weeks
- Close issues on PR API and PMI (etc.) (led by Editors). What issues require WG attention over the next few weeks?
- Review and advance payment apps API to FPWD (led by Payment Apps task force)
- Push payments proposal (led by Roy)
- Advance test suite (led by Shane)
- Reminder of CfC for Overview until 7 Oct
- Review of payment apps spec by Max, Zach, Shane (from FTF action item).
- Issue 287: Adam Roach proposal for a user agent-generated transactionId to allow payment apps and payees to know they are referring to the same transaction.
- Review actions in WG tracker
- Manu to prepare Overview document for CFC
- AdamR to propose text about why the API can reduce need for card data storage; without any recommendations
- Roy to revise the tokenization specification based on today's feedback
- Ben to organize review of tokenization spec from EMV perspective
- Ian to clarify the language around consent (to say more about WG thinking) for security and privacy considerations
- Ian to work with AdamR on feedback (and question) to the TAG about ambiguity around what to do re: private browsing mode (IN PROGRESS)
- MaheshK to work with Ben Smith on a proposal to handle merchant query for specific payment methods
- Shane to write a pull request on what might change around error handling re: addresses
- zkoch to remove the diagram from basic card
- Zach to work with Max to revise the payment manifest proposal
- 2017 FTF meeting schedule (start discussion of location and dates).
- What months?
- Host volunteers?
If we have time:
- Should there be a default user agent behavior for PMIs that are not URLs and not recognized short strings? (E.g., just used for matching.)
- ISO 20022 data type alignment for basic card terms (cf Matt Saxon and ISO PaymentCard value types)
- Detecting if payment app is available from Mahesh
- What exactly are the requirements? "Some app available?" "Specific app available?"