> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/payments/status-flags.md).
# Status Flags
### Overview
Status Flags are markers next to a Customer's purchase that tell an Admin what is happening with that purchase at a glance.
They appear on the Purchase Page of the Dashboard and within the Purchase tab of the Reservation or Event side panel.
Click the blue hyperlink to the left of a Status Flag to look further into the purchase.
#### What each Status Flag means
* **Confirmed** — the purchase, or part of it, has been captured
* **Pending** — the system is trying to capture a payment from the Customer
* **Draft** — a purchase was initiated and never completed by the system
* **Settling in X-time** — the system will attempt to capture payment after the countdown ends
* **Canceled** — the Customer or an Admin canceled the purchase
* **Refunded** — an Admin refunded the Customer for some or all of the purchase
* **Charge Failed** — the system could not capture the purchase and an Admin needs to act
* **Expired** — a hold that was not captured within 7 days of authorization, which happens when a Reservation or Event is canceled
* **Processing** — the Customer has completed payment and Stripe is waiting to receive the funds, normally through ACH payments
* **Creating** — while this should rarely happen, it the response from Stripe didn’t reach the server immediately, and I should change to Captured after a browser refresh
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.podplay.app/payments/status-flags.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
