FASTag recharge: trace balance and credit

“My FASTag needs money” sounds simple. But it can mean a few different things: a normal top-up, a question about why the balance looks wrong, or a payment they made yesterday that never showed up. It helps to find out which one it is before anybody touches a phone.

Most FASTag recharge trouble comes from the money going to the wrong place, or going to the right place and not being checked. So this post is mostly about checking: where the money should land, how to confirm it did, and what to ask when it didn’t.

How do you find the right FASTag account?

Start by asking the customer which bank issued the tag. They can usually tell from the tag itself or from their account records. Then open that issuer’s official FASTag service. Check the vehicle number against the receiving account before you type in any amount. If the customer can’t tell you where the money should go, ask the issuer before paying anything.

One more thing to keep separate: an annual-pass purchase and an ordinary recharge are not the same thing. Look at the purpose written on the payment record to see which one you’re doing.

The issuer is the bank responsible for the customer’s tag account. National Electronic Toll Collection (NETC) is the FASTag programme. Its rules are in the NETC procedural guidelines, a framework from the National Payments Corporation of India (NPCI) that Indian Highways Management Company Limited (IHMCL) hosts. Section 4.6.1 lists several underlying payment instruments, including bank accounts and prepaid accounts. So don’t assume every customer has a separate prepaid wallet.

When you check a balance, say out loud which one you mean: the account the money is coming from, or the FASTag account that should receive it. Ask the customer to keep both records open during a missing-credit enquiry. Your own counter balance has nothing to do with that comparison.

Which recharge route should you use?

As of 18 October 2026, the IHMCL FAQ describes bank portals, netbanking, Unified Payments Interface (UPI), debit cards and credit cards for online recharge. It also describes cash recharge through the Bharat Bill Payment System (BBPS) at toll-plaza points of sale. Check that the facility exists before you send a customer there.

For a QR code or Virtual Payment Address (VPA), get the destination through the issuer’s official service. The NETC guidelines say issuers should offer a tag-linked UPI QR generator and the personalised VPA. Please don’t build a payment handle out of a vehicle number. It might look right and still go nowhere.

Use the vehicle number the chosen service asks for, and follow that service’s own screens. If what it shows doesn’t match the customer’s account record, stop and ask the issuer to confirm the correct destination.

What should you check before the customer pays?

Let the customer be the one who authorises the payment. You can help read the screen and save the result, but their PIN and authentication stay with them.

The IHMCL FAQ describes a UPI sequence: verify the FASTag UPI destination, enter the amount, then authenticate. Here’s a quick run before the customer presses the final button:

1. Confirm what they want. Is it a top-up of an existing FASTag? If the screen shows a different purpose, read it before going on.
2. Check the receiving details. Issuer and vehicle should match the customer’s account record. If not, ask the issuer to confirm.
3. Read the amount. Ask the customer to look at the final figure and any terms shown.
4. Let the customer authorise. If it fails, save the exact message instead of guessing why.
5. Save the result. Keep the payment reference and later look for the matching credit in the receiving account.

For a cash payment, ask for a record that names the account, the amount and a transaction reference. Read it before the customer leaves. And if the counter can’t explain how to trace the payment later, get that explanation before the customer hands over the cash.

How do you check the balance and a deduction?

Start with the receiving issuer’s account information, and look for the recharge entry itself. Don’t just compare the final balance with the amount paid, because tolls may have been deducted in between. A payment confirmation from the sending app is useful, but it isn’t a check on the receiving account.

The NETC guidelines, section 4.7(e), say issuers should send an SMS after a toll transaction with the plaza, toll fare amount and date and time. Use those details to identify a toll deduction. Don’t treat that SMS as a recharge receipt, because it’s about a different thing.

If an SMS and the current account view disagree, compare dates and any transactions in between. Ask the issuer to explain what’s left. And don’t add up an account balance, a deposit and an amount from some other service until you know what each one stands for.

For a deduction the customer doesn’t recognise, note the plaza and the transaction details and ask the issuer to investigate that debit. Keep this separate from a complaint that a recharge never arrived. They’re two different problems with two different answers.

Another common mix-up is about limits. A minimum top-up amount, a balance needed for a transaction and a security deposit answer different questions. Ask the issuer which limit applies to this account and this route, and if an amount is rejected, save the exact message. Don’t copy a figure from an old message or another customer’s account.

What if the recharge has not appeared?

Before suggesting another payment, find out what happened to the sending payment and to the receiving account. Look at the exact result shown by each service. If the customer says “it failed”, ask them to show you the screen or the record.

Be careful with the phrase “settlement delay.” Don’t use it unless there’s evidence about that specific transaction. If support uses it, ask which part of the payment is still incomplete and what the customer should do.

The last row deserves a word. If the credit is there but the tag is still restricted, another payment isn’t a proven fix. Ask the issuer what the restriction is. Don’t guess it from the recharge receipt alone.

The IHMCL FAQ directs customers whose account was debited without FASTag wallet credit to call the bank’s call centre and request reversal. Present that as a request for the bank to look into it. Don’t promise a reversal, and don’t promise a refund date.

For a UPI problem, the customer should use the complaint facility in the app they paid with. The Reserve Bank of India’s (RBI) online dispute resolution circular of 6 August 2020 requires that facility for UPI third-party apps, with a unique complaint reference and a way to track the complaint.

If two providers are involved, keep the payment complaint reference and the issuer reference together, and tell each provider what the other said. In each reply, ask support to state the outcome, the next step and any time limit that applies.

What should the customer write down for a complaint?

The NETC guidelines require the issuer’s toll-free user service number to appear on the tag, the usage guide and the website. Use that number to reach the issuer. Then keep a short case note. It needs only these:

• The issuer and the vehicle or account the money was meant for.
• Payment date, amount, the sending reference and the exact result.
• The matching credit, or a note that none was found when you checked.
• Any disputed toll, written down by plaza and reference.
• Every complaint reference, every reply and the next action asked for.

Keep PINs and authentication codes out of the note. Share only what the official complaint route asks for. And write down the provider’s own words, so the next follow-up is about the same unresolved point and not a fresh story.

How does automatic top-up work?

An e-mandate is the customer’s instruction allowing recurring payments under stated terms. As of 18 October 2026, RBI’s Digital Payments E-mandate Framework, 2026 requires authenticated registration and covers mandate validity and facilities to modify or withdraw it. The customer can set a maximum recurring transaction value for a variable mandate.

Before the customer agrees, they should look at the payment source, how long the mandate lasts and the maximum amount, and keep the mandate reference. Signing up doesn’t give the counter permission to authorise later payments on their behalf.

There’s one detail that surprises people. The framework exempts registered FASTag auto-replenishment mandates from the pre-transaction notification requirement, so no advance reminder may arrive. It keeps the post-transaction notification, including transaction and mandate references and grievance information. Explain that before the customer opts in.

If an automatic debit looks unfamiliar, the customer should compare the notification with their mandate record and contact the issuer through its grievance route. Automatic top-up doesn’t prevent every recharge or tag-status problem, so don’t sell it as a cure.

To change or withdraw a mandate, the customer opens it through the issuer’s service and checks the mandate reference first. The framework requires an additional factor of authentication for that, and the customer completes it themselves. If the result is unclear, ask the issuer whether the change or withdrawal took effect before relying on it. Treat that request separately from any complaint about a past debit.

Questions about a recharge already paid

What if someone else made the payment?

Keep the payer and the FASTag account holder clear in the record. The actual payer keeps the payment reference and uses their own provider’s complaint route. Link the issuer query to the vehicle or account that was meant to receive the money. Nobody at the counter should act as either party.

What if manual recharge and automatic top-up both appear?

Check each payment reference against the receiving account entries and the mandate record. Don’t call either payment a duplicate just because they happened close together. Handle any change to future automatic top-up as a separate request.

Can an old minimum-balance message decide a new recharge?

No. NETC guidelines v2.1, section 4.1.1 A(ix), checked on 18 October 2026, prohibit a VC04 threshold apart from the security deposit. Ask which current provision applies to this vehicle and account instead of copying another customer’s figure.

Where do you get help?

For the published recharge routes and the missing-credit instruction, point customers to the IHMCL FASTag user FAQ. Give them the complaint reference, the provider’s reply and the next action in writing.

A problem with your own SiOnline account or panel is a separate matter from the customer’s tag. For that, use SiOnline support, the Help Centre or customer care. If you’re thinking about offering FASTag at your counter, see the page on how to become a FASTag agent.

Sources

• IHMCL FASTag user FAQ, reopened 18 October 2026.
• NPCI NETC Procedural Guidelines, version 2.1, reopened 18 October 2026.
• RBI Online Dispute Resolution circular, 6 August 2020, reopened 18 October 2026.
• RBI Digital Payments E-mandate Framework, 21 April 2026, reopened 18 October 2026.

Confirm current issuer instructions before acting.