> For the complete documentation index, see [llms.txt](https://pocketpay.gitbook.io/pocketpay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pocketpay.gitbook.io/pocketpay/white-paper/products-and-services/use-cases.md). # Use Cases For merchants, PocketPay offers a comprehensive solution that not only processes payments but also manages the business side of operations. From small online shops to large retail chains, our platform supports businesses of all sizes in streamlining their payment processes and gaining valuable insights into their operations. Consumers benefit from the simplicity, security, and flexibility of using PocketPay. Whether making purchases online or in-store, users enjoy a smooth payment experience across multiple currencies and platforms. With third-party integrations, consumers can also access PocketPay's functionalities within their favourite apps and DA\apps, ensuring a seamless transaction experience wherever they go. In conclusion, PocketPay's products and services are designed to address the specific needs of today's digital economy, offering a secure, efficient, and user-friendly payment solution for merchants and consumers alike. Through innovation and integration, PocketPay is set to transform the way payments are processed and managed globally. --- # 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://pocketpay.gitbook.io/pocketpay/white-paper/products-and-services/use-cases.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.