> For the complete documentation index, see [llms.txt](https://docs.rivalryze.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rivalryze.com/gems-and-wallet/transaction-history.md).

# Transaction History

Every gem that moves in or out of your wallet is logged. The transaction history is your full audit trail — find it under **Wallet → Transactions** on your dashboard.

## What you'll see

Each entry shows:

* **Date and time** of the transaction.
* **Type** — what category of gem movement (see below).
* **Amount** — positive for credits to your wallet, negative for debits.
* **Description** — what triggered it (e.g., "Joined Contest: Elden Ring Platinum Race").
* **Running balance** — your wallet total after that transaction.

## Transaction categories

| Category              | What it means                                                        | Direction                                             |
| --------------------- | -------------------------------------------------------------------- | ----------------------------------------------------- |
| **Signup bonus**      | Your starter gems on account creation.                               | Credit                                                |
| **Daily claim**       | Your daily login reward.                                             | Credit                                                |
| **Contest entry fee** | You joined a Contest.                                                | Debit                                                 |
| **Contest win**       | You won a Contest's prize pool.                                      | Credit                                                |
| **Contest refund**    | A Contest you joined was cancelled or you left before start.         | Credit                                                |
| **Donation made**     | You donated to a Contest's prize pool.                               | Debit                                                 |
| **Donation received** | You won a Contest that included donations.                           | Credit (shown as part of the Contest win)             |
| **Tip received**      | Another player tipped you (in supported Discord servers).            | Credit                                                |
| **Tip sent**          | You tipped another player.                                           | Debit                                                 |
| **Reward program**    | You completed a reward program goal.                                 | Credit                                                |
| **Shop purchase**     | You bought something in the Shop.                                    | Debit                                                 |
| **Shop refund**       | A Shop order was refunded (e.g., a gift card couldn't be fulfilled). | Credit                                                |
| **Host boost**        | You added a starting boost to a Contest you hosted.                  | Debit (refunded if you win, kept by winner otherwise) |

## Filtering and searching

You can filter the history by:

* **Category** — show only Contest wins, only Shop purchases, etc.
* **Date range** — narrow to a specific week, month, or custom range.
* **Contest name** — find every transaction tied to a specific Contest.

This is especially useful at tax time, end-of-month accounting, or just to figure out where your gems went last weekend.

## Exporting your history

You can export your full transaction history to CSV from the **Wallet → Transactions → Export** button. The CSV includes every column above plus a transaction ID.

{% hint style="success" %}
Keep an exported copy if you're spending a meaningful amount on the platform. It's your record if you ever need to dispute a charge or verify a balance.
{% endhint %}

## Understanding negative balances

You can't have a negative wallet balance — RivalRyze will reject any transaction that would put you below zero. If you try to join a Contest that costs more than your current balance, you'll be prompted to come back when you have enough.

## When something doesn't add up

If your balance doesn't match what you expected:

1. Check the most recent transaction. The "running balance" column will show what your wallet was after that transaction.
2. Look for missing or unexpected transactions. Filter by date range to narrow it down.
3. If you find a discrepancy, contact [support](/help-and-faq/contact-support.md) with:
   * The transaction ID (visible by clicking the row)
   * A description of what you expected vs. what you see

We'll investigate within 24 hours.

## Privacy

Your transaction history is **private** — only you can see it. Hosts of Contests you join can see *that* you joined and paid the fee, but they don't see your wallet balance or other transactions. Same with donations: the donation amount and username are public on the Contest page, but the donor's full balance and history are not.


---

# 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.rivalryze.com/gems-and-wallet/transaction-history.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.