That is an interesting and reasonable way to view the experience. I suppose it could be acceptable to have the payment app decline with appropriate messaging, but only if it is hassle-free to make another app selection. On Thu, Jan 19, 2017 at 3:39 PM -0800, "Dave Longley" <notifications@github.com<mailto:notifications@github.com>> wrote: @tommythorsen<https://github.com/tommythorsen>, This will of course be visible to the user, but I think that in any case, if the merchant is so shady that the payment provider does not want anything to do with it, this is useful for the user to be made aware of. +1. In fact, I think it would be downright mystifying if a Payment App that I usually pay for things with all the sudden doesn't show up on a website that, AFAICT, accepts the same kind of payment I'm used to using. I'd think there was a problem with the Payment App or my browser. I'd be totally unaware that the merchant had been blacklisted by my Payment App. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://github.com/w3c/webpayments-payment-apps-api/issues/92#issuecomment-273933542>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ARKSKT8eQq9-ThAPKfBhCzhVfCcfPTSAks5rT_QLgaJpZM4LnikN>. -- 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/webpayments-payment-apps-api/issues/92#issuecomment-273934557
Received on Thursday, 19 January 2017 23:45:24 UTC