> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rem.money/llms.txt
> Use this file to discover all available pages before exploring further.

# Settlement Zones

> Private settlement rails for treasury, intercompany, and institutional flows — encrypted, EVM-compatible, bridgeable.

REM designs, deploys, and operates dedicated **Settlement Zones** for institutional clients — private, EVM-compatible chains for the flows that should never hit a public network.

Stablecoin and tokenised-asset settlement stays encrypted, compliance policies travel with the tokens, and external observers see nothing. Built so payroll, treasury, intercompany, and institutional flows settle privately while remaining bridgeable to public rails.

Zones run as a private deployment on **Tempo** (primary), with the same architecture available on other supported networks where institutional requirements demand it.

## Zone structure

<CardGroup cols={3}>
  <Card title="Admission contract" icon="id-card">
    Defines who can transact; anchored to a KYB decision from the operator.
  </Card>

  <Card title="Private state tree" icon="lock">
    Balances and transactions committed as opaque commitments; only Zone participants can resolve.
  </Card>

  <Card title="Bridge" icon="bridge">
    Value enters and leaves through public stablecoin issuance; enforces admission and AML controls.
  </Card>
</CardGroup>

## Three-step flow

<Steps>
  <Step title="Deposit">
    `rem.zone.deposit()` moves funds from the public rail into the Zone. Sender and amount public; recipient and intent stay in Zone.
  </Step>

  <Step title="Transact privately">
    `rem.zone.transfer()` — transfers encrypted; external observers see nothing.
  </Step>

  <Step title="Withdraw">
    `rem.zone.withdraw()` — uses cryptographic commitments; REM cannot block legitimate exits.
  </Step>
</Steps>

## Capabilities

* **Encrypted intra-zone transactions** — opaque to everyone except Zone participants and the operator
* **Non-custodial** — REM can view for compliance but cannot move, freeze, or confiscate
* **EVM-compatible** — existing Solidity, wallets, and tooling work unchanged
* **TIP-403 compliance** — policies defined on the public rail replicate to the Zone automatically
* **Mainnet-interoperable** — withdraw to the public rail anytime; liquidity pools unified
* **Multi-token** — supports any TIP-20 token (stablecoins, tokenised assets) across multiple zones

## Trust model

| REM (Operator) **CAN**                            | REM (Operator) **CANNOT**                                     |
| ------------------------------------------------- | ------------------------------------------------------------- |
| Sequence transactions                             | Move user funds                                               |
| View tx details (operator-level audit visibility) | Freeze or confiscate assets                                   |
| Manage zone liveness                              | Block valid withdrawals (users exit with cryptographic proof) |
| Enforce TIP-403 policies                          | Share tx details outside compliance scope                     |

## Use cases

<CardGroup cols={2}>
  <Card title="Corporate payroll" icon="building-user">
    Pay staff in stablecoins without leaking salaries to the public chain.
  </Card>

  <Card title="Treasury management" icon="vault">
    Move balances between entities and counterparties without revealing positions.
  </Card>

  <Card title="Intercompany B2B settlement" icon="building-columns">
    Settle at scale across subsidiaries, with policy enforcement and unified reporting.
  </Card>

  <Card title="Institutional flows" icon="chart-network">
    Private settlement layer for funds, asset managers, and tokenised-asset issuers where positions and counterparties must stay confidential.
  </Card>
</CardGroup>

## Quickstart

```typescript theme={null}
import { REM } from "@rem-money/sdk";

const rem = new REM({ apiKey: process.env.REM_API_KEY });

await rem.zone.deposit({
  zoneId: "zone_acme_payroll",
  from: "wallet_treasury_mainnet",
  amount: "250000",
  currency: "USDC",
});

await rem.zone.transfer({
  zoneId: "zone_acme_payroll",
  from: "zone_wallet_treasury",
  to: "zone_wallet_employee_4781",
  amount: "8500",
});

await rem.zone.withdraw({
  zoneId: "zone_acme_payroll",
  from: "zone_wallet_employee_4781",
  to: "wallet_employee_4781_mainnet",
  amount: "8500",
});
```

***

## Custom solutions

Settlement Zones are not a self-serve product. Every zone is a designed deployment — REM works with you on admission, governance, bridge integration, and operator tooling.

<CardGroup cols={2}>
  <Card title="Zone design" icon="compass-drafting">
    Topology, participant model, governance, and admission rules tailored to the use case (payroll, treasury, B2B settlement, institutional flows).
  </Card>

  <Card title="Admission contracts" icon="id-card-clip">
    Custom KYB and access logic — including multi-operator setups, tiered participants, and revocation flows.
  </Card>

  <Card title="Bridge integration" icon="link">
    Connect Zone liquidity to your existing treasury, core banking, or other Settlement Zones — including circuit breakers and rate limits.
  </Card>

  <Card title="Operator tooling" icon="gauge">
    Compliance dashboards, supervised viewing, regulator access, sequencer monitoring, and incident playbooks.
  </Card>
</CardGroup>

<Card title="Commission a Zone" icon="envelope" href="mailto:hi@rem.money" horizontal>
  Tell us the participants, the flows, and the regulator. We'll come back with a Zone design and operating proposal.
</Card>