- From: ianbjacobs <notifications@github.com>
- Date: Tue, 29 Mar 2016 05:39:45 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Tuesday, 29 March 2016 12:40:20 UTC
This relates to issue #19 as well. We have identified a number of scenarios: enrollment, payment, reservation, recurring payment, ... At a high level I like for the merchant to be able to send a clear signal plus hints for how to communicate to the user. (We need a concrete proposal. :) 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/browser-payment-api/issues/56#issuecomment-202874961
Received on Tuesday, 29 March 2016 12:40:20 UTC