W3C home > Mailing lists > Public > public-payments-wg@w3.org > December 2015

Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39)

From: Manu Sporny <notifications@github.com>
Date: Tue, 15 Dec 2015 21:49:00 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/39/165004009@github.com>
> Should the payment request API have shipping address APIs?

No, it should not for at least the following reasons:

1. There are other pieces of data that may be important to a payment request (billing address, drop shipping address, pickup address, over 18, loyalty card, subscriber number, etc.). I assume we are not going to add APIs to the payment request API for all of those pieces of information. This problem should be solved in a more generalized way (and that mechanism is the focus of the Verifiable Claims Task Force and the Credentials CG). We shouldn't make a special exception for shipping address.
2. 80% of the state information in the paymentRequest API is dedicated to shipping address. We could greatly reduce the state information by just removing this one feature.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 16 December 2015 05:49:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:12 UTC