Pricing rules
Travellers compare prices on FlightGPT and then pay on your site. If the two numbers differ for reasons other than a genuine fare change, they stop trusting both of us. These rules keep the gap to real market movement only.
1. The price you send us
1.1 It is the total for the whole party
The price for a search is the amount for all the travellers or rooms in that search — not per person, not per night. We show it as is. For hotels, also send the per-night figure if you have it; we compute it if you don't.
1.2 It includes everything mandatory
Include every charge a traveller cannot avoid to complete the booking:
- airline and government taxes, GST, and airport charges;
- service, booking, processing or convenience fees, however named;
- for hotels, any mandatory resort, facility or service charge;
- the cost of the cheapest payment method, if none of your methods is free.
If a charge genuinely cannot be collected in advance — a tax paid in cash at the hotel, for example — show it clearly on your booking page and tell us in writing before you go live.
1.3 Anyone can get it
The price must be available to every traveller. It must not need a membership, a login, a coupon, a specific bank's card or an app-only offer.
1.4 It is in Indian rupees
FlightGPT shows prices in INR. Send INR and charge in INR. Deals in any other currency are dropped rather than converted.
2. What you may add at checkout
Nothing mandatory. On FlightGPT traffic, UPI, RuPay and consumer debit and credit cards must be payable at the price you sent us, with no surcharge. That is our policy for every partner, whatever your other channels do.
You may offer a discount for a particular payment method, as long as the price you sent us is the highest a traveller would pay and the discount appears only after they choose that method.
3. Optional extras
Seats, meals, extra baggage, insurance, refundable-fare upgrades and similar extras are the traveller's choice. Never pre-select them, never add them by default, and never make them look mandatory.
4. The deeplink lands on the deal we showed
The link we send the traveller to must open your booking page for the exact flight or room rate we displayed. If that fare has sold out, say so on the page and report it with the not_available landing status — do not silently swap in a different, dearer fare.
5. How we check
Your landing events tell us the price the traveller saw on arrival. We compare it with the price we displayed, automatically, for every landing. A difference of up to 1% is treated as rounding. Fares can change between our search and your page, so a single difference is never treated as a breach — we look at patterns across many landings.
You can see your accuracy results in your statement, on the same numbers we use.
6. If there is a gap
We start with a conversation, and almost every case ends there. If a gap continues, in this order we may:
- ask you to fix it within an agreed time;
- rank your deals on the price we verified at your checkout rather than the price you sent;
- pause your deals on FlightGPT;
- end the partnership under your partner agreement, if it continues or is deliberate.
We will always talk to you before pausing anything.
7. Changes
We will give at least 30 days' notice of any change to these rules that asks more of you, and tell you exactly what changed and why.