> For the complete documentation index, see [llms.txt](https://piqpay.gitbook.io/merchant-integration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://piqpay.gitbook.io/merchant-integration/callback/list-of-order-payout-statuses.md).

# List of Order/Payout statuses

There is a "type" field in the Callback JSON which stores the current status of the order/payout.

**PAYMENT**

\* PAYMENT\_ORDER\_CREATED (not final, initial status)

\* PAYMENT\_ORDER\_COMPLETED (final successful status)

\* PAYMENT\_ORDER\_EXPIRED (not final fail status; the status can changed if your client pays for the order)

\* PAYMENT\_ORDER\_CANCELLED (not final fail status; the status can changed if your client pays for the order)

<br>

**PAYOUT**

\* PAYOUT\_CREATED (not final, initial status)

\* PAYOUT\_COMPLETED (final successful status)

\* PAYOUT\_EXPIRED (final fail status, after 24 hours delay)

\* PAYOUT\_CANCELLED (final fail status)

By default, the callback is sent to the URL specified in the Subscriptions tab in your Bussinesoffice. If you want to get the callback to another URL, specify it in the "callbackUrl" parameter in the request body.


---

# 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:

```
GET https://piqpay.gitbook.io/merchant-integration/callback/list-of-order-payout-statuses.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.