> For the complete documentation index, see [llms.txt](https://stellar-developer-tools.gitbook.io/anchortrace-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellar-developer-tools.gitbook.io/anchortrace-sdk/reference/limitations.md).

# Limitations

* Classic direct `payment` operations only. SEP-24 tells anchors to also listen for path payments; v1 reports them `unsupported` so a human decides.
* The external leg (bank, cash, mobile money, crypto rail) is never observed. `matched` and `completed` say nothing about it.
* Evidence is what you supply or what one Horizon returned at one time. No cryptographic ledger verification; one Horizon instance is trusted for a live read.
* Absence cannot be proven: terminal failure statuses without evidence are `insufficient_evidence`, not "confirmed no payment". The tool reads transactions by hash; it does not scan an account's history.
* The SEP-24 record does not state the on-chain asset when `amount_in_asset`/`amount_out_asset` are omitted; you must pass `--asset`. Cross-asset (converted) amounts are not checked.
* The fee policy is an explicit interpretation, not something SEP-24 stores. Pick the one that matches the anchor; a wrong choice shows up as an amount mismatch, not silently.
* Redaction scans free text for addresses, emails and known memos only. Review exports before sharing.
* The shipped SEP-24 records are synthetic. No anchor, wallet or support team has used this tool; there is no adoption evidence.
* No Soroban/SEP-41 token transfers, liquidity pools, offers, SEP-6/31.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stellar-developer-tools.gitbook.io/anchortrace-sdk/reference/limitations.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 `automate deployments from our CI pipeline` 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.