> 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/welcome/what-is-ur.md).

# What is UR?

UR is the financial infrastructure for the open economy. The UR Platform is the account layer that wallets, developers, and financial platforms build on.

A wallet stores value. An account lets you live financially.

UR is the financial infrastructure for the open economy: manage and move stablecoins and fiat from a single account. The infrastructure to turn on-chain value into a real financial life (identity, compliance, fiat rails, card, multi-currency) does not exist inside wallets. Building it yourself means banking licenses, card issuing partnerships, and years of compliance work.

The UR Platform is the account layer. It gives wallets, developers, and financial platforms the ability to offer real accounts through one integration, without building the infrastructure themselves.

## What your users get

When you integrate UR, your users receive:

* **Swiss IBAN**: a personal Swiss IBAN account in their name
* **On-chain identity (**[**URID**](/concepts/urid.md)**)**: a verified, portable identity issued to every user or business that has been KYCed or KYBed respectively
* [**Tokenized deposit**](/concepts/tokenized-deposits.md) **currencies**: EUR, USD, CHF, CNH, SGD, JPY, HKD, each backed 1:1 by fiat reserves
* **Mastercard debit card**: co-branded with your platform
* **Global bank transfers**: SEPA Instant (EUR), SWIFT (multi-currency)
* **Crypto off-ramp**: convert USDC, USDT, USDe, or ETH to fiat
* **FX conversion**: atomic burn-and-mint between currencies

## The stack

The account layer is built in four layers, each on top of the last:

| Layer        | Traditional finance                     | UR: the account layer                                                                                 |
| ------------ | --------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Identity** | KYC/KYB paperwork                       | URID, an on-chain identity issued after verification. Portable, programmable, and verifiable.         |
| **Money**    | Fiat held in bank accounts              | Tokenized deposits on-chain, each unit backed 1:1 by real deposits. Seven currencies, all composable. |
| **Rules**    | Compliance enforced by operations teams | Smart contracts. Core banking is code, not process.                                                   |
| **Data**     | Records in siloed databases             | Core banking and settlement is done on-chain. Transaction records are verifiable publicly.            |

## Core concepts

* [URID](/concepts/urid.md): the on-chain identity that unlocks UR accounts
* [Tokenized deposits](/concepts/tokenized-deposits.md): 1:1 fiat-backed tokens on Mantle Network
* [UR Account](/concepts/ur-account.md): a Swiss IBAN account issued by UR's regulated entity, connected to a URID
* [On-chain ledger](/concepts/on-chain-ledger.md): every transaction recorded on Mantle Network

## Platforms

* Web app: [get.ur.app](https://get.ur.app)
* [iOS App Store](https://apps.apple.com/app/ur-fiat-crypto-unified/id6748420070)
* [Google Play](https://play.google.com/store/apps/details?id=com.mantle.ur)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ur.app/welcome/what-is-ur.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.