We understand that mistakes happen! Whether you entered the wrong location or selected the wrong vehicle, we want to help you resolve it quickly so you can get back to your day with confidence.
Step 1: Act Quickly
The faster you act, the easier it is to minimize any costs.
Check the Type: Look at your session in the app to see if it is a Start-Stop or a Fixed-Duration session.
Stop the Session: If it is a Start-Stop session, tap Stop in the app immediately (or call 0203 046 0010). You will only be charged for the few minutes the session was active.
Fixed-Duration: These sessions cannot be cancelled once they’ve started, but you can request a refund.
Step 2: Request a Refund
If you were charged for a session you didn't intend to book, we are here to empower you through the refund process.
Action: Log in to your account and submit a refund request here.
What to include: To help us move quickly, please provide the location code, date, and time of the accidental booking.
Live Chat: You can also start a Live Chat to speak with one of our friendly team members for guidance.
Important Things to Know
We want to be dependable and transparent about how refunds work:
Operator Rules: RingGo processes payments on behalf of parking operators. Because of this, the final decision on a refund usually depends on the specific rules set by the local council or car park owner.
Our Role: We will either process the refund directly, reach out to the operator for you, or provide you with their contact details so you can speak with them.
No Guarantees: While we always aim to be helpful, refunds are not guaranteed and depend on the operator's policy.
Tips for a Smooth Journey
Double-Check the Sign: Always verify the 4 to 7-digit location code on the nearby parking signs before confirming.
Verify your VRN: Make sure the correct mobile number or email address and vehicle registration are selected in your account.
Our Vision: By helping you manage accidental bookings fairly, we’re making city parking more reliable and stress-free for everyone.
Comments
0 comments
Article is closed for comments.