> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/popular-topics/ticketing/atlas-booking-fulfilment-and-cancellation-guide.md).

# Atlas Booking Fulfilment and Cancellation Guide

Last Updated: 4 September 2026

This guide applies to booking fulfilment orders submitted through two workflows: 

1. Full Stack (Atlas Search / Verify / Order) Workflow 
2. Fulfilment API Workflow 

#### Ticket Issuance Time Standards 

Atlas ticketing system features efficient processing mechanisms to ensure booking fulfilment for most orders.

**Full Stack (Atlas Search / Verify / Order) Workflow** 

The Full Stack (Search / Verify / Order) workflow applies for business scenarios where you search for and obtain fares through Atlas, complete price verification, place the order, make payment and issue the ticket.

For regular flight bookings submitted through the Full Stack (Search / Verify / Order) workflow, the typical fulfilment timeline is as follows: 

* ≥90% of orders are issued within 5 minutes.  
* ≥98% of orders are issued within 1 hour. 

{% hint style="info" %}
Note: The above timeline depends on the airline's system, inventory, payment, and technical connections all functioning normally. If there are delays or abnormalities in the airline's system, external system anomalies, or other factors beyond Atlas's control, the fulfilment timeline might be affected. The progress is subject to the relevant status returned by the system. 
{% endhint %}

For "last-minute flight" booking where the scheduled departure is less than 15 hours away or scheduled for the same day — an independent real-time pricing/ticketing and timeout mechanism applies: a clear result is returned within 5 minutes of submission (see "Order Cancellation Rules" below).

**Fulfilment API Workflow** 

This workflow applies for business scenarios where you have already received confirmed orders from your passengers. You can then submit relevant information to Atlas to complete price verification and booking fulfilment. 

A clear processing result will be returned within 5 minutes of submitting a fulfillment request (see "Order Cancellation Rules" below). 

#### Order Cancellation Rules 

Depending on the workflow, payment method, customer-specific settings and flight type, Atlas handles cancellations according to the following details:

**Full Stack (Search / Verify / Order) Workflow** 

I. Regular Flight Booking 

a) VCC Passthrough 

Orders will be automatically cancelled by the system if fulfilment is unsuccessful due to the following reasons: 

* Temporary price changes by the airline.  
* The target flight being sold out.  
* Payment card verification failure.  
* No ticket issuance confirmation received from the airline within 2 hours after successful payment.  

 b) Atlas Deposit 

If fulfiment is unsuccessful due to the following reasons, Atlas will first communicate with you to confirm the solution before proceeding:  

* The target flight being sold out.  
* Airline system failure preventing ticket issuance.  

c) Customer-Specific Settings (Applicable to All Payment Methods)  

If specific settings have been set, the system will cancel orders based on the defined conditions. Common settings include:  

* Time-based Settings: For example, setting "Auto-cancel if not issued within timeout period" (e.g., cancel if not issued within 15 minutes after payment).  
* Price Change Settings: For example, setting "Auto-cancel upon price change" (i.e., the system automatically cancels the order if the airline's fare changes).  
* Manual Cancellation: The customer initiates a "Stop Ticket Issuance" request within the system; the order is cancelled after successful system validation. 

II. Last-Minute Flight Booking 

For customers with the last-minute flight feature enabled, eligible orders go through real-time pricing/ticketing with only two possible outcomes:  

* Ticketed within 5 minutes: ticketing result and PNR are returned 
* Not ticketed within 5 minutes: the order is auto-cancelled, with no extended wait or manual handling. 

If ticketing fails, you may resubmit the order based on the system's returned result.

**Fulfilment API Workflow** 

If a fulfillment request isn't ticketed within 5 minutes of submission, the system auto-cancels it; you may resubmit your order. 

{% hint style="info" %}
**Good to Know**

* The two workflows above are independent. You can choose to use them according to your specific business needs or use them in parallel.
* Last-minute flights remain subject to the airline's latest booking deadline, inventory, sales restrictions, and system availability — meeting eligibility does not guarantee successful ticketing. 
  {% endhint %}