Main Page/FTF June2015/Deployment

Goals

W3C creates technical specifications that must demonstrate interoperability. This means we need people to implement and deploy the technology. The goals of this session are:

• To understand parties critical to adoption of new standards.
• Identify important obstacles to success (technical, legal such as contracts, regulatory)
• To brainstorm about how we can set up an experimental program as part of W3C process requirements to secure implementation experience.

Implementation Considerations

• Dave Raggett will speak about implementation considerations for payment agents that are in-browser or native or cloud-based, and what that implies about involvement by different parties and deployment strategy. The focus of this work will not include
  • in-app payments, and
  • point of sale / mobile payments.
• What versioning system might be useful to help achieve goals (communicating work, evolution of payment features supported by the platform)?

How can we set up a program for early adopters?

For integration

Notes from Manu:

• 3 major online retailers launching Web Payments support (for example: Alibaba, Walmart, Target, Best Buy, Overstock.com, Amazon, Tesco, or eBay)
• 1-2 large online payment companies (or banks) launching Web Payments support (for example: Google Wallet, PayPal, Alipay, Bank of America, HSBC, US Fed)
• 5-10 smaller players from the online retail space and the payments space
• Success would look like:
  • 1 million payments within the first year after standardization
  • Favorable reviews by the Web developer community

For Security

@@

For Credentials

@@

What are obstacles to success?

• How do you experiment with a payments system?
• Are there ecosystem-specific challenges (e.g., may be one thing in card networks, something else in different ecosystem)

What would help achieve success?

• Do we need a marketing campaign to convince people to use the new technology?
• Development of transition plans to facilitate adoption by existing ecosystems?
• Would alignment with other initiatives (e.g., strategies for improving payments) help drive adoption?
• Are there labs (e.g., in selected retailer/bank) we can work with to set up an experiment as part of rolling out?
• Would submitting specifications to ISO in this space help drive deployment?
• For features that require browser support, will browser vendors work together on a javascript library that adds support?
• What help can we get from regulators? Are there key hooks that must be part of V1 or we will not get support?
• Mark Tiggas spoke of bodies who cooperate to voluntarily adopt ISO standards. To whom should we reach out?

Observations from Manu

• Do not try to do anything that does not already have a prototype
  • Inventing something new in version 1 would increase the risk of failure to an unacceptable level
• Do not require new hardware to be deployed
  • We need to be able to deploy and iterate rapidly
• Do not try to support both cloud and local wallets
  • There may be a protracted fight on who provides the "message bus" - the browser or the OS?