You’re at the counter, the customer is watching, and the screen says the booking failed. Then you look at your wallet and the money has gone. No ticket, no PNR, and a debit sitting there. It’s an uncomfortable moment, especially when you’re not sure what to say.

This is a short guide to what a failed booking actually is, what you can tell the customer, and when it’s time to ask support to take a look.

What is a failed booking?

A rail booking isn’t one single step. It’s a reservation request, a payment authorisation, and a confirmation that gets written back to you. A failure is a break somewhere between those steps. A few typical cases:

The seat was taken before your request completed. No PNR is generated.
The payment went through but the reservation timed out. The railway system didn’t respond in time.
The session expired mid-booking. Nothing was committed.

In each of these, no PNR exists. And if no PNR exists, no ticket was issued. A PNR is the reference number a booked ticket gets. No PNR, no ticket.

That’s the one test worth remembering. Before you say anything else to the customer, check whether a PNR was generated.

Did the booking really fail? Check before you tell the customer

Don’t rely on memory, and don’t rely on the first thing the screen showed. Open your booking history and look. Is there a PNR for this customer, this train and this date? If yes, it isn’t a failed booking, and you’re in the cancellation or TDR world below. If no, carry on.

This also protects you from a different mistake. If you think the first attempt failed and you book the same journey again, check the history first. Otherwise you could end up with the customer holding two tickets they didn’t ask for.

What should you tell the customer?

Keep it plain and accurate. Something like:

“The booking didn’t complete, so no ticket was issued. The failed transaction gets reconciled. I’ll check your wallet statement, and if the money hasn’t come back I’ll take it up with support.”

Notice what that doesn’t say. It doesn’t say “it will be refunded” (nothing was sold, so there’s nothing to refund). It doesn’t give a number of hours or days. And it doesn’t blame the customer or the railway. You’re describing what you know and what you’ll do next.

Please don’t use “refund” for a failed booking and a cancellation in the same breath. They’re different things, and the customer will remember whichever word you used.

Failed booking, cancellation or TDR: what’s the difference?

These three get mixed up all the time, and each one has its own route.

A failed booking never produced a ticket. Nothing was sold, so there’s no cancellation charge.

A cancellation is a ticket that did exist and is being given up. Railway cancellation rules apply, and the refund is net of those charges.

A TDR is a refund claim, used when the normal cancellation route isn’t available. If a PNR was generated but the ticket isn’t usable, that’s a cancellation or a TDR case, not a failed booking. Read how to submit an IRCTC refund request for that route. If the cancellation involves an OTP step, how to verify the OTP for an IRCTC cancellation or refund walks through it.

Be specific with the customer about which of the three happened. “It will be refunded” said about the wrong one is how a disagreement starts two days later.

When should you contact support?

Contact support when your wallet statement still shows the debit and the booking history shows the booking as failed, or shows nothing at all. Before you do, check four things.

Was a PNR generated? Look in your booking history, not in your memory.
What’s the transaction reference? You need the actual reference, not the approximate time.
What does your wallet statement show? Confirm the debit is still there and hasn’t already been reversed.
Is this a one-off? If several bookings failed in the same period, say so up front.

A request without a transaction reference can’t be traced. So send the reference, the date and time, the amount and the passenger details together. That turns a long back-and-forth into one message.

What a good message looks like

You can adapt this:

“A booking for [passenger name], [train and date], failed and no PNR was generated. My wallet shows a debit of ₹[amount] on [date] at [time], transaction reference [reference]. It hasn’t been reversed. This is the only failed booking today. Please check.”

Add your agent ID. Never include a password or an OTP.

What if you’ve already taken money from the customer?

Sometimes the customer has paid you before the booking is attempted. If the booking fails, tell them plainly what happened: the booking didn’t complete and no ticket was issued. Then ask what they’d like to do next. They might want you to try again, or they might want to change their plans.

Don’t quietly use their money for a different journey, and don’t treat the original request as permission to book something else. A different train, date or class is a new decision, and it belongs to the customer.

What should you avoid promising?

A few things are tempting to say at the counter, and it’s better not to say them.

A timeframe. Don’t give hours or days for the reversal. You don’t know it, and the customer will hold you to it.
“It’s already refunded.” Check the wallet statement first.
“It’s automatic, don’t worry.” The accurate version is that failed transactions are reconciled, and that you’ll contact support if the reversal hasn’t reached your wallet.
A cancellation charge. A failed booking has none, so don’t mention one.

A small note worth keeping

Each time a booking fails, jot down the same few things. It takes a minute, and it’s what support will ask for anyway.

What to note	Why it matters
Passenger name, train and date	So the request matches the right booking
Whether a PNR was generated	Tells you if it’s a failed booking or a cancellation case
Transaction reference	The one thing support needs to trace it
Debit date, time and amount	Matches the entry on your wallet statement
Whether it reversed	Closes the case, or starts the message to support
Any other failures that day	Tells support if it’s a pattern

An example, start to finish

Say a customer asks for a ticket, you submit the booking, and the screen shows an error. This is an example, not a real case.

You open the booking history. There’s no PNR for that journey. You open the wallet statement and see the debit. You note the transaction reference, the date, the time and the amount, and you tell the customer the booking didn’t complete and no ticket was issued. You ask whether they’d like you to try again once you’ve confirmed the first attempt left nothing behind.

If the debit has reversed by then, you carry on. If it hasn’t, you send the message above to support. At no point did you promise a refund, give a timeline or tell the customer to wait without knowing what you were waiting for.

Questions agents ask

Is a failed booking the same as a cancellation?

No. A failed booking never produced a ticket, so there’s no cancellation charge. A cancellation gives up a ticket that existed, and railway cancellation rules apply.

Do I need to file a TDR for a failed booking?

No. A TDR is for a ticket that exists. If no PNR was generated, there’s nothing to claim. Check your wallet statement and, if the debit is still there, contact support.

What if a PNR was generated but the ticket doesn’t work?

That’s not a failed booking. It’s a cancellation or TDR case. See the guide on submitting an IRCTC refund request.

What if the booking history shows nothing but the wallet shows a debit?

Contact support, with the transaction reference, the date, the time and the amount.

What if the customer insists a ticket was booked?

Go back to the booking history and look for a PNR. If there is one, a ticket exists, and you’re no longer dealing with a failed booking. If there isn’t one, show the customer the history so they can see for themselves that nothing was issued. Showing beats arguing.

What if several bookings failed in a row?

Say so up front when you contact support, and send the transaction reference for each one. A run of failures in the same period is a different conversation from a single failed booking, and support needs to know which one they’re looking at. Stop retrying for that customer until you’ve checked the booking history, so you don’t create extra debits or tickets nobody asked for.

How do I reach support?

Support runs 24 hours, 7 days. Call or WhatsApp +91 91091 35959, or see customer care. For something that has gone wrong on your account, the support page is the place to start.

IRCTC Refund for a Failed Booking: Agent Guide