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

# Lending, Receivables, Trade Finance...

> Netting is a primitive, not a venue - point it at whatever book you already settle, and settle less of it.

The clearing engine is **domain-blind**: it clears who owes whom and by when, so a new kind of obligation enters through an intake lane with no engine changes.

Netting is not a venue you bring flow to, and it is not waiting on TetraFi to reach critical mass: it is **adoptable by operators who run none of TetraFi's other rails** - our own are simply the first book pointed at it. And it is privacy-preserving by construction: positions are readable only inside a [sealed engine](/netting/privacy-and-control) and you see only your own slice, so a book plugs in without leaking its flow, its counterparties, or its edge to anyone - TetraFi included.

<Note>
  **Coming soon.** [Multilateral Netting](/netting) is in design. The lanes below describe the shape the primitive is built for; third-party policy domains arrive as the network opens, and parameters publish at launch.
</Note>

## What Your Book Gets

Whatever the book - loans, receivables, a payment schedule - the outcome is the same three things:

* **Less to settle.** Obligations between the same participants collapse by **atomic multilateral set-off** to one net residual per party; a day's gross flow stops paying gross tolls, and every book that joins the graph compresses yours further
* **Capital efficiency: less capital clears more debt.** Only the residual needs funding, so the same capital clears a far larger gross book - widest of all in a high-volatility event, when gross settlement demands the most liquidity just as it is scarcest. Until then, hold, don't move: no pre-funding, no margin, no inventory bridged to cover a debt
* **The residual, handled.** Whatever doesn't net takes a priced backstop from the [Shared Collateral Network](/collateral), with an early exit any time before the deadline - so the worst case is what you pay today, and the remainder stops being your problem

## Adopt It On What You Already Run

You configure your participation, not the engine. There is one clearing network - the way there is one Ethereum - and what you own is your slice of it:

* **Your own policy domain** - your counterparty sets, deadline-tier menu, backstop configuration, funding mode, perimeter policy, and visibility slice
* **Your own backend, or ours** - the clearing service is packaged to run on your institution's own infrastructure, or alongside a backend you already operate
* **Your existing settlement, untouched** - set-off sits on top of the rails you run today; what changes is how much has to move at the end of a run, not who moves it

## Who This Is For

<CardGroup cols={2}>
  <Card title="Lending markets" icon="landmark">
    A loan book is a netting set: obligations between the same participants clear on one graph and only the residual moves - and a tokenized asset that can be [redeemed T+0](/collateral/instant-redemption) is one you can list as collateral.
  </Card>

  <Card title="Receivables & trade finance" icon="file-invoice">
    Chains of dated obligations - 30, 60, 90 days out - mostly cancel. Set-off clears the circle by settlement date instead of wiring every leg in it, and the working capital parked against invoices that would have cancelled comes back.
  </Card>

  <Card title="Real-world payment obligations" icon="building-columns">
    Recurring obligations between the same parties settle gross today; on one graph a day's flow nets to one wire instead of a schedule of them.
  </Card>

  <Card title="Equities & tokenized assets" icon="arrow-right-arrow-left">
    Delivery-versus-payment at scale: offsetting legs cancel outright, so only the net position is ever delivered - and never one leg without the other.
  </Card>

  <Card title="Energy & circular debt" icon="bolt">
    Imbalance settlements and circular debt are loops by nature - and a loop is exactly what **atomic multilateral set-off** cancels, with zero money moved.
  </Card>

  <Card title="Where each lane stands" icon="diagram-project" href="/netting/where-it-applies">
    Which lanes ship with the primitive, which are designed, and which are further out.
  </Card>
</CardGroup>

## Adopt What You Need

| Adopt                                                      | What changes                                                                           | What you keep                                            |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| **[Multilateral Netting](/netting)** (coming soon)         | your own book clears by **atomic multilateral set-off**; only the net residual settles | your settlement rails, your counterparties, your backend |
| **[Shared Collateral Network](/collateral)** (coming soon) | the residual gets a backstop, and an early exit any time before the deadline           | your capital - nothing locked, nothing pre-funded        |
| **Firm liquidity** (live)                                  | TetraFi's rails become one more obligation source feeding your graph                   | everything above, unchanged                              |

## Get Started

Have a book that settles gross today? [Start the conversation](/support) - tell us who owes whom, and how often.
