Media Alert: Standards for Streamlined Checkout Gain Traction

Dear Media, Analysts and Friends of W3C,

W3C is pleased to announce that we are calling for broad implementation and testing of Web technologies to make online checkout easier for users and improve conversions and security for merchants.

For more information, please see the Media Advisory "Standards for Streamlined Checkout Gain Traction” here and text version below:
https://www.w3.org/2017/09/payments-media-advisory.html.en

For more information or to arrange interviews, please contact: 
w3t-pr@w3.org <mailto:w3t-pr@w3.org
Thank you.

Kind regards,

Amy van der Hiel
W3C Media Relations

———


[1]W3C For Immediate Release

     [1] http://www.w3.org/

  Media Advisory

           Standards for Streamlined Checkout Gain Traction

W3C Calls for Testing and Experimentation to Broaden Interoperability
    __________________________________________________________

  [2]W3C Press Release Archive
    __________________________________________________________

     [2] https://www.w3.org/Press/

  [3]https://www.w3.org/ — 14 September 2017 — The World Wide Web
  Consortium (W3C) today called for broad implementation and
  testing of Web technologies to make online checkout easier for
  users and improve conversions and security for merchants. All
  major browser makers are now implementing [4]Payment Request
  API. The [5]Web Payments Working Group encourages merchants,
  Web developers, and users to experiment with these early
  implementations and provide feedback to the group. In parallel,
  the Working Group will be expanding its [6]test suite for the
  API to help ensure browser interoperability.

     [3] https://www.w3.org/
     [4] https://www.w3.org/TR/payment-request/
     [5] https://www.w3.org/Payments/WG/
     [6] https://github.com/w3c/payment-request/blob/gh-pages/test-plan.md#test-plan--payment-request-api

Improved User Experience

  Making purchases on the web, particularly on mobile, can be a
  frustrating experience. Every web site has its own flow, and
  most require users to manually type in the same addresses,
  contact information, and payment credentials again and again.
  This can lead to shopping cart abandonment and lost customer
  loyalty. Likewise, users may abandon checkout if their
  preferred payment methods are unavailable, but it can be
  difficult and time-consuming for developers to create and
  maintain checkout pages that support multiple payment methods.

  The [7]Payment Request API (and supporting specifications)
  enable merchants to create streamlined checkout pages where
  people reuse previously stored information, saving time and
  effort and reducing error.

     [7] https://www.w3.org/TR/payment-request/

  With these technologies, users no longer complete Web forms to
  provide payment credentials, shipping information, and contact
  information. Instead, the user registers support for different
  payment methods —such as card payments, proprietary native
  mobile payments, bitcoin or other distributed ledgers, or
  credit transfers— with the browser or other user agent. During
  checkout, the browser determines which of the user's payment
  methods match those accepted by the merchant. The browser
  displays just the matches, which simplifies selection of the
  user's preferred payment application and makes the experience
  consistent across the Web. The user then chooses a payment
  method, after which the merchant receives relevant information
  through the standard API in order to complete the transaction.

Increased Conversions and Security for Merchants

  Payment Request API is expected to lower the cost of creating
  and maintaining a checkout page and increase payment security.
  The standard will make it easier to bring more secure payment
  methods (e.g., tokenized card payments) to the Web. The
  standard also means that merchants or their service providers
  can achieve a streamlined user experience without having to
  store customer payment credentials, potentially reducing their
  liability.

  For more information about using the APIs, security, and the
  relation to various rules and regulations, please see the
  [8]Payment Request FAQ.

     [8] https://github.com/w3c/payment-request-info/wiki/FAQ

More Choice Via Third Party Payment Apps

  The [9]Web Payments Working Group envisions that a diverse
  ecosystem of third party payment apps will give merchants and
  users more payment choices.

     [9] https://www.w3.org/Payments/WG/

  Browsers and other current implementations of Payment Request
  API allow users to store credit and debit card information for
  convenient reuse. Some also already support user registration
  of native mobile payment apps.

  In addition, to enable users to make payments from Web sites,
  the Web Payments Working Group is also working on the
  [10]Payment Handler API.

    [10] https://www.w3.org/TR/payment-handler/

Web Payments Demos at Money20/20

  On Monday, 23 October 2017 at the Money20/20 conference, W3C,
  Google, Mastercard, and Airbnb demonstrate [11]how to
  streamline online checkout using the Payment Request API.

    [11] https://www.w3.org/blog/2017/09/check-out-web-payments-demos-money2020/

About the World Wide Web Consortium

  The mission of the World Wide Web Consortium (W3C) is to lead
  the Web to its full potential by creating technical standards
  and guidelines to ensure that the Web remains open, accessible,
  and interoperable for everyone around the globe. W3C standards
  HTML5 and CSS are the foundation technologies upon which all
  Web sites are built.

  W3C's vision for "One Web" brings together thousands of
  dedicated technologists representing nearly 450 member
  organizations and dozens of industry sectors. Organizationally,
  W3C is jointly run by the [12]MIT Computer Science and
  Artificial Intelligence Laboratory (MIT CSAIL) in the United
  States, the [13]European Research Consortium for Informatics
  and Mathematics (ERCIM) headquartered in France, [14]Keio
  University in Japan and [15]Beihang University in China. For
  more information see [16]https://www.w3.org/

    [12] http://www.csail.mit.edu/
    [13] http://www.ercim.eu/
    [14] http://www.keio.ac.jp/
    [15] http://ev.buaa.edu.cn/
    [16] https://www.w3.org/

  End Media Advisory

Media Contact

  Amy van der Hiel, W3C Media Relations Officer
  <[17]w3t-pr@w3.org>
 mailto:w3t-pr@w3.org
+1.617.253.5628 (US, Eastern Time)
    __________________________________________________________





—
Amy van der Hiel
W3C Media Relations
<amy@w3.org>
+1.617.253.5628

Received on Thursday, 14 September 2017 20:20:51 UTC