> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/4.-developer-and-payment-engine/waas/query-transaction-records.md).

# Query Transaction Records

In WaaS projects, transaction history is used to view all business records related to fund flows under the current project, helping users track withdrawals, sub-address transactions, and collection records. Transaction history is mainly divided into the following three categories:

* Withdrawal History
* Transaction History
* Collection History

#### Withdrawal History

Withdrawal History is used to view withdrawal requests initiated via API. Depending on the source of the withdrawal, it is categorized into:

* Wallet Withdrawal: Refers to withdrawal request records initiated through the wallet withdrawal API.
* Sub-address Withdrawal: Refers to withdrawal request records initiated through the sub-address withdrawal API.

<figure><img src="https://3263384427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3NzJ0yGNKhTsgI2zNjK%2Fuploads%2FqJN1CrB55nSG8pjxlWnh%2Fimage.png?alt=media&amp;token=da34bb96-0b5f-46bb-b454-5cd5166ef3d7" alt=""><figcaption></figcaption></figure>

#### Transaction History

Transaction History is used to view transaction records related to the sub-addresses of the WaaS project. Including:

* Receive
* Send

Excluding:

* Collection-related transactions (Collection, Gas Fee Top-up)

Transaction History is categorized into:

* History: Displays transaction records in their final state (Successful, Failed, Canceled).
* In Progress: Displays transaction records that are currently still pending confirmation on the chain.

<figure><img src="https://3263384427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3NzJ0yGNKhTsgI2zNjK%2Fuploads%2FTiGXwm7tELqtcnCmzIVb%2Fimage.png?alt=media&amp;token=4d181925-4737-492d-8c19-2ed89a981db8" alt=""><figcaption></figcaption></figure>

#### Collection History

Collection History is used to view transaction records related to sub-address collection in the WaaS project. Including:

* Collection (Manual Collection, Auto-Collection)
* Gas Fee Top-up

Collection History is categorized into:

* History: Displays collection transaction records in their final state (Successful, Failed, Canceled).
* Processing: Displays collection transaction records that are currently still pending confirmation on the chain.

<figure><img src="https://3263384427-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3NzJ0yGNKhTsgI2zNjK%2Fuploads%2Fnhq6is60hwF82Mf1jCfH%2Fimage.png?alt=media&amp;token=204c6db2-e354-4114-a85e-68016e95b712" alt=""><figcaption></figcaption></figure>


---

# 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://support.cregis.com/4.-developer-and-payment-engine/waas/query-transaction-records.md?ask=<question>&goal=<user_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.