A debited payment with no permit in hand is the moment a safari holiday stops being a planning problem and becomes a banking one. Money has left the account, no ticket has arrived, and every instinct points at the same risky move: pay once more and sort it out later. This article is a troubleshooting workflow for exactly that state. It gives an ordered diagnostic sequence, the evidence to gather, the official channels to use, and a clear statement of what the reserve does and does not publish about payment failures. It repeats none of the gate-day advice that already exists elsewhere on this site, and it promises no refund and no timeframe.
Official sources checked on 19 October 2026: the day-visit safari booking flow, the guest login, check booking and e-Verification page, the password and OTP recovery page, and the contact page. The support details as displayed on those pages are the telephone number +91-9411568917 and the address [email protected], with the Rajaji Tiger Reserve Safari Booking Office at 5/1 Ansari Marg, Dehradun, available from 10 AM to 5 PM.
Start by naming the branch you are actually in
Debited without a permit is a headline, not a diagnosis. Five different states produce the same first impression, and each has a different first move. Work through them in order, because the cheap checks come before the expensive ones.
- Debited, no booking record. Nothing appears under your details and no permit arrived. Do not pay again yet. Confirm the debit reference in your bank app, then search the guest login and e-Verification page for a record under the mobile number and email you used.
- Booking exists, email or SMS missing. A record or permit exists in the system but the confirmation never reached you. This is a delivery problem: open the record through guest login, capture the permit or its reference from there, and check spam, blocked senders and any alternate address you may have typed.
- Pending or failed transaction. The bank shows the amount as pending, reversed or under enquiry rather than settled. Record the status word exactly as the bank displays it, note the reference, and treat the money as unresolved until the bank states otherwise.
- Duplicate debit. Two debits for one intended booking. Capture both references with amounts, dates and times, state plainly that only one booking was intended, and ask which transaction, if any, produced a booking record.
- Expired session or abandoned checkout. The payment left your account while the portal session had timed out, or the browser was closed mid-flow. Note the time of the debit against the time of the failure message, and screenshot the message before it disappears.
This first step may clarify the situation, because a record search either finds the booking or establishes, in your own words with your own screenshots, that it does not exist.
The evidence pack to assemble before you contact anyone
Support staff cannot match a story to a transaction; they can only match references. Assemble this list in one document before you write or call:
- Booking date, zone and shift you were attempting to buy, plus the intended visit date.
- Full name, mobile number and email address entered in the booking.
- Bank transaction reference, shown as the UTR or RRN depending on the rail used.
- Amount, date and time of the debit, as displayed by your bank.
- Any application, booking or reference number displayed by the portal.
- Proof of debit: bank statement line, passbook entry or app screenshot showing the reference.
- A one-line statement of the problem, for example: payment debited on this date, no permit or booking record found.
- Screenshots of any error or expiry message, captured with the timestamp visible.
Send the pack through the official contact route only. Never share a one-time password, your account password or your card CVV with anyone, in any channel, including anyone who contacts you claiming to be support. The password recovery page itself describes an OTP delivered to your registered mobile number or email as part of e-Verification, which means an OTP request you did not start is a reason to stop, not a reason to reply.
Order of operations: check, then contact, then decide
The sequence matters as much as the content. First, search for a booking record through the official guest login and e-Verification page, since a completed payment can exist without an email. Second, if you cannot reach the account, use the official password recovery page, which states that a password can be recovered after completing e-Verification through an OTP delivered to the registered mobile number or email address, and asks you to keep the registered mobile and email account ready. Third, if neither route produces an answer, send the evidence pack to the reserve through its contact page, inside the published hours of 10 AM to 5 PM.
Only after that should you consider paying again. Do not pay again immediately before checking guest-login status and contacting the reserve, and do not assume in the other direction either: nothing here says a slot, seat or provisional hold is waiting for you while a transaction is unresolved. An unresolved payment gives you no confirmed permit, and a second payment may simply produce a second debit. The safe position is neutral until the status is known in writing.
What the official pages do not publish
As of 19 October 2026, the reserve publishes no payment-failure refund service-level agreement, no refund timeline, no refund calculator and no payment status lookup. The pages checked cover the booking flow, guest login and e-Verification, password and OTP recovery, and contact details. That absence is recorded here for one reason: a specific number of days, or a promised refund date, coming from anywhere other than the reserve is not something these pages support. Do not accept it, and do not treat the silence as a refusal either; ask for a written answer instead, and keep it.
The same rule applies to your own bank. If the transaction was pending or failed, ask your bank what its own process and enquiry period are, in your own words, and record that answer separately from anything the reserve says. Two different parties, two different processes, two different written answers.
How this differs from the confirmation and gate checklist
Our booking confirmation and gate-day checklist already covers the two headline rules: a payment is not a permit, and you should not pay twice. Read it as the background for this page. This article is deliberately narrower and more procedural: it is the ordered diagnostic workflow you run when the first rule has already been broken by circumstance, with the evidence pack, the branch-by-branch checks and the escalation route spelled out.
Related reading: payments, deposits, UPI and receipts covers how to keep good records before and after a booking, the after-booking checklist covers what to do once a permit exists, and operator verification covers dealing with a third party instead of the portal. None of them states a refund promise, and neither does this one.
Safety rules while a payment is unresolved
- Never share an OTP, password, card CVV or banking login with anyone offering help.
- Deal only with the official pages linked above and the contact details published on them.
- Keep every reference, screenshot and message in one folder with dates attached.
- Do not accept a promised refund date from a third party as an official answer.
- Do not repeat the payment until the status of the first one is known in writing.
- Do not assume a slot or seat is being held for you while the transaction is unresolved.
The discipline is unglamorous: name the branch, gather the references, check the record, contact the reserve through the published route, and wait for a written status before authorising anything new. Stamp your own notes with the date you checked, 19 October 2026 for the official pages cited here, and recheck them close to any decision.
Rajaji payment debited without a permit: questions answered
My payment was debited but I have no permit. What should I check first?
Check for a booking record before you attempt anything else. On 19 October 2026 the reserve publishes a guest login and e-Verification page at rajajitigerreserve.uk.gov.in/VisitorAuth/GuestLogin.aspx, which is the route for signing in as a guest and looking up a booking with a mobile number, so a completed payment can exist even when no confirmation email has reached you. Keep your bank transaction reference ready, search that page first, and only then decide whether anything further is needed.
Where do I check a booking when the confirmation email or SMS never arrived?
Use the official guest-login and e-Verification page, then the official password recovery page if you cannot get in. The password recovery page states that a password can be recovered after completing the e-Verification process, through an OTP delivered to the registered mobile number or email address, and asks visitors to keep the registered mobile and the email account ready. Treat a missing email as a delivery problem until a record search proves otherwise.
What evidence should I send to the reserve about an unclear payment?
Send one complete pack: the booking date, zone and shift you were buying; the full name, mobile number and email address used in the booking; the bank transaction reference such as the UTR or RRN; the amount, date and time of the debit; any application or booking reference shown on screen; and proof of the debit from your bank statement or app. State the problem in a single sentence, attach screenshots showing the reference and timestamp, send it through the official contact page, and keep a copy of everything you sent.
Does the official site publish a refund timeline or a payment status lookup?
No such tool or timeline was found on the official pages checked on 19 October 2026. The reserve publishes the booking flow, the guest login and e-Verification page, the password and OTP recovery page and a contact page, but no published refund service-level agreement, no refund calculator and no payment status tracker. Do not accept a promised number of days from a third party, and do not treat the silence as a refusal either; ask the reserve for a written answer instead.
Should I pay again to secure a slot while the first payment is unresolved?
No, not before you have checked guest-login status and contacted the reserve, and at the same time do not assume that a slot is being held for you in the meantime. An unresolved transaction gives you no confirmed permit, while a repeat payment may produce a second debit against the same intended booking. Search for an existing record first, send the evidence pack, and only pay again after a clear written answer about whether a booking already exists.