-
Notifications
You must be signed in to change notification settings - Fork 308
display on-site notification re: credit card failure #1746
Comments
As a side note, "Fix your" is a separate link from "credit card", and the "Fix your" link merely goes to |
If you click "credit card" it should link you to https://www.gittip.com/credit-card.html which should tell you your error. |
It does, and it shows me this:
(Where Between how cryptic that is (I believe it boils down to my bank [it's a debit card] basically replying with "LOLNOPE"?) and the fact that it doesn't have any sort of notification -- neither via email nor when you are on Gittip but not on someone else's profile -- that mentions it, it's very difficult to notice. That little message doesn't stand out at all, and is only on other users' profiles. I talked to @seanlinsley briefly on IRC and they mentioned that #89 is a long-standing issue related to why we can't email people, and #1643 is already in master and could be useful for notifying users when they visit the site. If we were to use #1643 for this (which makes sense to me), I'd say we should look into a way to have "sticky" alerts (always show them until they are explicitly acknowledged in some manner). |
Ftr, notifying users of payment errors via email is #583. |
I take it this issue is about notifying users via on-site notifications. |
Title updated. |
+1 from @dcwalk at #2372 (comment). |
+1 from @mlncn at #583 (comment). |
Note that @rummik implemented sticky notifications, so we should have everything necessary to implement this, now. |
To clarify for anyone reading this later, we have notifications for impending credit card expirations (#2379), but nothing for failures |
Anonymous +1 from support: |
[was: Lack of information about failed transactions]
The only indicator I got that a transaction failed was this:
If I hadn't gone to somebody else's profile, I would have never found out that the transaction had failed. I can't even reliably determine which transaction it is that failed.
The text was updated successfully, but these errors were encountered: