This page is for information about Web Payments Working Group ideas and strategies to encourage adoption of the group's deliverables. Questions? [email protected] (archive).

Meetings

• Next meeting: 24 February at 11 ET. Meet on irc.w3.org, #wpwg. Agenda notes:
  • First two activities: developer resources, brand
  • Who wishes to get involved in each project?
  • Development of a plan / timeline.
• WebEx for recurring meeting
• Previous meeting minutes: 10 Feb, 3 Feb, 20 Jan

Plan

This is a draft plan based on the 20 January call.

Audience

• CMOs and product owners at larger merchants

Deliverables

• Developer site
• Develop the identity of this new system
  • Find a marketing friendly name so that users gain confidence in using the standard APIs to initiate payments.
  • Subsequently we can consider visual identity, a domain for resources related to this identity, etc.
• Events
  • once we arrive at a key implementation moment, organize an event to highlight interoperability
  • organize a panel at a conference
• Seek and promote adoption by one or more prominent merchants

Value proposition

Questions we are hearing

• Cf 10 Feb 2017 call

Messages from previous discussion

These are draft messages based on discussion.

• Improved user experience will increase conversions. The improved user experience across the Web will accentuate the improvement.
• It will be simpler to provide a good checkout experience
• There will also be security benefits, especially as more secure payment methods become part of the Web thanks to this standard.
• This is an investment that will continue to bear fruit moving forward as it will be easier to integrate more payment methods into the checkout experience.
• This standardization effort is backed by industry.

Background

Problem statement

• Chicken and egg
  • Users want lots of merchants to support in order to justify storing credentials.
  • Merchants want lots of users with stored credentials ready to go.
  • Initially users will not have stored credentials or registered payment apps
• This is a new system and some user education will be required; there is no familiar identity to this system (a brand problem)
• Not all browsers will support the API initially on all platforms. We need to communicate clearly how to manage the transition.
• We lack clear support materials to explain how it all fits together (or will moving forward), including third party payment apps.

Goals

• Raise awareness about Payment Request API and encourage merchant adoption.
• Gauge interest in merchant payment apps as part of the full ecosystem we are creating.

Ideas for deliverables

• Demo site
• Brand components (name, visual identity)
• Video?
• Conference participation
• Tools
• Data (e.g., about conversions)

Communications

Venues

• WPWG Member developer channels

Messages

• Different messages for different size merchants?
• What's the ROI?
  • Increasing Conversions
  • Simplicity, security
  • Control (and various benefits that go with simpler checkout)
• Third party app development (native, Web app) for merchant apps

Press and Analysts

History

• Introduction of this topic to the WPWG