Account* **********Rceived invoice * ********* on *******for non-payment ($*.**) throug...

GetHuman2616833's overcharge issue with Sunpass from March 2019

Help with my Sunpass issue
Top Tip from another customer
If you are looking for a refund you should call into the company as the best option is to talk with a representative about the charges. If it is fraud you should call in to cancel your card and request a refund.
The issue in GetHuman2616833's own words
Account* **********Rceived invoice * ********* on *******for non-payment ($*.**) through toll with license plate FL-***YJD on *******, in Miami FL.**This is not my vehicle (registered, rental, leased,) or licensen plate.**I have checked my Sunpass dashboard for fraudulent activity and the is none. Additionally, I have not loaned my transponder toany oneandhave itin my possession.**I believe this maybe a clerical error on behalf of Sunpass.**Please investigate and let me know.**Thank you and have a great day.
GetHuman2616833 did not yet indicate what Sunpass should do to make this right.
I have an issue with Sunpass too
How GetHuman2616833 fixed the problem
We are waiting for GetHuman2616833 to fix the problem and share the solution with the rest of us customers.
Please help with my Sunpass issue
Do you have a customer issue as well?
We can help you get Sunpass's attention and get better help faster. Tap below to get started.
Having Sunpass issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid


overcharge issue
Reported by GetHuman2616833
Mar 28th, 2019 - 24d ago
I have an issue with Sunpass too
Seen by 8 customers so far
Similar issue to 675 others
0 customers following this
Items needed
Who made the booking
Booking reference
Billing address
Email address on the account
Loyalty program number (if applicable)
GetHuman2616833 started working on this issue
Mar 28th 3:14pm
GetHuman2616833 indicated the issue is not fixed yet.
Mar 29th 3:28pm
GetHuman2616833 indicated the issue is not fixed yet.
Mar 31st 7:30pm