Fwd: CR: Payment Request API (Call for Wide Review)

Thanks for sending in this request Ian, Nick and Adrian. We will assign the review at our next PING meeting on 17 December 2020 at UTC 17.

Christine (PING co-chair)

Begin forwarded message:

From: Notifier <sysbot+notifier@w3.org<mailto:sysbot+notifier@w3.org>>
Subject: CR: Payment Request API (Call for Wide Review)
Date: December 2, 2020 at 11:27:11 PM PST
To: public-review-announce@w3.org<mailto:public-review-announce@w3.org>
Resent-From: public-review-announce@w3.org<mailto:public-review-announce@w3.org>

Payment Request API

https://www.w3.org/TR/2020/CR-payment-request-20201203/

Abstract

This specification standardizes an API to allow merchants (i.e. web sites selling physical or digital goods) to utilize one or more payment methods with minimal integration. User agents (e.g., browsers) facilitate the payment flow between merchant and user.

Status of the Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.

The working group maintains a list of all bug reports that the group has not yet addressed. Pull requests with proposed specification text for outstanding issues are strongly encouraged.

The working group will demonstrate implementation experience by producing an implementation report. The report will show two or more independent implementations passing each mandatory test in the test suite (i.e., each test corresponds to a MUST requirement of the specification).

There has been no change in dependencies on other workings groups during the development of this specification.

This document was published by the Web Payments Working Group as a Candidate Recommendation Snapshot. This document is intended to become a W3C Recommendation.

GitHub Issues are preferred for discussion of this specification.

Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. A Candidate Recommendation Snapshot has received wide review and is intended to gather implementation experience.



This Candidate Recommendation is not expected to advance to Proposed Recommendation any earlier than 31 December 2020.

This document was produced by a group operating under the 1 August 2017 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 15 September 2020 W3C Process Document.


Changes since last publication

Substantive changes to the Payment Request API since the 9 July 2018 version are as follows. The complete list of changes, including all editorial changes, is viewable in the commit history. Key set of changes are viewable in the Changelog.

 * Added support for notification when the user selects a payment handler, but before confirming payment. This allows merchant to update totals, validate acceptance, etc.
 * Added support to notify site of billing address selection. This allows a merchant to update a total (e.g., for VAT in Europe). To enhance privacy, only some billing address data is returned to the merchant as long as the user has not confirmed payment.
 * Added support for retry() and fine-grain error reporting to the user.
 * Clearer definition of canMakePayment() and worked to align implementations. canMakePayment() does not reveal whether payment handler is primed to pay.
 * Removed languageCode and regionCode from PaymentAddress.
 * Removed currencySystem.
 * &quot;Payment request is showing&quot; boolean now attached to top-level browsing context. Previously, only a single payment UI was allowed to be shown at a time across the whole browser. This now allows multiple browser tabs to show a payment UI at the same time (for those payment handlers able to support it).
 * Integrated with Permissions Policy.
 * Defined handling of multiple applicable modifiers.
 * Removed support for merchant validation because of lack of multi-implementer support.
 * Deprecated allowpaymentrequest attribute.
 * Calling show() now consumes the user activation.

--
This report was generated using https://github.com/w3c/transition-notifier