> For the complete documentation index, see [llms.txt](https://tegro.gitbook.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tegro.gitbook.io/en/tegro-money/background-information/payment-statuses.md).

# Payment statuses

## Waiting

Usually the status is immediately changed to successful or erroneous, but in case the user has not completed the payment, left the 3DS stage, form or other, the status may remain for a certain period of time.

This usually lasts for 24 hours, after which the timeout ends. At this point the payment can still take the status "Paid" if the customer completes the payment.

In some situations, the wait lasts longer, but payments that have been pending for more than 24 hours almost always go into error.

## Paid

The payment was successful.

## Error

Status is final, there may be many reasons, contact support.

## Cancelled

Most often it is assigned when the payment is not completed in the timeout we specified *(e.g., left the payment page or widget, 3DS code is incorrect or not entered, etc.).*

## Rejected

This status occurs when an erroneous response to our "Check" request is sent to your payment processor URL.


---

# 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://tegro.gitbook.io/en/tegro-money/background-information/payment-statuses.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.