Help a Customer Authenticate IRCTC Aadhaar
Help a customer authenticate their own IRCTC account with the official Aadhaar guide, while keeping personal credentials and agent bookings separate.
A customer walks in holding their phone. “It won’t let me book Tatkal. It keeps asking about Aadhaar.” You’ve seen this before, and you can help. But there’s a right way to do it, and a few ways that cause trouble for both of you.
The short version: the profile belongs to the customer, so the customer does the typing. You can guide them through IRCTC’s official steps. You shouldn’t hold their password, read their OTP, or book from their personal account. The sections below show what to say and what to watch for at each step.
Which kind of booking does the customer mean?
Start here, because two different rules get mixed up. As checked on 18 October 2026, PIB’s Tatkal announcement says online Tatkal on IRCTC’s website and app needs an Aadhaar-authenticated user from 1 July 2025, and Aadhaar-based OTP from 15 July 2025.
Tatkal through an authorised agent works differently. The announcement says it needs an OTP sent to the mobile the user gives at booking. So preparing a personal profile with Aadhaar is one job, and giving the passenger’s mobile number for an agent booking is another.
Ask the customer which one they want. If they’re setting up their own account, follow the official guide below. If they want you to book through your agent ID, explain that route, and tell them about the agent Tatkal timing restriction.
What should the customer have ready?
IRCTC’s Aadhaar authentication guide, retrieved 18 October 2026, asks for the account holder’s Aadhaar number or Virtual ID. The verification OTP goes to the mobile registered with Aadhaar. The name, date of birth and gender shown on the profile have to match Aadhaar.
So before you start, ask two things. Do you have your Aadhaar number or Virtual ID handy? And do you have the phone that’s registered with Aadhaar, with you, switched on? If the answer to the second one is no, there’s no point going further today.
Let the customer type the sensitive details themselves. Don’t write Aadhaar numbers or OTPs on a shop worksheet, take a screenshot of them, or paste them into a support message.
What are the steps on IRCTC’s website?
These steps follow the official guide, checked on 18 October 2026. Use the customer’s own account. If the live page looks quite different from what’s described here, stop and sort that out first.
- The customer signs in on IRCTC’s website and opens MY ACCOUNT, then Authenticate User.
- They enter their Aadhaar number or Virtual ID, and check that the name, date of birth and gender on screen match Aadhaar.
- If something needs fixing, the guide offers an Edit option for those profile details before authentication. Check the corrected values before moving on.
- They select Verify details and receive OTP. The OTP goes to the mobile registered with Aadhaar.
- They enter the OTP, read and agree to the consent shown, then submit.
- They close the window and log in again. The guide shows a green tick next to the username, and at Authenticate User, as the sign that it worked.
How do you tell where you are, and when to stop?
If things stop halfway, work out the last stage you actually reached. This table pairs each stage with what the guide says you should see. The “when to stop” column is our suggestion for keeping the job inside the published guidance. It isn’t an extra official screen.
| Stage | What the guide describes | When to stop |
|---|---|---|
| Open the profile task | Sign in, MY ACCOUNT, then Authenticate User; the authentication page appears | Wrong account, or a very different page: stop and work out the right task |
| Compare identity details | Enter Aadhaar number or Virtual ID; compare name, date of birth and gender; Edit is described before authentication | A value doesn’t match and no correction is offered: don’t guess it |
| Request the OTP | Verify details and receive OTP sends the message to the mobile registered with Aadhaar | That phone isn’t available: pause, and don’t use someone else’s |
| Submit | Enter OTP, agree to the consent, submit | The customer hasn’t understood the consent: let them read it first |
| Check the result | Success message, then close and log in again; green ticks appear | No green tick: note the actual stage or error, and don’t say it worked |
| Get more help | The guide points to IRCTC’s eQuery service | Ask about the exact stage where you’re stuck |
Source: the profile-authentication section of the IRCTC Aadhaar guide, checked on 18 October 2026.
What if authentication fails?
Read the error before you try again. If the profile details don’t match Aadhaar, use only the correction route on the official page. The guide says name, date of birth and gender can be changed only before Aadhaar authentication, not after. So please don’t guess a spelling or a date just to make the form go through.
If the OTP doesn’t reach the required phone, don’t swap in another person’s Aadhaar or mobile. Stop, and describe the real problem when you ask for help. The guide points users to IRCTC’s eQuery service for further help.
Mobile numbers can add to the confusion. A customer may also want to separate their personal IRCTC mobile from the Aadhaar-linked one. The personal account mobile guide covers that, and one thing to remember: updating one record doesn’t update the other.
IRCTC’s guide also separates authenticating the user profile from authenticating passengers through Add/Modify Master List. They’re different sections. A saved passenger entry doesn’t show that the profile itself is authenticated.
What does it look like when two things go wrong at once?
Here’s an example. It isn’t a real customer, and it has no real numbers in it. A customer wants to get their own profile ready for online booking. They can sign in. But a value shown on the profile doesn’t match their Aadhaar record, and the phone linked to Aadhaar isn’t with them today.
Treat these as two separate problems. For the mismatch, ask the customer to compare the field with their own record and point out the difference themselves. If the correction option is there, they use it and read the corrected value. Remember the boundary in the guide: those fields can be changed only before authentication. So don’t promise to finish the authentication now and fix the details later.
For the phone, the guide sends the OTP to the mobile registered with Aadhaar. It doesn’t describe sending that OTP to any number you choose. Don’t use your own phone, and don’t change an IRCTC contact field and then announce that the Aadhaar phone has changed. This article doesn’t cover how to update an Aadhaar-linked mobile.
Even if the customer fixes the mismatch, the phone problem is still open. One fix shouldn’t hide the other. Tell the customer plainly: “Your profile detail is sorted, but we can’t finish today because the OTP phone isn’t here.” And don’t call it a failed ticket booking, because no booking was tried.
Which tasks sound alike but aren’t?
A few requests use similar words. Sort out which one you’re dealing with before you do anything.
| The customer says | What the task is | What not to assume |
|---|---|---|
| “Is my own login authenticated?” | The profile-authentication section; check its actual result | A saved passenger doesn’t answer this |
| “I’m looking at a saved traveller” | Passenger-list editing, a different task | Don’t change the account holder’s identity just to edit a traveller |
| “Book it through your agent ID” | An agent booking, with the OTP to the mobile given at booking | A personal profile result is not permission to use the agent’s credentials |
If the customer changes the request halfway, say the new task out loud. Helping with a profile doesn’t automatically cover editing passengers or making a paid booking.
Can the shop book from the customer’s account?
No. IRCTC’s agent policy prohibits agents from selling tickets booked through personal IDs, and it prohibits sharing agent access credentials. Showing a customer how to read an authentication page doesn’t give the shop permission to make commercial bookings from that personal account.
Use the agent login guide for your own authorisation. If the issue is about a passenger’s own ticket or account, send them to the customer-care routing page.
How do you ask for help without leaking anything?
If you need to ask IRCTC’s help route, keep the question narrow. Something like: “The customer can sign in and reached the profile comparison stage. One profile value doesn’t match Aadhaar, and the Aadhaar-linked phone isn’t available. Which official action applies?”
Share only the account reference the help route asks for, plus the stage and the error. If you need a screenshot, hide anything unrelated, such as identity fields. Never post a customer’s Aadhaar image, password or OTP in a public group to get a faster reply.
And read the reply against both problems. An answer about correcting a value may not say anything about the phone. Mark off only what was answered, and ask a short follow-up on the rest.
How do you close the session?
When the task is finished or paused, ask the customer to sign out, so their details aren’t left on screen for the next person. In your own note, write down which stage was reached and which question is still open. Leave the identity numbers out.
Don’t issue a shop certificate saying the customer is Aadhaar-authenticated. The guide’s own check is the success message, followed by the green tick after logging in again. That tells you about the profile. It isn’t a train reservation.
Questions customers ask
Can you do the Aadhaar authentication for me?
You can talk the customer through it, but they enter their own Aadhaar details and OTP. That’s their identity and their profile.
Does authenticating my profile mean an agent can book Tatkal for me?
No. They’re two different rules. Authentication is for online Tatkal on the IRCTC website and app. For Tatkal through an agent, the announcement asks for an OTP to the mobile given at booking.
The details on my profile don’t match Aadhaar. What now?
Use the Edit option on the official page, but only before authentication. After that, the guide says those fields can’t be changed through that route. Don’t guess a value to make it match.
Sources
- IRCTC: Authenticate IRCTC User Profile with Aadhaar, retrieved 18 October 2026.
- PIB: Aadhaar and Tatkal booking measures, retrieved 18 October 2026.
- IRCTC: Agent Policy, retrieved 18 October 2026.
Confirm the applicable rule and account status before acting.
Registration is ₹3,000
Incl. GST, one-off. We check your eligibility before you pay.
IRCTC agent registrationSupport runs 24 hours, 7 days
If this guide does not cover your case, call and ask. You will get a person who knows the rules.
+91 91091 35959Start your registration
Takes about a minute. Submit your details below. No payment at this stage.