> For the complete documentation index, see [llms.txt](https://help.xaman.app/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.xaman.app/app/getting-started-with-xaman/buying-xrp/banxa.md). # Banxa All about the Banxa serivce {% hint style="info" %} This article is currently under construction {% endhint %} ### What is Banxa? Banxa is a financial technology platform that provides On/Off ramp solutions for XRP. Banxa is not a bank / authorised deposit taking institution. Crypto Assets are not FDIC-insured products. ### What kind of partnership does Banxa have with Xumm? We have partnered with Banxa (among others) in order to provide On/Off-ramp services to our user around the world. ### Where are they located? Banxa has offices in: **Global Internet Ventures Pty Ltd**\ Level 2, 2/6 Gwynne Street\ Cremorne, Victoria 3121\ Australia **BNXA USA MTL Inc.** (NMLS ID: 2347615)\ 1 East Liberty Street\ Suite 600, Office 16\ Reno NV 89501\ United States of America **EU Internet Ventures B.V.**\ Piet Heinkade 95b, 1019GM\ Amsterdam\ The Netherlands Au ### How do I use their services via Xumm? ### How do I contact Banxa if I have questions about their services? Banxa can be reached via their site at: {% embed url="" %} ### --- # 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://help.xaman.app/app/getting-started-with-xaman/buying-xrp/banxa.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.