On 5/10/16 08:54, Tommy Thorsen wrote: > I think many payment apps will want to supply shipping information > along with the rest of the payment response, and I think we should > allow that. However, since we are planning to pass the request to the > payment app by means of HTTP POST, the onshippingaddresschange > mechanism isn't going to work. The shipping address will have to be > passed back in the payment response. I must be missing some context here. Can you point to one of the callflow diagrams that shows the scenario you're thinking of? -- Adam Roach Principal Platform Engineer Office of the CTO
Received on Tuesday, 10 May 2016 14:28:07 UTC