> 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/how-it-works/security.md). # Security ## Custody Recyv never holds funds. There is no balance, no pooled account, and no contract of ours that money passes through. A payment is one transaction between two wallets. This also means there is no refund button. A confirmed payment is final, in the same way a cash payment is. ## The token is fixed to the link When you create a request you choose the token, and that choice is carried by the link. A request for 500 USDG cannot be settled in 500 units of something worthless. Without this, anyone could pay an invoice in a token they minted themselves and the interface would render it as a completed payment. ## Contracts are read, not trusted The symbol and decimals shown on a payment page come from the contract itself, never from the link or the registry. Two things follow: A link claiming to be USDG that points at a contract reporting a different symbol is refused, with an explanation. A token that is not in Recyv's list is not blocked outright, but it is labelled unverified and the payer must acknowledge it before the button works. Anyone can deploy a token using a familiar name. ## Wrong network Payments are pinned to Robinhood Chain. If a wallet is on another network the pay button is replaced by a switch prompt, and the transaction cannot be broadcast elsewhere even if the interface were bypassed. ## What you should still check The recipient address, before you pay. Recyv can verify that a contract is what it claims to be. It cannot tell you whether the person who sent you a link is who they say they are. --- # 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/how-it-works/security.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.