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

Related to:

:+1: for a more generalized method for exchanging data between payee application (website) and payment app outside of the payment request and response messages. But, I'd like to establish if this is a firm requirement for the API before we define the way it is done.

The only use case I can think of that requires this is when the data exchanged alters the parameters of the payment so that the payee needs to update the payment request. In this case, setting a shipping address changes the shipping cost which in turn changes the amount.

Are there use cases beyond shipping where the payee may need the ability to update the payment request before the payment app responds?

Reply to this email directly or view it on GitHub:

Received on Wednesday, 16 December 2015 14:53:20 UTC