> For the complete documentation index, see [llms.txt](https://docs.evopay.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evopay.me/problem-and-solution.md). # Problem & Solution ## The Problem Current crypto transactions on platforms like Telegram lack native tools, privacy, and accountability. Users rely on screenshots, manual messages, or off-platform wallets, all of which create risk, delays, and disputes. Privacy-focused users resort to expensive mixers, which are complicated and raise regulatory concerns. In parallel, users have no native tools to track spending, plan financial goals, or automate budgeting within their Telegram-based crypto activity. This leaves a major gap in self-custody finance. ## Our Solution EvoPay solves both problems. It offers Telegram-native, private, and fully verifiable crypto payments with no wallet connection, no KYC, and no custody. Payments are recorded both on-chain and in Telegram for full transparency. Alongside this, EvoPay introduces the **Accountant AI Agent**, a smart assistant that helps users: * Track their crypto income and expenses * Set budgeting goals * Receive real-time spending reports * Get AI-powered financial suggestions Together, EvoPay and the Accountant AI Agent create a complete ecosystem for secure, anonymous, and intelligent crypto financial management. --- # 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.evopay.me/problem-and-solution.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.