Settings and activity
13 results found
-
2 votes
Thank you for submitting your Idea to UserVoice.
Noelle
supported this idea
·
-
1 vote
Noelle
shared this idea
·
-
14 votes
Thank you for submitting your Idea to UserVoice.
Noelle
supported this idea
·
-
2 votes
Thank you for submitting your Idea to UserVoice.
Noelle
shared this idea
·
-
1 vote
Thank you for submitting your Idea to UserVoice.
Noelle
shared this idea
·
-
3 votes
Thank you for submitting your Idea to UserVoice.
Noelle
supported this idea
·
-
6 votes
An error occurred while saving the comment
Noelle
supported this idea
·
-
2 votes
Thank you for submitting your Idea to UserVoice.
Noelle
shared this idea
·
-
2 votes
Thank you for submitting your Idea to UserVoice.
Noelle
shared this idea
·
-
44 votes
Noelle
supported this idea
·
-
11 votes
Noelle
supported this idea
·
-
1 vote
Noelle
shared this idea
·
-
21 votes
Thank you for submitting your Idea to UserVoice.
Noelle
supported this idea
·
Declines should show the native network response on the Clover dashboard so merchants can know why a payment declined. Ideally, the decline reason should also show on the hosted checkout at time of sale.
This includes Telecheck declines: currently, some Telecheck declines do not even show up on the dashboard at all. This leads people to believe that there is a front-end error instead of a decline.
Having detailed decline descriptions pulling from the native network response code would help in troubleshooting declines immensely.