Atlas Booking Fulfilment and Cancellation Guide

Last Updated: 24 July 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. For 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.

The pricing verification and fulfilment workflow adopts independent mechanisms for price verification, booking issuance, and exception handling. For a detailed guide, see the "Order Cancellation Rules" below.

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.

Order Cancellation Rules

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

1）Full Stack (Search / Verify / Order) Workflow

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

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.

2）Fulfilment API Workflow

This workflow is suitable 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. If the fulfilment request is not successful within 5 minutes of submission, the system will automatically cancel the request. After cancellation, you can resubmit the request based on the system's return results.

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.

• The Fulfilment API workflow supports same-day departure flight bookings, subject to airline’s latest booking deadlines, inventory status, and sales restrictions. Please reserve adequate time for ticketing and exception handling.