Warning:
This wiki has been archived and is now read-only.

Communications Strategy Task Force

From Web Commerce Interest Group
Jump to: navigation, search

Pat Adler and Ian Jacobs are working on a communications strategy for the Web Payments Interest Group. This is draft material and has not been discussed by the group or approved. Questions? Please contact Ian Jacobs <ij@w3.org>.

Participants: Pat, Ian, Nick Telford-Reed

Goals

  • Drive payments industry acceptance of the the value of the Open Web Platform for achieving some of their goals for ubiquity, security, and usability, as expressed in the use cases developed by industry representatives.
  • Help the group create deliverables that are understandable and useful to both payments industry specialists and the Web community at W3C.

Audiences

  • Payments industry
  • W3C Working Groups

Industry Segments and Interests

Stakeholders User Wallet Merchant Wallet Transaction description Digital Receipt Transaction flow (more generally interaction with Payment systems) (API+Protocol+Vocab) Identity (and privacy) Authentication Others
Banks X X X X X X X anti-fraud data, ALM/regulation data, user data (basket content, etc.)
Payment Service Providers 0 0 X X X X X anti-fraud data, AML/CFT/Regulation data
Merchants 0 X 0 0 X X X loyalty card, coupons, user data, etc;
Internet + mobile companies X 0 X X X X X

More resources

Timeline

See also relevant confs for the IG

  • February
    • 25: Present draft of strategy to Interest Group as well as first draft of executive summary
  • March
    • 25: Slide deck on Use Cases available
  • April
    • Early: Publish first payments interview
    • 3: Call for consensus to publish FPWD of use cases (until 10 April)
    • 7: Glossary available from Evert for inclusion in use cases
    • 10: FPWD of use cases transition request
    • 13: FPWD of use cases publication reuqest
    • 16: Publication of FPWD of use cases
    • 21: Talk at Payments 2015 on standards
    • 26-30: Connexxus 2015 in Annapolis
    • 27: W3M review of advance notice plan
    • 29: Send work plan (advance notice) to AC and let them know about ftf meeting and roundtable in NYC
  • May
  • June
    • 16-18: IG FTF meeting and roundtable
    • Mid: First Public Working Draft of Payment Agent architecture vision
    • 26 June: Share draft charters with W3M; start to socialize draft charters publicly and raise awareness among key groups
  • July
    • 29 July: W3M approves N charters for AC review
  • August
    • 3 August: AC review of charters until 14 September
      • Publish revised (and stable) use cases, architecture
      • Set expectations that there will be ftf metings in Sapporo if the groups are approved.
  • September
    • 28:
      • Launch N WGs with press release
  • October
    • 26-30: W3C TPAC 2015 in Japan
      • FTF meetings of IG + 3 WGs. One idea is to have 1 day per group. Although each group meets less, we think there will be many of the same participants so overall they will have a lot of time together.

Goal: Acceptance

Messages

Messaging Notes

  • Scope?
    • Standardize transactions between payers and payees. Get an ecosystem to support payment instruments in a harmonious way.
    • Standardize basis for a universal payment instrument; they typically talk about regulation.
  • Security and privacy and transparency
  • Increased security, privacy
  • Cross platform interoperability
  • Cross boundary jurisdiction support
  • Data Portability
  • Opportunities for different stakeholders to add value
  • Reduce hops
  • Faster payments
  • Convergence of online and in-store
  • Avoid vendor lock-in
  • Improve interop across platforms (native and Web)
  • Making it easier to move value between different networks.
  • Payment technology agnostic
  • Question: Do we need more messaging on cryptocurrencies?
  • Relate to application foundations

Topics to cover

  • Push/pull
  • Integration with existing standards and terminology
  • Possible requirements on topics such as
    • Repudiability
    • Support for legally binding digital services
    • Regulatory requirements
    • Auditibility

Pain points

  • How do you bridge the gap between merchant instruments supported by merchant and available to users?
    • Merchant will have easier time providing ecommerce solutions because they will only need to invoke the payment agents, which will in turn manage the security, identity, compliance, and other aspects of the communications with the payment processor. This will make it much easier for merchants to adopt payment schemes for their customers and lower their maintenance costs. This will also foster innovation in payment instruments as merchant acceptance increases (due to lower integration cost).
  • 1 extra second at the POS costs $12M (get more precise statement from Mario)

Content Development

White papers, summaries, etc.

  • Executive summary
  • Piece on relevance of this work (value proposition) to different industry segments
  • Piece on how this work relates to the work of external groups
  • Multiple pieces on relevance of this work in different regions of the world
    • This could also be achieved through participant blog posts.
  • Videos?

Technology Road Map

  • See W3C's Mobile Roadmap as a model; can do the same thing for payments once we have identified key technologies (existing or proposed).

Group Blog

  • Group blog
    • Encourage each participant to write a few paragraphs on what they want out of the group and key topics of interest to them individually.
    • Make sure blog comments are on.
  • Regular blog post from Erik on what's going on in the world and how it relates to the work of the group.

Interviews

Dissemination and Socialization

Collateral

  • (Updated) Printed flyer
  • Slide decks for use cases, payment agent presentations
  • Diagrams (especially web payment architecture)

Media Outreach

Conferences and events

  • See Relevant Conferences for the IG
    • Sharing events periodically with group / hearing about other events
    • Sharing the responsibility of public communications / travel to events

W3C Groups

  • Tech talk for sharing with other groups inside W3C

Industry Relations

  • Quarterly liaison calls with key external groups?
  • Work with group participant departments (PR, industry outreach)
  • Tweet when organizations join with tag #webpayments

Webinar

  • Possibly March 2015 time frame; to be discussed

Goal: Clear Deliverables

  • Review deliverables for clarity (to both industry and Web community)
  • Develop a visual identity system for the work.
    • Graphics?
    • Logo for Web payments?