> 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/api-document/readme/booking-overview/confirm-order.md).

# Confirm Order (FR only)

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this page only for FR booking flows.

This page uses `Confirm Order` as the primary name.

You may also see this step called `Order Commit`.

{% hint style="info" %}
Most airlines do not use this step.

For standard booking flows, call `order.do` and then `pay.do`.

Only FR inserts `orderCommit.do` between those two steps.
{% endhint %}

### Main API

* `orderCommit.do`

### When this step applies

Use `Confirm Order` only when:

* the airline is FR
* the booking flow returns an FR confirmation page
* the user must complete FR confirmation before payment

Skip this step when:

* the airline is not FR
* the order can go directly from `order.do` to `pay.do`

If you are building a standard booking flow, do not add `Confirm Order` as a required step.

### Where it sits in the flow

#### Standard flow

* `verify.do`
* `order.do`
* `pay.do`

#### FR flow

* `verify.do`
* `order.do`
* `orderCommit.do`
* user completes FR confirmation
* `pay.do`

### Notes

* This step is airline-specific
* It is required for FR
* Payment must wait until FR confirmation finishes
* `Confirm Order` and `Order Commit` are the same step

### What you get back

Atlas returns a `confirmationUrl`.

Use it in:

* popup mode
* iframe mode

### Related pages

* [Create Order](/api-document/readme/booking-overview/create-order.md)
* [Payment & Ticketing](/api-document/readme/booking-overview/payment-and-ticketing.md)
* [FR Integration](/api-document/readme/special-integrations/fr-integration.md)
* [Booking APIs](/api-document/api-reference/booking-apis.md)

### Full API reference

See endpoint-level details here:

* [Confirm Order](/api-document/api-reference/booking-apis/confirm-order.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/booking-overview/confirm-order.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.