Useful answers for searching, booking, payments, accounts and travel planning.

The current platform supports end-to-end simulated flows for flights, hotels, holiday packages, buses, trains, cabs and activities, plus informational visa, cruise and travel-insurance discovery.

Not in this static release. Inventory and confirmations are seeded for product demonstration. The architecture is designed so approved live supplier services can replace the static providers later.

Yes. Sign in and open My Trips to review upcoming, completed and cancelled bookings, payment status, travellers and printable invoice details.

Yes. The account area includes reusable traveller profiles for name, date of birth, nationality and optional passport information.

Yes. The search studio supports one-way, round-trip and multi-city planning interfaces. Static search results are generated from seeded routes and fares.

No. Seeded schedules are designed for interface testing. Production schedules must come from an authorised airline or GDS/NDC supplier integration.

Each seeded hotel includes multiple room categories with occupancy, meal plan, cancellation wording, room rate and taxes so the complete selection and checkout flow can be tested.

No. Ratings and review counts are seeded merchandising data used to demonstrate sorting and presentation. A live product should only show verified or properly sourced review data.

Yes. The bus flow includes an interactive seat selector. Selected seat numbers are carried into checkout and reflected in the booking summary.

No. Train availability is static sample data. The site must not represent it as IRCTC availability unless an authorised production integration is implemented.

Seed data includes hatchbacks, sedans, SUVs and premium vehicles with passenger capacity, luggage allowance, included kilometres, base fare and tax.

Each package displays accommodation, selected transfers, listed experiences and day-wise itinerary information, together with exclusions and cancellation wording.

No. The mock payment flow is for test values only and is intentionally separated behind a payment gateway interface. A production gateway should use hosted or tokenised payment controls.

The server resolves the selected inventory price and then calculates taxes, the configured service fee and any valid coupon discount. Browser-submitted totals are not trusted.

A booking record is created with failed payment status so the failure state can be demonstrated without moving real money.

Coupons can be flat-value or percentage discounts with minimum amounts, maximum discount limits, usage limits and validity dates.

No. Visa content is an informational interface template. Always confirm current requirements through the relevant government, embassy, consulate or authorised official source.

No. Insurance provider names and benefits in this static release are fictional product data. A production platform should connect only licensed providers and their authoritative policy wording.

Sign in, open Security in your account panel, enter your current password and choose a new password.

Use the Delete Account page while signed in or submit the public account-deletion request form using your registered email.

A production operator may need to retain limited records for tax, accounting, fraud prevention, dispute handling or other legal obligations. The final retention policy should be reviewed by qualified counsel.

Use the Contact page, configured support email, phone or WhatsApp details. All business contact information is editable in Admin Settings.

Yes. The current architecture leaves room for company profiles, traveller policy rules, approval workflows, GST invoicing, cost centres and reporting.

Yes. Travel categories use service interfaces and static implementations so a real supplier implementation can be bound later while keeping controllers and views largely unchanged.