<!-- tempo-docs-context -->
> Source: [/docs/guide/private-zones/send-tokens-across-zones](https://tempo.com/developers/docs/guide/private-zones/send-tokens-across-zones.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.

# Send Across Zones

Send `OUSD` test tokens from Zone A to Zone B through Tempo.

## Overview

A cross-Zone send moves `OUSD` test tokens from **Zone A** to **Zone B**. It uses the [testnet sandbox](https://tempo.com/developers/docs/guide/private-zones#testnet-compatibility), which differs from current deployments. The transfer settles on Tempo before Zone B credits the balance.

The flow uses the sandbox's [SwapAndDepositRouter deployment](https://tempo.com/developers/docs/guide/private-zones#sandbox-router-deployment) on Tempo in same-token mode. It withdraws from `Zone A` and skips the swap, since the asset stays `OUSD`. Then it deposits that `OUSD` into `Zone B`.

Zone A withdraws OUSD to a public router, which skips the swap and deposits OUSD into the Zone B portal. Zone B imports the deposit and credits its private balance later.

<a id="sending-pathusd-from-zone-a-into-zone-b" />

<span id="sending-ousd-from-zone-a-into-zone-b" />

## Send OUSD to Zone B

**Interactive demo: Send tokens across zones**

1. Send tokens across zones

## Code Example

This snippet assumes a signed-in `rootClient` on Tempo and a `zoneAClient`. It also assumes the shared token and portal constants used throughout the Zone guides. The router address and callback encoding are specific to Moderato's Zone A and Zone B sandbox.

This code covers the routed send submission. Use the demo to watch the routed deposit settle into Zone B.

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

const swapAndDepositRouter = '0xf9b794e0dca9bc12ac90067df792d7aad33436e4' as const
const transferAmount = parseUnits('25', 6)

await zoneAClient.zone.signAuthorizationToken({ zoneId: 6 })

const callbackData = encodeAbiParameters(
  [
    { type: 'bool' },
    { type: 'address' },
    { type: 'address' },
    { type: 'address' },
    { type: 'bytes32' },
    { type: 'uint128' },
  ],
  [false, ousd, ZONE_B.portalAddress, rootClient.account.address, zeroBytes32, 0n],
)

const { receipt } = await zoneAClient.zone.requestWithdrawalSync({
  account: rootClient.account,
  amount: transferAmount,
  data: callbackData,
  feeToken: ousd,
  fallbackRecipient: rootClient.account.address,
  gas: routerCallbackGasLimit,
  to: swapAndDepositRouter,
  token: ousd,
})

// This receipt confirms source submission. Verify L1 processing and destination credit next.
console.log(receipt.blockNumber)
```

<span id="what-this-routed-send-does" />

## Routed Send Settlement

The token leaves `Zone A`, briefly lands on Tempo, and arrives in `Zone B` as the same asset. The routed send:

1. Withdraws `OUSD` from `Zone A` through the outbox (`ZoneOutbox`).
2. Routes that withdrawal to `swapAndDepositRouter` on Tempo.
3. Skips the DEX swap because the input and output token are both `OUSD`.
4. Deposits the routed `OUSD` into `Zone B` through its portal (`ZonePortal`).

The target deposit pays the normal [deposit fee](https://tempo.com/developers/docs/protocol/zones/execution#deposit-fees). `Zone B` receives the routed `OUSD` minus that fee.

The transfer completes when the destination Zone credits the recipient. Follow the [routed-result checks](https://tempo.com/developers/docs/guide/private-zones#check-the-full-routed-result) to confirm destination credit.

:::warning
If the routed withdrawal fails on Tempo, the amount [bounces back](https://tempo.com/developers/docs/protocol/zones/bridging#withdrawal-failure-and-bounce-back) to the withdrawal's `fallbackRecipient` inside `Zone A`. Failures include a reverting callback or a target deposit that can't complete. The sequencer still collects the fee.
:::

## Related

[Swap Across Zones](https://tempo.com/developers/docs/guide/private-zones/swap-across-zones): Use for trading OUSD in Zone A for betaUSD in Zone B.

[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 From a Zone](https://tempo.com/developers/docs/zones/withdraw): Use for withdrawals and contract callbacks on a current Zone deployment.

[Testnet Sandbox](https://tempo.com/developers/docs/guide/private-zones): Covers the sandbox router deployment and the routed-result checks.
