Re: [webpayments] Should a Payment Request API have shipping address APIs? (#39) from Manu Sporny on 2015-12-17 (public-payments-wg@w3.org from December 2015)

From: Manu Sporny <notifications@github.com>
Date: Wed, 16 Dec 2015 21:01:48 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/39/165337760@github.com>

> Physical good purchases are the majority of online transactions, and part of that flow is the collection of shipping information. Shipping information is special because, unlike loyalty cards, etc, it is impossible to fulfill the transaction without it. It is both ubiquitous and critical across all physical good transactions.

To be clear, I don't think that anyone is arguing that shipping information is not important. We do want to automate the collection of it. That said, we don't want to automate it in a way that incurs technical debt in the Web Platform. Once you add a questionable feature to the Web, it's very hard to &lt;marquee>remove it&lt;/marquee>.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/39#issuecomment-165337760

Received on Thursday, 17 December 2015 05:02:21 UTC