> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/vault/sign-a-transaction/stellar.md).
# Stellar review screen
Memo, trustlines and account reserve.
{% stepper %}
{% step %}
### The transaction
**Stellar operation** lists each operation (payment, path payment, …), the **Fees**, the recipient and the amount. *Transaction with fees paid by someone else* means a fee-bump: the sponsor is shown.
A Stellar payment decoded on the Vault.
{% endstep %}
{% step %}
### Memo
The **Memo** is a short tag attached to the payment. *Exchanges usually require it; a deposit sent without the right memo is often lost.* Compare it letter by letter with what the exchange gave you.
The memo field.
{% endstep %}
{% step %}
### Trustlines and reserve
To hold an asset other than XLM, your account first **accepts the asset** (a trustline). The Vault shows **Accept the asset** or **Stop accepting the asset**, and reminds you that each open line **locks 0.5 XLM** of your balance as a reserve.
A non-XLM asset payment: the asset code and its issuer are shown in full.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**An operation the Vault does not decode** is listed as *Operation type not decoded on this device* on a **grey** strip. An **account merge** stays red with its checkbox.
{% endhint %}
{% hint style="warning" %}
**HANDS OVER THE WHOLE ACCOUNT** is an *account merge*: it empties your account into another one and closes it. Refuse unless you are doing exactly that on purpose. Also refuse anything that says *This looks like a sign-in but it is a real transaction*.
{% endhint %}
## Learn more
* [Send Stellar from the extension](/browser-extension/send/stellar.md)
---
# 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://doc.lockerprotocol.com/vault/sign-a-transaction/stellar.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.
