Skip to content

AirScalp purchase logic

How AirScalp Decides to Book

A clear look at the checks AirScalp runs before an authorized booking can happen.

A target-price match starts a decision. It does not by itself authorize a purchase. A booking-enabled rule must still pass the current itinerary, availability, price, time, payment, and authorization checks.

The pre-booking checks

  1. Rule status: active, not paused, not expired, and not previously completed.
  2. Itinerary: airports, dates, passengers, cabin, stops, and supported trip limits still match.
  3. Availability: the fare and required seats remain available.
  4. Total price: the refreshed total remains inside the hard maximum.
  5. Action mode: approval is present when required or automatic action is explicitly enabled.
  6. Payment readiness: the authorized payment method is available for the rule.

Reasons AirScalp should stop

A price increase, itinerary change, unavailable seat, expired rule, missing approval, provider error, or failed payment check should stop the attempt. The outcome belongs in the audit trail instead of being silently retried beyond the rule.

Confirmation is the finish line

A detected fare is not a ticket. A booking is complete only after the airline or booking provider confirms it. Until then, availability and price may change.

Designed by Envy Leads