> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/transaction-types.md).

# Transaction Types

Learn the instructions Brava executes and records.

## Transaction Types

Six things you can instruct. Everything else in history is Brava’s plumbing, recorded so you can see it.

### What you instruct

| Type           | What moves                                               | Where from          |
| -------------- | -------------------------------------------------------- | ------------------- |
| **Deposit**    | Custody wallet into the workspace                        | Portfolio → Actions |
| **Withdrawal** | Workspace back to the custody wallet                     | Portfolio → Actions |
| **Allocation** | Cash holdings into a strategy                            | Strategy → Actions  |
| **Redemption** | A strategy back to cash holdings                         | Strategy → Actions  |
| **Rebalance**  | Between a strategy’s holdings. The total does not change | Strategy → Actions  |
| **Transfer**   | One strategy to another, in the same workspace           | Strategy → Actions  |

Deposits and withdrawals cross the custody boundary. The other four move capital inside the workspace.

### What Brava records

History also carries types you do not instruct directly. They are steps of a larger operation, or classifier verdicts.

| Type                         | What it means                                      |
| ---------------------------- | -------------------------------------------------- |
| **Cross-Portfolio Transfer** | The recorded form of a transfer between strategies |
| **Pending Bridge**           | A bridge leg in flight between two chains          |
| **Drifted Bundle**           | On-chain results did not match the plan            |
| **Anomalous**                | Movement the classifier could not attribute        |
| **Unknown**                  | The classifier reached no verdict                  |

These are not errors by definition. A Pending Bridge is a healthy cross-chain allocation mid-flight. Drifted and Anomalous are worth reading.

### Status

| Status                 | Meaning                                             |
| ---------------------- | --------------------------------------------------- |
| **Complete**           | Settled, in full                                    |
| **Pending**            | Submitted, not yet settled                          |
| **Partial**            | Some legs settled, others did not                   |
| **Failed**             | Did not settle                                      |
| **Bridge In Progress** | Funds left one chain and have not arrived           |
| **Bridge Stuck**       | A bridge leg has not settled in the expected window |
| **Bridge Failed**      | A bridge leg did not complete                       |

Partial and bridge states exist because a cross-chain transaction uses several transactions. One can settle while another does not.

### Filtering

The **Transactions** screen filters by type, status, strategy, and date. Type pills cover the five you instruct most. The table lists everything.


---

# 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.brava.finance/platform/transaction-types.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.