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

@rsolomakhin and I discussed this further today and I anticipate he will write up something sensible when time permits. At a high level, we discussed this type of flow which is a better experience than the one I had in mind.

 * The user has not yet selected a billing address.
 * The user selects a payment handler.
 * Within the payment handler, the user selects a payment instrument with associated billing address.
 * The payment handler informs the browser that the user has selected a billing address. The payment handler waits for a response (read: promise to resolve) that may update the total. The payment handler will not complete the transaction until hearing back from the merchant.
 * The browser fires the onpaymentmethodchange event to let the merchant know the billing address has changed.
 * The merchant responds with a (possibly null) update of the total.
 * The browser gives the (possibly updated) total back to the payment handler.
 * The payment handler displays the total and allows the user to proceed.

@marcoscaceres, regarding push v pull payments, here's a piece by Adrian Hope-Bailie:

  A Push Payments Manifesto
  https://adrian.hopebailie.com/a-push-payments-manifesto-2d8ff105f48a

Examples: wire payments, ACH payments, SEPA credit transfers, Boleto Bancário, bitcoin, various real-time payments systems, etc. I invite others who know more about payments to list some useful resources.

Ian

-- 
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-411962921