WPWG Plan 2019

Status

This is a draft document for discussion.

This document does not include:

• ongoing discussion of feature enhancements for after PR API 1.0

Goals

1. Interoperability
2. Adoption
3. 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

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)

Action	Owner	Due	Notes
Work on secure modal window proposal	Adrian, Marcos
Get TAG review of proposal	Rouslan		See TAG issue 472
Get WICG review of proposal

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

2. Adoption Objectives

• Payment Handlers
  • Major payment service providers experiment with a Payment Handler
  • Organize a hackathon in the Bay Area (January 2020)
  • Organize a hackathon in Europe (March 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
Seek Stripe data	Jeremy Wagemans		Action from TPAC 2019

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
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 the Bay Area (January 2020)

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			May be joint project with MAG.

Organize a hackathon in Europe (March 2020)

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		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

• Revise charter

Revise Charter

Action	Owner	Due	Notes
Create draft	Ian	17 October
Get WG review	co-Chairs	14 November
Call for Consensus	Ian	Ends 27 November
Get W3M Review	Ian	4 December
Get AC Review (with extension)	W3C Communications Team	15 December