- From: Shane McCarron <notifications@github.com>
- Date: Mon, 14 Mar 2016 12:18:34 -0700
- To: WICG/paymentrequest <paymentrequest@noreply.github.com>
- Cc: webpayments <public-payments-wg@w3.org>
Received on Monday, 14 March 2016 19:19:03 UTC
That's really good data. Thanks! I personally agree with this. So it would be good if the architecture permitted it to *seem* as if there is a single solution in place. If the reality is that I installed the XYZ loyalty card app and that is one of my available payment methods, as long as the experience is more or less smooth, I expect we will be fine. I also expect the situation will be self correcting. Payment apps that do not integrate well / have a less comfortable and familiar user experience will either 1) not be approved by the relevant app store, or 2) get quickly panned by their users for not working well. --- Reply to this email directly or view it on GitHub: https://github.com/WICG/paymentrequest/issues/66#issuecomment-196483095
Received on Monday, 14 March 2016 19:19:03 UTC