> 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/project/roadmap.md). # Roadmap Everything below the first section is intent, not commitment. There are no dates, and nothing here should be read as a promise. ## Shipped Payment links with short URLs and QR codes. Multiple tokens, with the token fixed to the link. Amounts in tokens or in dollars. On-chain verification of every token before payment. Wrong-network detection with one-tap network adding. Payment tracking with verified receipts. Dollar totals across tokens. Live on Robinhood Chain mainnet. ## Being considered next **Requests that follow you between devices.** Today the list of requests you have created lives in the browser that made them. The links work everywhere; the list does not. **Sender identity.** A display name and handle carried by the link, so a payer sees who is asking rather than a hex address. **Payment history for native ETH.** ETH payments settle correctly but do not appear in the received feed, because there is no transfer event to scan for. This needs an indexer. ## Further out Invoices and receipts as documents. Recurring requests and subscriptions. Splitting a payment between several recipients. An API for merchants who want to generate links programmatically. ## Not planned Custody of user funds. Holding balances, offering withdrawals, or standing between a payer and a payee in any way. This is the one thing that will not change, because it is what makes the rest simple. --- # 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/project/roadmap.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.