> For the complete documentation index, see [llms.txt](https://docs.tensor.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensor.trade/trade/troubleshooting/weird-phantom-transactions.md).
# Weird Phantom Transactions
A common question we get is: "hey, I'm not using Tensor, don't have any pools or listings setup, but I see these negative value transctions in my wallet by your app - what are they?"
The answer is - those are **royalty payments**.
The **large green** numbers are royalties paid to you by Tensor. The **small negative gray** numbers are fees paid BY THE SENDER of Royalties to make those transactions happen.
Unfortunately Phantom INCORRECTLY CLASSIFIES those fees as if they were paid by your wallet, when in actuality they haven't.
In other words, it's a UI bug. You haven't paid a cent of your own money.
{% hint style="success" %}
The small negative numbers are INCORRECTLY displayed by Phantom as if you paid them - when actually the SENDER of royalties paid them. It's a UI bug.
{% endhint %}
As a proof, click into one of these transactions, open it on Solscan and check who actually paid the fee. You'll see it wasn't your wallet.
We're chatting to team Phantom to get this fixed 🫡
---
# 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.tensor.trade/trade/troubleshooting/weird-phantom-transactions.md?ask=&goal=
```
`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.