I just tried to load a check onto my account, the check was approved and I had to write...

GetHuman1362125's customer service issue with RushCard from October 2018

3 views
 | 
1796 similar
 | 
0 following
Help with my RushCard issue
How did GetHuman1362125 do it?
Waiting to hear how GetHuman1362125 fixed the problem to share with other customers.
The issue in GetHuman1362125's own words
I just tried to load a check onto my account, the check was approved and I had to write VOID on the check and submit the picture. When I did the I received a message stating that the load had failed the message I received stated "we are sorry the load failed your issuer may not have enabled this function for you please contact your issuer" what does this mean as I have loaded several checks into my card before. How can I get this fixed and receive the money as I have already written VOID on the check
GetHuman1362125 did not yet indicate what RushCard should do to make this right.
I have an issue with RushCard too
How GetHuman1362125 fixed the problem
We are waiting for GetHuman1362125 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
Do you have a customer issue as well?
We can help you get RushCard's attention and get better help faster. Tap below to get started.
Having RushCard issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would RushCard email you?
This email address isn't valid
Follow this issue
See how GetHuman1362125 fixes it.
This email address isn't valid

RushCard

Customer service issue
Reported by GetHuman1362125
Oct 17th, 2018 - 2 mons ago
I have an issue with RushCard too
Fixed
Seen by 3 customers so far
Similar issue to 1796 others
0 customers following this
Follow this issue to see how it gets fixed
Items needed
Card Number
Email on Account
Home Address
Name of Account Holder
Phone Number
Timeline
GetHuman1362125 started working on this issue
Oct 17th 5:15am
GetHuman1362125 confirmed the issue is fixed. Hooray!
Oct 18th 5:41am