> For the complete documentation index, see [llms.txt](https://stablemesh.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stablemesh.gitbook.io/docs/home/stablemesh-doc/cards/transactions.md).

# View Transactions

Every card maintains a complete log of its spending activity. Use this to track purchases, spot issues, and reconcile expenses.

***

## How to View Transactions

1. Go to **Cards** and click any card.
2. In the detail panel, scroll down to the **消费记录** (Transaction History) section.
3. Transactions are listed in reverse chronological order (newest first).

***

## Transaction Details

Each transaction entry shows:

| Field           | Description                                              |
| --------------- | -------------------------------------------------------- |
| **Merchant**    | Name of the store or service charged                     |
| **Date & Time** | When the transaction occurred                            |
| **Amount**      | Value in USD (negative = charge, 0 = authorisation only) |
| **Status**      | Outcome of the transaction                               |

***

## Transaction Statuses

| Status      | Meaning                                       |
| ----------- | --------------------------------------------- |
| `COMPLETED` | Transaction was successful and funds deducted |
| `FAILED`    | Transaction was declined or failed            |
| `REVERTED`  | Transaction was reversed and funds returned   |

***

{% hint style="info" %}
If you see an unexpected transaction, freeze the card immediately using the **snowflake icon** in the detail panel, then contact Stable Mesh support.
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://stablemesh.gitbook.io/docs/home/stablemesh-doc/cards/transactions.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 `build a script that syncs our docs to a CMS` 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.