Cancelled Ticket: Check the Agent Charge Refund

A customer comes back to your counter. They cancelled a ticket you booked, and now they want to know why the refund looks smaller than what they paid. They point at your charge and ask, “Do I get that back too?”

It’s a fair question, and the honest answer takes a bit of care. Three different things get mixed up in a cancelled ticket: the charge you collected at booking, whatever the railway deducts, and any new charge for cancelling. They have different rules, so keep them apart and check each one before you quote the customer a total.

What is the difference between a booking charge and a cancellation charge?

As of 18 October 2026, SiOnline’s fixed agent charge is ₹20 per non-AC PNR and ₹40 per AC PNR, collected from the customer at booking. It’s per PNR, not per passenger (source: SiOnline, as of 18 October 2026).

IRCTC’s agent policy states that the agent charge applies to the booking transaction, and that agents have no charge for cancellation transactions. So when a customer asks you to cancel, don’t add a handling fee. That’s a clear rule.

But look closely at what the rule actually says. It stops you from adding a new charge. It doesn’t say what happens to a charge that was already paid at booking. Those are two different questions, and the second one needs its own answer. So ask for the term that governs the original charge. And don’t tell the customer it’s refundable, or that you’re keeping it, just because a different charge is prohibited. For the booking unit itself, read the agent charge explanation.

How do you reconcile what the customer paid?

Put the records side by side, and ask one question of each.

Keep the invoice and the cancellation receipt together in one place. If the treatment of the original charge isn’t clear, ask the booking agent or PSP for a written explanation before you promise that the full amount collected will return.

Also keep a disputed fee separate from a railway refund that hasn’t been credited yet. They’re different problems with different people to ask. And remember that a customer isn’t paid just because the agent account received a credit. Follow each stage with its own reference.

How does the passenger OTP fit in?

IRCTC’s Revised Agent Policy, effective 29 November 2019, describes cancellation on the customer’s request, an OTP sent to the passenger’s mobile, and refund credit to the account used for booking after the correct OTP is entered. The agent then passes the cancellation refund on to the customer.

That OTP belongs to the one cancellation it’s authorising. It is not your agent account-login OTP. So never share a password or a login OTP with a caller who happens to know a PNR. If the passenger can’t complete the authentication, treat that as its own problem, separate from any charge dispute, and describe the exact message they saw. There’s more in the cancellation OTP guide.

Why shouldn’t you rely on an old cancellation table?

Because the rules have moved. The Ministry of Railways announcement published by PIB on 24 March 2026 describes revised cancellation arrangements and removal of the e-ticket TDR requirement. An old chart on a wall, or a number someone remembers, may no longer apply.

So check the rule applied to the actual ticket, and the cancellation quote shown on screen. If the result isn’t what the customer expected, write down the quota, the passenger status, the cancellation time and the exact amount. Then ask for an explanation specific to that ticket. And don’t cancel a ticket just to see what the refund turns out to be, unless the customer has agreed to it.

What about a partial cancellation?

This is where most arguments start, so go slowly. IRCTC’s User Guide for E-Ticket Cancellation, checked on 18 October 2026, says only the passengers being cancelled should be selected, and that the passengers who are continuing should have a fresh ERS printout. That’s an instruction about scope. It isn’t a refund deadline.

First, check that the customer’s instruction, the cancelled selection and the continuing record all agree. A mistake here can make a partial cancellation look like a whole one. Then find the original agent-charge line on the invoice. Don’t split it into passenger shares just because only part of the booking was cancelled. Ask the provider which term covers that line for this partial cancellation. Hearing “agents can’t charge again for cancellation” again doesn’t answer it.

Mark each question as settled only when the reply deals with that part and that stage. An explanation of the term doesn’t prove the amount was worked out correctly. And an amount doesn’t explain the term.

What does a worked example look like?

Here’s a made-up case, to practise the order of thinking. A customer asks to cancel two of four passengers on an agent-booked PNR. You have the invoice. You don’t yet have the term that says what happens to the original agent charge. No fare, deduction or deadline is assumed here, so every figure stays blank until a real record supplies it.

You’d work through it in this order:

1. Confirm what was cancelled. Match the customer’s words with the cancellation record. Which two passengers were selected, and who is still travelling?
2. Find the original lines on the invoice. The railway fare, the agent charge, IRCTC’s own charge and any payment-related charge are separate lines. Keep them separate.
3. Ask about the agent line only. “Which term explains this original agent-charge line for this partial cancellation?” If the reply only sends the new ERS, thank them and ask again. If it only sends an amount, ask how that amount covers the named line.
4. Read the assessed refund. If the breakdown doesn’t separate the components, ask for one. A rounded difference between two totals doesn’t tell you which fee was taken.
5. Trace the credit. Find the credit with its reference and date. If you can’t find a match, mark that stage pending and ask the channel to trace it.
6. Then trace the payment to the customer. Keep their payment acknowledgement, and compare its amount and reference with what was agreed.

Notice what the worked case never does. It never guesses a fee, and it never splits the agent charge by head count.

Can you see the whole thing as one worksheet?

Sometimes a single grid helps. The one below is a reconciliation worksheet for the made-up case above, not an official refund schedule. Every unknown cell says what evidence you need, instead of filling in a nice-sounding answer.

The original agent-charge question stays open in this grid because the sources used here don’t say whether it returns or stays. That’s a different gap from the question of payment-gateway treatment, which is also still being confirmed with IRCTC. Don’t mix the two.

What if the passenger can’t complete the cancellation OTP?

Treat it as its own issue. Describe the exact message, and note which passenger’s mobile it went to. Work out which cancellation was actually requested, and whether the passenger’s message was received at all. Use the booking agent and the official support route to look into it. And until the cancellation is truly completed, don’t speak as if a final refund has been assessed and paid. State the narrower fact: “the cancellation isn’t complete yet, because the OTP step is pending.”

What should you tell the customer?

Keep it short, and follow the same order. Say which passengers were cancelled. Say which terms you’ve established, and which one you haven’t. Give the amount assessed, where the credit stands, and what’s already been paid. Then name the one open item.

For example: “The cancellation for two passengers is recorded. The railway refund shown is the amount on the receipt. I’m still waiting on the written term for the booking charge, and I’ll tell you the result as soon as I have it.” That is clear and it promises nothing you can’t back up.

Don’t say the original total will return. Don’t say every original fee will be kept. You don’t know either yet. If the customer asks about one charge, answer that one first, and don’t send every document at once. If the question grows to include a railway deduction or a missing credit, add it as its own item.

What mistakes should you avoid?

• Adding a handling fee for cancelling. IRCTC’s agent policy applies the agent charge to booking, not cancellation.
• Calling the original charge refundable, or kept, without a written term. Neither is established by the no-new-charge rule.
• Dividing the agent charge among passengers. The charge is per PNR, not per passenger.
• Treating an OTP as proof of a refund. An OTP only authorises the cancellation. It tells you nothing about the money.
• Sending a login OTP to anyone who asks. The cancellation OTP and your login OTP are different things, and the second one stays with you.

Who do you ask about a disputed line?

Existing SiOnline agents should send SiOnline support the PNR, the cancellation reference and the receipt line that’s being questioned. Passengers should contact the agent who booked the ticket, rather than picking a random provider from a search. Use customer care to separate an agent-account issue from a passenger’s booking enquiry.

Keep a short list of the answers you get. If the person you asked can’t see the record, ask who can, and write that down too. That stops the customer from being passed from one help line to another with nobody looking at the actual charge.

Sources

• IRCTC: Agent Policy, retrieved 18 October 2026.
• Ministry of Railways: cancellation and refund reform announcement, 24 March 2026, retrieved 18 October 2026.
• IRCTC User Guide for E-Ticket Cancellation, retrieved 18 October 2026.

Facts checked on 18 October 2026. Confirm the applicable rule and account status before acting.