> For the complete documentation index, see [llms.txt](https://docs.deso.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deso.org/deso-backend/configuration/selling-usddeso/wyre-buy-with-usd.md). # Wyre - Buy with USD Description of flags related to selling DESO for BTC with Wyre on your Node Note: You will need to work with [Wyre](https://www.sendwyre.com/) in order to set up an integration. Wyre will take credit card payment from your users and in exchange send you BTC to the address specified at [Buy with BTC](/deso-backend/configuration/selling-usddeso/buy-with-btc.md#buy-deso-btc-address) ## Wyre URL `--wyre-url` Type: String Default: None Wyre API URL. For production purposes, this should be . For testing purposes, this should be [https://api.testwyre.com](< https://api.testwyre.com>) ## Wyre Account ID `--wyre-account-id` Type: String Default: None Wyre account ID ## Wyre API Key `--wyre-api-key` Type: String Default: None API Key for Wyre account ## Wyre Secret Key `--wyre-secret-key` Type: String Default: None Secret key for Wyre account --- # 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://docs.deso.org/deso-backend/configuration/selling-usddeso/wyre-buy-with-usd.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.