Before you raise a FASTag dispute, build a short record: the two statement lines, their timestamps, the vehicle number, the toll plaza name and what your own trip log says about that day. A complaint with specifics is easier to act on than one that says I was charged twice. Then log each contact with its date and reference number.
Is it really a double charge?
Check first. Two similar lines can be legitimate: an outbound and a return crossing on the same day, two separate plazas close together, or a different vehicle on the same account. Compare the plaza name, the time gap and your trip log. If the two lines are minutes apart at the same plaza and you crossed once, that is worth raising. If you are unsure, note it in your record as a question for the issuer instead of an accusation.
Look at the balance trail too. On a wallet-based tag, the running balance after each line shows whether both debits went through or whether one is shown differently; read what your own statement says rather than guessing.
What should you collect before contacting the issuer?
- The statement lines: date, time, amount, plaza name and transaction reference, copied exactly.
- The vehicle registration number and the tag identifier, as shown on your account.
- Your trip log for that day: where you went, when, and the route taken.
- Anything that supports a single crossing, such as a map timeline or a fuel stop.
- Whether the tag draws on a wallet or a linked bank account, since refunds follow that route.
Download the statement from your issuer's app or portal and check your own screen for the option, because menus differ between issuers. Keep screenshots as well.
What does a dispute log look like?
| Date raised | Plaza and time | Amount (₹) | Channel used | Reference no. | Follow-up date | Status |
|---|---|---|---|---|---|---|
| 14 Nov | Plaza A, 08:15 and 08:22 | 65 and 65 | Issuer's app | REF-2001 | 21 Nov | Waiting for reply |
| 21 Nov | Plaza A, 08:15 and 08:22 | 65 | Phone, spoke to agent | REF-2001 | 28 Nov | Refund promised |
| 28 Nov | Plaza A, 08:22 | 65 | Bank statement | REF-2001 | - | Credit received |
The amounts and references are invented. Add a column for the name of the person you spoke to, and keep the original reference number on every row so one dispute reads as one line of history.
What can you do with a double-charge report?
SpendixAI has a Possible duplicate charges report that lists the same amount paid to the same merchant within two days, which is useful if you upload a statement that includes your tag payments. It only flags candidates, so you still decide whether the second line is a genuine repeat. Journeys that cross the same plaza twice in a day will appear too, and that is why your trip log matters.
How long will it take?
No timeline can be promised from outside, because it depends on the issuer and the case. Ask when you raise the dispute how long they expect it to take, note the answer in your log and set a follow-up date. If the date passes, quote your reference number and the previous contact.
What if it is not resolved?
- Ask for a written outcome that explains why the second charge was valid, or the refund date.
- Use the issuer's escalation route, which should be named in their grievance process.
- Keep every reference number and reply in one place.
- If your bank is the issuer, check its own complaint channel too.
Before you hang up
- Get a complaint reference number.
- Ask how and when you will hear back.
- Note the date, time and name of who you spoke to.
- Never share OTPs or your UPI PIN on a call, however official it sounds.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

