- From: Dave Longley <dlongley@digitalbazaar.com>
- Date: Tue, 9 Feb 2016 16:53:58 -0500
- To: Rouslan Solomakhin <rouslan@google.com>, Web Payments Working Group <public-payments-wg@w3.org>
On 02/09/2016 04:22 PM, Rouslan Solomakhin wrote: > Layering is good idea in general. It would be great if virtual goods > that do not require shipping could be bought using a simpler API. > > However, in current proposed form, your API would not work with a UI > that has a dropdown for shipping method. I envision this UI to update > the total price estimate based on the shipping method selection. > Selecting a different address might update the price as well based on > distance or state tax. This logic lives on merchant website or comes > from their payment processor. (See Adrian Bateman's example below.) This should be in the examples in the spec we put together over the weekend, but since it's unclear, we'll write up a more clear one. When changes are made to the payment details, those details are sent to the merchant site so they can respond to them however they want (which potentially includes sending updated line items, etc.). This is just done by resolving the promise and explicitly passing control back to the merchant site rather than by emitting an event. -- Dave Longley CTO Digital Bazaar, Inc. http://digitalbazaar.com
Received on Tuesday, 9 February 2016 21:54:23 UTC