> For the complete documentation index, see [llms.txt](https://developers.shopbase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.shopbase.com/tutorial/manage-orders-and-shipping/manage-orders-with-the-rest-admin-api/transaction.md).

# Transaction

Transactions are created for every order that results in an exchange of money.

![](https://i.imgur.com/JCO5TTz.png)

There are five types of transactions:

* **Authorization**: An amount reserved against the cardholder's funding source. Money does not change hands until the authorization is captured.
* **Capture**: A transfer of the money that was reserved during the authorization stage.
* **Void**: A cancellation of a pending authorization or capture.
* **Refund**: A partial or full return of captured funds to the cardholder. A refund can happen only after a capture is processed.

Refund transactions must be created by using the [Refund resource](https://api-doc.shopbase.com/#tag/Refund).

### Note

An order can have no more than 100 transactions associated with it.

## What you can do with Transaction

The Shopbase API lets you do the following with the Transaction resource. More detailed versions of these general actions is [available here](https://api-doc.shopbase.com/#tag/Transaction).


---

# 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://developers.shopbase.com/tutorial/manage-orders-and-shipping/manage-orders-with-the-rest-admin-api/transaction.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.