W3C home > Mailing lists > Public > public-payments-wg@w3.org > February 2019

[Summary] Substantive changes to Payment Request API since July 2018 Candidate Recommendation draft

From: Ian Jacobs <ij@w3.org>
Date: Tue, 5 Feb 2019 10:53:45 -0600
Cc: Marcos Caceres <marcos@marcosc.com>
Message-Id: <E7788D9E-88C6-4148-A4BD-E21BD2DDDB37@w3.org>
To: Web Payments Working Group <public-payments-wg@w3.org>
Dear Web Payments Working Group,

This week I shared [1] that the editors have closed Payment Request API issues we wanted to address before moving version 1 to Recommendation.

I thought it would be useful (for this group and others) to summarize the main changes since the 9 July 2018 draft [2], which was the last draft announced to the Membership as a Candidate Recommendation. A full edit history is also available [3].

I note also one important change to Basic Card [4]: we removed supportedTypes. Basic Card will become a W3C Working Group Note when we complete Payment Request v1. 

Thank you,

Ian

P.S. Marcos, if you see any other changes that I’ve missed, please add to this thread. Thanks!

[1] https://lists.w3.org/Archives/Public/public-payments-wg/2019Feb/0001
[2] https://www.w3.org/TR/2018/CR-payment-request-20180709/
[3] https://github.com/w3c/payment-request/compare/CR...gh-pages
[4] https://w3c.github.io/payment-method-basic-card/

======
Substantive changes to Payment Request API since the 9 July 2018 draft

* Added support for notification when the user selects a payment method,
  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.

* Added support for merchant validation by the payment handler.

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

* "Payment request is showing" boolean now attached to top-level
   browsing context.

* Integrated with Feature Policy specification.

* Defined handling of multiple applicable modifiers.

--
Ian Jacobs <ij@w3.org>
https://www.w3.org/People/Jacobs/
Tel: +1 718 260 9447
Received on Tuesday, 5 February 2019 16:58:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 5 February 2019 16:58:25 UTC