> For the complete documentation index, see [llms.txt](https://docs.recyv.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.recyv.xyz/using-recyv/tracking.md). # Tracking payments ## Requests The Requests tab lists what you have created, with a status against each. **Pending** — created, not yet paid. **Paid** — a matching payment has been found. **Expired** — past its 30-day window. The link still works. ## How Paid is determined Two ways. Token payments are matched by scanning transfer events to your address for the right token and amount. Payments made through a Recyv link also report a receipt, which the server verifies against the chain before recording — the browser says *where to look*, never *what happened*, so a fabricated receipt changes nothing. The second path exists because native ETH emits no transfer event and cannot be found by scanning alone. ## Received Every incoming payment across all supported tokens, newest first, with the sender and the date. ## Totals The headline figure is in dollars across all tokens, with the raw amounts listed underneath. Stablecoins are treated as one dollar rather than priced live. Any token with no available price is left out of the total and the app says so, rather than counting it as zero. ## A limitation worth knowing Your list of requests is stored in the browser that created them. Create a request on a laptop and it will not appear on your phone. This affects the list only — the links themselves work anywhere, for anyone, forever. --- # 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.recyv.xyz/using-recyv/tracking.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.