Contact person: Update IRCTC Booking Software Already Made iN c# and .net

Phone:Show

Email:Show

Location: Allahabad, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"My in-house “Instant” ticket-booking tool was built in C# and had been running flawlessly against IRCTC until the recent platform overhaul. IRCTC now sits behind Akamai and has altered both the login flow and the booking page structure. I already have the official, detailed documentation for these changes; I simply need the working code updated so our automated bookings run again without manual intervention.

Key areas that must be refactored
• Akamai edge-token acquisition and verification bypass (the tool must obtain every required cookie/header exactly as the browser does).
• New multi-step login process, including fresh CAPTCHA, OTP and session-keep-alive logic.
• Session tracking throughout the “Login → Search → Select → Passenger → Payment” sequence so tickets reach the payment gateway without an unexpected logout.
• Re-mapping of booking-page requests and any shifted endpoints, parameters or headers exposed in the latest APIs.

Step-by-Step Code Review Strategy
Here’s how we can approach it:
1. Login Flow & Session Handling
- Check if IRCTC has added new hidden fields, tokens, or dynamic headers during login.
- Ensure your code handles session revalidation and doesn’t reuse stale cookies.
- Add logic to detect forced logout or session expiry and reinitiate login cleanly.
2. Captcha & OTP Integration
- IRCTC may now use dynamic captchas (e.g., image distortion, click-based challenges).
- If you're using OCR, consider switching to manual input fallback or external solving APIs with human-in-the-loop.
- OTP flow might now require device fingerprinting or session binding—check if OTP is tied to a specific login session.
3. Booking Page Access
- Booking pages may now include JavaScript-based validation or CDN tokens.
- Use a headless browser (e.g., Selenium with stealth plugins) to simulate real user behavior if raw HTTP fails.
- Monitor for rate limits or IP throttling—rotate IPs ethically or use verified account

Form Autofill & Submission
- IRCTC may have randomized field names or added anti-bot JS checks.
- Ensure your autofill logic mimics human typing speed and order.
- Add delays, mouse movement simulation, and randomized intervals to avoid detection.
5. Error Handling & Logging
- Implement detailed logging for each step: login, captcha, OTP, form load, submission.
- Capture and analyze error codes, redirects, or unexpected HTML changes." (client-provided description)