> 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/post-booking-overview/post-booking-operations/refunds.md).

# Refunds

{% 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 section for the full refund lifecycle.

Start here when you need to:

* decide whether the case should use **Refund** or **Void**
* follow the standard refund sequence
* confirm which identifiers to keep for follow-up

### FAQ

#### What is the standard Atlas API refund flow?

The standard flow is `refundQuotation.do` → `refund.do` → `queryRefundOrders.do`.

Start with quotation before submission.

#### When can a refund request fail even before submission?

Refund requests can fail when ticketing is not complete, the refund offer expired, the order number is wrong, or the itinerary is incomplete.

Check current order state and refund conditions first.

#### When should I use Refund instead of Void?

Use Refund when the case is outside the void window or needs the refund flow.

Use [Void](/api-document/readme/post-booking-overview/post-booking-operations/void.md) when the order is still eligible for the dedicated void flow.

### Typical flow

{% stepper %}
{% step %}

### Check refund eligibility

Call `refundQuotation.do` first.

Confirm the latest refundable amount and conditions.
{% endstep %}

{% step %}

### Submit the refund

Use the latest `refundOfferId` when the flow requires quotation-based submission.

Keep the returned `refundCode`.
{% endstep %}

{% step %}

### Query final status

Use `queryRefundOrders.do` until the case is completed, rejected, or otherwise closed.
{% endstep %}
{% endstepper %}

### What should you confirm before refund submission?

Confirm:

* the original `orderNo` is correct
* ticketing is complete when required
* the itinerary in the refund request is complete
* the latest `refundOfferId` or quotation result is still valid

The refund path and reconciliation timing can also depend on the payment mode.

### Use this page when you need

* voluntary refunds
* involuntary refunds
* refund status follow-up

### What this page does not cover

This page does not list full endpoint schemas or field-level definitions.

Use the API reference for request and response details.

### Full API reference

Use endpoint-level details here:

* [Refunds](/api-document/api-reference/post-booking-apis/refunds.md)

### Related pages

* [Void](/api-document/readme/post-booking-overview/post-booking-operations/void.md)
* [Finance](/api-document/troubleshooting-and-support/faqs/atlas-api-finance.md)
* [Post-booking](/api-document/troubleshooting-and-support/faqs/atlas-api-post-ticketing.md)
* [Error Codes](/api-document/troubleshooting-and-support/errors-handing.md)
* [Post-booking APIs](/api-document/api-reference/post-booking-apis.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/post-booking-overview/post-booking-operations/refunds.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.