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

> 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:
https://github.com/w3c/webpayments/issues/39#issuecomment-165004009