> For the complete documentation index, see [llms.txt](https://docs.payengine.co/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payengine.co/developer-docs/processing-payments/introduction/transaction-flow-and-status.md).
# Transaction Flow and Status
Transaction request will initiate the following flow based on the request type
### Transaction Sale
When the transaction sale is initiated, it will be processed and added to the current day's batch. At this stage, this transaction can be voided
Once the batch is closed, the settlement process will be initiated and settled subsequently. After the transaction is settled or batch closed, it can be only refunded
### Transaction Auth and Capture
When the transaction auth is initiated, it will hold funds on the customer's card but it won't be settled until this transaction is captured separately.
A capture transaction will follow the same flow as sale transaction and it will be added to the current day's batch once captured.
---
# 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://docs.payengine.co/developer-docs/processing-payments/introduction/transaction-flow-and-status.md?ask=&goal=
```
`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.