Philippe and Ralph,

This is a transition request to Candidate Recommendation for the following specifications:

Payment Request API
https://rawgit.com/w3c/payment-request/f2e398621b8bd579f1dd95d4d37e15d4dfb80078/index.html?specStatus=CR

Payment Method Identifiers
https://rawgit.com/w3c/payment-method-id/b771279ea3cd68172ffa7461e30f1f00abca6161/index.html?specStatus=CR

Thank you,

For the Web Payments Working Group Co-Chairs,
Ian Jacobs

==============================================
GROUP DECISION

* https://lists.w3.org/Archives/Public/public-payments-wg/2017Jul/0057
* Deadline for comments on the CRs: 2017-10-31
* No Formal Objections

----------------------------------------------
CHANGES

There have been many changes since the FPWDs were published in April 2016.

* Changes to Payment Request API
  https://github.com/w3c/payment-request/pulls?q=is%3Apr+is%3Aclosed

* Changes to Payment Method Identifiers
  https://github.com/w3c/payment-method-id/pulls?q=is%3Apr+is%3Aclosed

----------------------------------------------
ISSUES

* Issues closed for Payment Request API
 https://github.com/w3c/payment-request/issues?q=is%3Aissue+is%3Aclosed

* Issues closed for Payment Method Identifiers
 https://github.com/w3c/payment-method-id/issues?q=is%3Aissue+is%3Aclosed

----------------------------------------------
CHANGES TO DEPENDENCIES

A number of new specification dependencies have been introduced since FPWD:

* Tags for Identifying Languages (IETF)
* Unicode Common Local Data Repository (Unicode Consortium)
* Codes for the representation of names of countries and their subdivisions (ISO). [Was Unicode Common Locale Data Repository]
* DOM (WHAT WG)
* The international public telecommunication numbering plan (ITU-T)
* HTML (WHAT WG)
* INFRA (WHAT WG)
* PROMISES GUIDE (W3C TAG Finding)
* A Universally Unique IDentifier (UUID) URN Namespace (IETF)


----------------------------------------------
WIDE REVIEW

The Working Group received review from the following W3C groups.

* PRIVACY INTEREST GROUP

  Various conversations and feedback:
  https://lists.w3.org/Archives/Public/public-privacy/2016AprJun/0091
  https://lists.w3.org/Archives/Public/public-privacy/2016OctDec/0003
  https://lists.w3.org/Archives/Public/public-payments-wg/2017Mar/0089
  https://lists.w3.org/Archives/Public/public-privacy/2017JanMar/0029


* TECHNICAL ARCHITECTURE GROUP

  TAG reviews:
  https://github.com/w3ctag/design-reviews/issues/152

  WPWG also used the TAG's security checklist early in the process:
  https://lists.w3.org/Archives/Public/public-payments-wg/2016Jul/0012


* I18N CORE WORKING GROUP

  Various conversations and feedback:
  https://github.com/w3c/payment-request/issues/327
  https://github.com/w3c/payment-request/issues/480
  https://www.w3.org/Search/Mail/Public/search?type-index=public-payments-wg&index-type=t&keywords=i18n&search=Search


* ACCESSIBLE PLATFORM ARCHITECTURES

  Various conversations and feedback:
  https://lists.w3.org/Archives/Public/public-apa/2016Aug/0086
  https://lists.w3.org/Archives/Public/public-apa/2017Mar/0002

There have also been numerous discussions about the work
with external groups, including:

* GSMA (direct participation in the WG)
* ISO 20022 (direct participation in the WG)
* EMVCo 
* PCI Security Council
* NACHA
* European Central Bank
* ITU-T Focus Group on Digital Financial Services

For the most part these discussions have not constituted formal
review.  However, they do help raise awareness and ensure
interoperability with other parts of the financial services industry.

----------------------------------------------
IMPLEMENTATION

* 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).

* Payment request API is currently being implemented in:

 - Chrome
 - Edge
 - Firefox
 - Webkit
 - Facebook
 - Samsung Internet Browser

* Work has begun on a test suite:
  https://w3c-test.org/payment-request/

  We are actively working to increase our testing effort in
  discussions with W3C Members and other organizations.

----------------------------------------------
FEATURES AT RISK

* The Working Group identified one at-risk feature: "currencySystem",
 designed to enable support for currencies that are not yet part
 of the ISO 4217 standard.
 https://github.com/w3c/payment-request/issues/490

* The Working Group seeks input from implementers, developers, and the
 general public on whether the feature should remain in the
 specification.

----------------------------------------------
PATENT DISCLOSURES

* There are patent disclosures associated with the work of this
 Working Group:
 https://www.w3.org/2004/01/pp-impl/83744/status#current-disclosures

* W3C launched a PAG in August 2016 and closed it in March 2017:
 https://www.w3.org/2016/08/wpwg-pag/

* The PAG concluded that the Disclosed Patents do not contain
 Essential Claims as defined in the W3C Patent Policy and recommended
 that the Web Payments Working Group continue to work on the Web
 Payments Specifications. For more information, see the report:
 https://www.w3.org/2017/03/wpwg-pag-report.html