Re: [w3c/browser-payment-api] provide shipping address in PaymentResponse (#139)

@adrianhopebailie I appreciate your concern.  Question: architecturally, is there a reason the *payment app* could not supply shipping address etc?  My current payment app does this.  It's pretty handy.  I appreciate that some user agents have the built-in ability to do this as well, but are we precluding the possibility that a payment app could provide this service? 

I can answer my own question: Yes, we are precluding that.  But should we be?  If a payment app told the mediator, as part of its registration, that it had the ability to address merchant requests for address, phone, email, etc, then those requests could be passed along.  Right?

---
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/browser-payment-api/pull/139#issuecomment-212376475