- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 13 Aug 2018 20:31:04 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 14 August 2018 03:31:26 UTC
@ianbjacobs: > @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. I don't understand how this is different from what I had proposed in the pull request? Could you please comment on the pull request? It seems like a waste of time for @rsolomakhin to have to redo what I already worked on? I don't see anything in your points that my pull request didn't already do. The only difference from the points above is that there event was sent to the PaymentRequest (`.onpayerdetailchange`), instead of the `onpaymentmethodchange`, but that's just a detail. Wrote @adrianhopebailie: > @marcoscaceres the key difference with push is that by the time the website gets the PaymentResponse the payment is complete. Sure. I get that part. > Compared with BasicCard, for example, the merchant has nothing more to do but mark the sale as complete. The payment is already done. I'm still not following :( -- 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-412743487
Received on Tuesday, 14 August 2018 03:31:26 UTC