> For the complete documentation index, see [llms.txt](https://guides.privatesolution.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.privatesolution.org/hardware/payment-methods.md). # Payment Methods How you pay, and how your order starts. ## Hardware orders 1. Open a ticket on Discord and tell us what you want to buy. 2. We confirm it fits your setup. 3. You pay and we ship. ## Plan orders (XMA, RDMA, firmware) 1. Pick your plan on [privatesolution.org](https://privatesolution.org). 2. Pay at checkout or open a ticket and we will help you pick. ## Accepted payment methods * **Card** — Visa, Mastercard * **Crypto** — BTC, ETH, LTC and more * **Other** — ask in your ticket; we accept more options than we list publicly {% hint style="info" %} Ask in the ticket if you want to pay a way you do not see listed. There is almost always an option. {% endhint %} ## Refunds and problems If something does not work and we cannot fix it in your ticket, we make it right. Talk to us before opening a dispute — setup problems are almost always fixable in a few minutes. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guides.privatesolution.org/hardware/payment-methods.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.