> For the complete documentation index, see [llms.txt](https://docs.ur.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ur.app/design/user-experience/introduction.md). # Introduction What UR provides, and what it is not. This guide helps you integrate UR's account in a way that accurately represents the product and creates the best experience for your users. UR provides a real financial account: a Swiss IBAN account that holds and moves stablecoins and fiat as one, not just a wallet. The multi-currency card is a valuable spending tool that complements the account; it is not the primary product. Following these guidelines helps your users understand the full value of the account and sets the right expectations from the start. ### What UR provides UR offers a real financial account that lets your users: * Hold and manage multi-currency balances * Receive funds via incoming transfer to their Swiss IBAN * Send funds to external accounts * Convert digital assets to fiat (off-ramp) * Convert fiat to digital assets (on-ramp) * Spend their balance using a multi-currency card The account is the foundation. The card is a convenient way to access and spend the funds held in that account. ### What UR is not UR is not primarily a card product or a payment card service. The multi-currency card is a valuable feature, but position it as one of several ways your users can use their account, not as the main offering. --- # 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.ur.app/design/user-experience/introduction.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.