<!-- tempo-docs-context -->
> Source: [/docs/guide/private-zones/deposit-to-a-zone](https://tempo.com/developers/docs/guide/private-zones/deposit-to-a-zone.md)
> Section: [Zones](https://tempo.com/developers/docs/zones.md). Connect to a Zone and work with private balances, deposits, and withdrawals. Zones is live on Mainnet; see the introduction to set up a Zone. Earlier testnet sandbox guides describe a separate integration.
> Earlier testnet sandbox: use [Zones](https://tempo.com/developers/docs/zones.md) for current Mainnet deployments.
> [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.

<a id="deposit-pathusd-to-a-tempo-zone-on-testnet" />

# Deposit OUSD

Move `OUSD` test tokens from public Tempo into a private balance on Zone A.

## Overview

This guide deposits `OUSD` test tokens from public Tempo into **Zone A**. It uses the [testnet sandbox](https://tempo.com/developers/docs/guide/private-zones#testnet-compatibility), which differs from current deployments. You submit a deposit on Tempo, then wait for the Zone to credit the net amount after fees.

A public account signs a plaintext or encrypted deposit, the Zone A portal locks OUSD, and Zone A later imports the deposit and credits the private balance.

The portal (`ZonePortal`) on Tempo accepts the deposit. Reading the resulting balance needs an [authorization token](https://tempo.com/developers/docs/zones/connect#authorize-access), which scopes Zone RPC reads to your account.

<a id="depositing-pathusd-to-zone-a" />

<span id="depositing-ousd-to-zone-a" />

## Deposit OUSD to Zone A

**Interactive demo: Deposit to Zone A**

1. Deposit to zone

## Code Examples

These snippets assume a signed-in `rootClient` on Tempo and the usual token and Zone constants in scope.

Use the plaintext flow when revealing the recipient and memo is acceptable. Use the encrypted flow to hide those fields from public observers on Tempo.

### Plaintext

```ts
import { parseUnits } from 'viem'

const depositAmount = parseUnits('100', 6)

const { receipt } = await rootClient.zone.depositSync({
  account: rootClient.account,
  amount: depositAmount,
  token: ousd,
  zoneId: ZONE_A.id,
})

console.log(receipt.blockNumber)
```

### Encrypted

```ts
import { parseUnits } from 'viem'

const depositAmount = parseUnits('100', 6)

const { receipt } = await rootClient.zone.encryptedDepositSync({ // [!code focus]
  account: rootClient.account,
  amount: depositAmount,
  token: ousd,
  zoneId: ZONE_A.id,
})

console.log(receipt.blockNumber)
```

<span id="what-happens-during-a-deposit" />

## Deposit Settlement

A deposit settles in two phases. The Tempo receipt confirms that the portal accepted the deposit. The Zone balance changes later, when the Zone sequencer [imports the deposit](https://tempo.com/developers/docs/protocol/zones/bridging#deposits).

The Zone mints `amount - depositFee`, not the full amount you passed to `deposit(...)`. The portal deducts the [deposit fee](https://tempo.com/developers/docs/protocol/zones/execution#deposit-fees) in the deposited token. To land a specific net amount in the Zone, add the deposit fee first.

## Related

[Deposit Into a Zone](https://tempo.com/developers/docs/zones/deposit): Use for depositing into a current Zone deployment.

[Send Within a Zone](https://tempo.com/developers/docs/guide/private-zones/send-tokens-within-a-zone): Use for a private transfer between accounts in Zone A.

[Withdraw OUSD](https://tempo.com/developers/docs/guide/private-zones/withdraw-from-a-zone): Use for moving OUSD from Zone A back to your public balance.

[Testnet Sandbox](https://tempo.com/developers/docs/guide/private-zones): Covers the sandbox Zones, router deployment, and compatibility limits.
