Re: [w3c/webpayments-payment-apps-api] Users MUST be able to prevent the display of unregistered payment apps (#59)

Actually, @burdges , none of your examples are things I was envisioning.  And I used "notified" advisedly.  I don't like the word "displayed" as it implies a certain modality.  We are all about A11Y at the W3C!

My concern is this: Tom has chosen a Payment App as his payment representative on the Web.  Everything Tom does with regard to payments is done through that App.  All of his payment methods, loyalty cards, gift cards, digital offers, etc. are known to that App.  Tom does NOT want to ever use another Payment App.  Why should Tom be presented with Payment App options that he has not installed and never will.  He should just be sent to his payment app with his payment methods and be done with it.

Better yet, in the brave new world where Tom's payment app is very , very smart... that app is choosing his payment method for him.  He has told it that for domain X always use method Y.  Or he has said "whenever possible use method z at office supply stores because it gets me the most points.  At grocery stores use method w.  If methods z or w are not accepted.... prompt me."  

This is the sort of power that we are able to give to end users.  Spamming them with some web sites payment app when they already have these sorts of preferences available is just rude.

-- 
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/59#issuecomment-249733419