Re: [w3c/payment-request] Should API support billing address capture (for tax computation)? (#27)

@marcoscaceres I don't think you need to change the PRs but perhaps there is a need to add something that shows how a PaymentHandler may cause the `Payer address changed algorithm` to be invoked (when a user provides a billing address through interaction with the PaymentHandler).

**Q:** Are you suggesting the spec text that describes how a Payment Handler might invoke the `Payer address changed algorithm` doesn't belong in the PaymentRequest but rather in the PaymentHandler spec?

**Push Payments and `retry()`***

The underlying issue related to push payments is not with Billing Address but with `retry()`. It is too late to call `retry()` if the payment handler has already completed the payment. So, while a Billing Address issue may be one reason to call `retry()` it's not the root of the issue. 

I don't think `retry()` is a good idea and I think what @ianbjacobs and @rsolomakhin are attempting to do is find a flow that avoids needing it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/27#issuecomment-412874503