- The W3C published - Payment Request API 1.0 as a Proposed Recommendation in September - 2021. Since then, W3C has been working to resolve two Formal Objections - from W3C Members; see the Team Report for - details. At this time, a Council is evaluating the Formal Objections to - determine whether Payment Request API 1.0 should advance to - Recommendation or be returned to the Working Group for changes. + In September 2022 the Web Payments Working Group published a Payment + Request Recommendation. Following privacy and internationalization + reviews, the Recommendation excluded + capabilities related to billing and shipping addresses. However, + implementations have continued to support those features interoperably, + and so the Working Group has decided to try to re-align the + specification with implementations, and re-engage the community on + associated issues.
- In the meantime, the Editors have continued to update this - specification with new features (see change log below). To provide - devellopers and implementers with more confidence about these features, - the working group has decided to formally publish the a new W3C Working - Draft. This will also provide the group with a foundation for potential - discussion at TPAC about the future of Payment Request. + This document is a Candidate Recommendation Snapshot based on the text + of the original Recommendation. A subsequent Candidate Recommendation + Draft will add back address capabilities and a small number of other + changes made since publication of the Recommendation.
- It is not uncommon for a Working Group to work on different revisions - of a specification simultaneously (e.g., see the CSS WG). With that in - mind, and because our current charter - anticipates enhancements to Payment Request 1.0, we've publish this 1.1 - draft. + As part of adding back support for addresses, this specification now + refers to the address components defined in the Contact Picker API rather + than define those components itself. Indeed, the Contact Picker API is + derived from the original definitions found in Payment Request API, and + pulled out of the specification because addresses are useful on the Web + beyond payments.
- 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 plans to engage in discussion and follow the usual + review process before advancing the specification to Proposed + Recommendation status.
The working group will demonstrate implementation experience by @@ -134,47 +133,6 @@
- There has been no change in dependencies on other workings groups - during the development of this specification. -
-- In September 2022 the Web Payments Working Group published a Payment - Request Recommendation. Following privacy and - internationalization reviews, the Recommendation excluded - capabilities related to billing and shipping addresses. However, - implementations have continued to support those features - interoperably, and so the Working Group has decided to try to - re-align the specification with implementations, and re-engage the - community on associated issues. -
-- This document is a Candidate Recommendation Snapshot based on the - text of the original Recommendation. A subsequent Candidate - Recommendation Draft will add back address capabilities and a small - number of other changes made since publication of the Recommendation. -
-- In adding back support for addresses, the group plans to refer to the - address components defined in the Contact Picker API rather - than define those components itself. Indeed, the Contact Picker API - is derived from the original definitions found in Payment Request - API, and pulled out of the specification because addresses are useful - on the Web beyond payments. -
-- The Working Group would engage in discussion and follow the usual - review process before advancing the specification to Proposed - Recommendation status. -
-