<!-- tempo-docs-context -->
> Source: [/docs/guide/ousd](https://tempo.com/developers/docs/guide/ousd.md)
> Section: [Partners](https://tempo.com/developers/docs/partners.md). Find wallet providers, bridges, RPC infrastructure, data services, and other third-party integrations.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.com/developers/llms.txt) and Markdown pages directly.

# OUSD on Tempo

Open USD (OUSD) is a USD stablecoin operated by [Open Standard](https://joinopenstandard.com), an independent company whose founding partners include Coinbase, Mastercard, Shopify, Stripe, and Visa. OUSD is issued natively on Tempo as a [TIP-20 token](https://tempo.com/developers/get-started/stablecoins) and is the recommended stablecoin for holding balances, accepting payments, and settling on Tempo.

Open USD (OUSD) logo

## Why OUSD

* **Mint and redeem at par.** Open Standard offers fee-free 1:1 minting and redemption through integration partners, which set access, supported regions, and any charges.
* **Regulated reserves.** Reserves are maintained at major financial institutions in compliance with US regulatory requirements.
* **Native on Tempo.** OUSD is issued directly on Tempo, so it does not depend on a bridge.

## Contract

| Property       | Value                                        |
| -------------- | -------------------------------------------- |
| network        | Tempo Mainnet (chain ID `4217`)              |
| address        | [`0x20c0000000000000000000006a37da5c996874be`](https://explore.tempo.xyz/address/0x20c0000000000000000000006a37da5c996874be) |
| `name()`       | `"OpenUSD"`                                  |
| `symbol()`     | `"OUSD"`                                     |
| `currency()`   | `"USD"`                                      |
| `decimals()`   | `6`                                          |
| `quoteToken()` | [pathUSD](https://tempo.com/developers/docs/protocol/exchange/quote-tokens#pathusd) (`0x20c0000000000000000000000000000000000000`) |

OUSD is also listed in the [Tempo token list](https://tempo.com/developers/docs/quickstart/tokenlist).

## Get OUSD

* **Mint or redeem through an integration partner.** OUSD integration partners mint and redeem OUSD 1:1 with USD. See [joinopenstandard.com](https://joinopenstandard.com) to get started.
* **Swap on the Stablecoin DEX.** Quote a swap into OUSD on the [Stablecoin DEX](https://tempo.com/developers/docs/guide/stablecoin-dex). A route requires available liquidity and compatible transfer policies for the tokens involved.
* **Bridge, then swap.** If you bridge USDC to Tempo, it arrives as USDC.e. Swap it to OUSD on the Stablecoin DEX. See [Fund an account](https://tempo.com/developers/docs/guide/getting-funds).

## How OUSD, pathUSD, and USDC.e fit together

| Token | Role on Tempo | Use it when |
| ----- | ------------- | ----------- |
| **OUSD** | Recommended stablecoin | Holding balances, accepting payments, settling, and paying fees |
| **pathUSD** | Root quote token on the Stablecoin DEX and the protocol's first fallback fee token | Routing between stablecoins. Most users never need to hold it directly. |
| **USDC.e** | USDC bridged from other chains through Stargate | Bringing USDC to Tempo from another chain, before swapping to OUSD |

pathUSD and USDC.e remain fully supported. Existing integrations that use them keep working without changes.

## Move to OUSD from USDC.e or pathUSD

### Balances

Swap USDC.e or pathUSD to OUSD on the [Stablecoin DEX](https://tempo.com/developers/docs/guide/stablecoin-dex). The DEX routes USD stablecoins through pathUSD, so a swap from USDC.e to OUSD happens in a single transaction.

### Fees

Set OUSD as your fee token to choose it ahead of pathUSD. Call `setUserToken` on the FeeManager once to set the account's preference. Alternatively, set `fee_token` on an individual [Tempo transaction](https://tempo.com/developers/docs/protocol/transactions/spec-tempo-transaction).

The [protocol fallback](https://tempo.com/developers/docs/protocol/fees/spec-fee#ordered-fallback-from-t13) tries pathUSD, then OUSD. This applies only when no explicit fee token, stored preference, or transfer/swap inference determines the fee token. OUSD is tried when the fee payer's pathUSD balance cannot cover the maximum fee. OUSD must cover the entire maximum fee; balances are not combined.

Integrations that explicitly select pathUSD still need updating for users who hold only OUSD. Select OUSD, or remove the pathUSD override to let the [fee token order](https://tempo.com/developers/docs/protocol/fees/spec-fee#fee-token-preferences) apply.

### Accepting payments

If your application accepts USDC.e or pathUSD and settles in OUSD, use a [Stablecoin DEX swap](https://tempo.com/developers/docs/guide/stablecoin-dex/executing-swaps) to convert the received funds. Quote the swap and verify its output amount. Choosing OUSD as the fee token pays transaction fees in OUSD; it does not convert the payment amount.

### Token selectors and allowlists

Add OUSD from the [token list](https://tempo.com/developers/docs/quickstart/tokenlist) and show it as the default USD stablecoin. Keep USDC.e and pathUSD available for users who already hold them.

### Bridging

USDC bridged through LayerZero (Stargate) still arrives as USDC.e. See [Bridge via LayerZero](https://tempo.com/developers/docs/guide/bridge-layerzero) for how USDC.e works, then swap to OUSD after it arrives.

## Testnet

OUSD is also deployed on Tempo Testnet (Moderato, chain ID `42431`) at the same address. Testnet OUSD is a test token and has no relationship to OUSD on Tempo Mainnet. Use the [faucet](https://tempo.com/developers/docs/quickstart/faucet) to request test tokens, then check the funded balance.
