This is a draft document for discussion about plans from Q4 2019 through 2020.
This document does not include:
Interoperability
Adoption
Rechartering
1. Interoperability Objectives
Specifications
Payment Request 1.0 advances to Proposed Recommendation
SRC payment method advances to FPWD
Payment Handlers
All major browsers add support for payment handlers (through PH API or other)
Security
Web Authentication works for payments use cases
Other considerations:
Do we need a 3DS module? Tokenization module?
Privacy discussions (3DS and trust tokens) happening in the WPSIG.
Do we need to spec JIT installation and skip-the-sheet at a high level for consistent UX?
Payment Request 1.0 advances to Proposed Recommendation
Note : At the 31 October 2019 WPWG teleconference we discussed delaying the advance to Proposed Recommendation to get more adoption first.
Action
Owner
Due
Notes
Webkit update for 813
Andy Estes
Andy indicated he would work on this mid-September (during TPAC)
Address pull request 873
Chairs/Ian
Cf TPAC discussion
Request updated test results
Ian
Create accurate implementation report
Ian
Will require hand edits to less-than-two to remove noise
Call for Consensus
Ian
Transition Request
Ian
Publication Request
Ian
All major browsers add support for payment handlers (through PH API or other)
SRC payment method advances to FPWD
Action
Owner
Due
Notes
Complete data model definition
Card Payment Security Task Force
Transform wiki to respec
Ian
Instrument-level display of instruments
Chrome team
This may not require changes to Chrome or the specification. However, a one-instrument-per-ph approach raises issues about how to add a new card and to do just-in-time handler installation
Delegation of data requests to payment handler
Chrome team
See delegation explainer
Browser default payment handlers
Chrome team
See blog post description
Address identity management, multiple authentications
Card Payment Security Task Force
Solicit EMVCo review
Bastien
Call for Consensus
Ian
Transition Request
Ian
Publication Request
Ian
Web Authentication works for payments use cases
Action
Owner
Due
Notes
Create joint task force with Web Authentication WG regarding TLD+1 and delegation
Tony Nadalin
Launched 31 October 2019
Payment Handlers
Major payment service providers experiment with a Payment Handler
Organize a hackathon in the Bay Area (January 2020). We decided only in Europe for now.
Organize a hackathon in Europe (April 2020)
Publicize payment handler benefits
Platforms
Gain support by two more PSP platforms for Payment Request API natively
Merchants
Publish adoption trend data
Compile a list of features required for a MVP (POC)
Launch a Merchant Business Group
Create resources for merchants to easily create superior checkout experiences
Socialize these resources and the technology with more merchants
Users
Reduce user surprise in the UX
Other ideas:
Put in place an incentive program (e.g., a grant) to spur payment handler development.
Major payment service providers experiments with a Payment Handler
Action
Owner
Due
Notes
Sync with major payment service providers
Ian
TPAC follow-up. Secure participation in a hackathon
Publish adoption trend data
Action
Owner
Due
Notes
Seek Google data
Justin Toupin
Mid-October
Action from TPAC 2019. Outcome: no data available yet!
Seek Stripe data
Jeremy Wagemans
Action from TPAC 2019. Outcome: no data available.
Compile a list of features required for a MVP (POC)
Action
Owner
Due
Notes
Speak with merchants 1-on-1
Ian
Gain support by three more PSP platforms for Payment Request API natively
Action
Owner
Due
Notes
Sync with Magento
Justin
Sync with Adyen
Ian
Launch a Merchant Business Group
Action
Owner
Due
Notes
Develop Merchant BG Plan
Alan Bird and Ian Jacobs
Organize a hackathon in Europe (April 2020)
Scheduled for 1-2 April in Dublin
Notes on participation:
Have a UX component (e.g., UX experts and/or ordinary users providing feedback)
Notes on deliverables:
Merchant requirements (e.g., on browser UX or functionality)
Demos / videos. These should be shared within companies to help socialize adoption, and see whether the APIs align with business requirements or what would need to change.
Action
Owner
Due
Notes
Develop Hackathon Plan
Alongside FTF meeting in Europe
Create resources for merchants to easily create superior checkout experiences
Action
Owner
Due
Notes
Research what materials would be useful
Merchant Business Group
Note existing documentation on MDN
Socialize these resources and the technology with more merchants
Publicize payment handler benefits
Action
Owner
Due
Notes
Write a blog post about payment handler benefits
Justin Toupin and Ian
Done 2019-10-29, see Payment Handler Value Proposition
See discussion at TPAC as starting point
Reduce user surprise in the UX
Action
Owner
Due
Notes
Explore alternatives to the sheet
Adrian Hope-Bailie
Support alignment between merchant and sheet styles
3. Rechartering Objectives
Action
Owner
Due
Notes
Create draft
Ian
17 October
Done.
Get WG review
co-Chairs
14 November
Done.
Call for Consensus
Ian
Ends 27 November
See [call for consensus](https://lists.w3.org/Archives/Public/public-payments-wg/2019Oct/0021.html) and [decision](https://lists.w3.org/Archives/Public/public-payments-wg/2019Nov/0016.html)
Get W3M Review
Ian
4 December
Done.
Get AC Review (with extension)
W3C Communications Team
13 December
[Announced 14 November](https://lists.w3.org/Archives/Public/public-payments-wg/2019Nov/0024.html). Review ends 13 December.