security

You sign.TetraFi never can.

TetraFi plugs into the custody you already run. Trade from MPC vaults and self-custody wallets side by side, under your own approvals and policies.

01Nothing is sent firstYour side locks in an on-chain escrow and releases only when delivery is proven on the other chain.
02No custody keyTrade from MPC vaults or self-custody wallets. TetraFi never holds a key.
03No client fundsTetraFi Ltd provides the settlement infrastructure and holds no client funds.
04Checked before any deskNine mandatory checks run on every request, before any desk sees it.
05Your own contractsEach institution runs its own deployment: immutable contracts, no upgrade key, governed inside its own regulatory perimeter. TetraFi is infrastructure, not a counterparty.
01 custody and wallets

Bring your own wallets
and custody.

TetraFi plugs into the custody you already run. Trade from MPC vaults and self-custody wallets side by side, under your own approvals and policies. TetraFi holds no custody key and no upgrade key.

your workspace approvals whitelists member wallet links settlement network no custody key
custody · you sign, TetraFi never canno custody key · no upgrade key

MPC custody providers

Register vaults from your MPC provider and trade straight from them. Approvals and whitelisted destinations stay under your policy.

FireblocksBitGoMore planned

Self-custody wallets

Connect a wallet directly and sign each trade yourself. Link wallets to named members, so every signature maps to a person.

WalletConnectBrowser walletsSolana wallets

Embedded, and several at once

Give your own users a self-custodial wallet on a page TetraFi hosts, with passkeys if your policy calls for it. Run several vaults and wallets in one workspace and pick the source per trade.

Embedded walletsPasskeysFiat in and out
Integrations screen: embedded wallets, custody, API keys and webhooks
integrations · embedded wallets, custody, api keys, webhooks
02 compliance

Checked before
anyone sees it.

Nine mandatory checks run on every request. A request that fails never reaches a desk, and every blocked attempt keeps its full per-check evidence.

  1. 01Risk labels
  2. 02Originatorsanctions
  3. 03Beneficiarysanctions
  4. 04Deposit walletscreening
  5. 05Jurisdictioncorridor policy
  6. 06Corridorvolume caps
  7. 07Travel ruleFATF R16
  8. 08Workspacerequirements
  9. 09Unhosted walletEDD · EU TFR
  • A locked floor. The nine checks are the platform floor on every workspace, and they run before any desk sees the request.
  • Your workflows on top. Velocity limits, structuring detection and review holds, rolled out from draft to shadow to active. An EU MiCA CASP template to start from.
  • Onboard once. One KYB and one policy cover every counterparty on the network.
  • Evidence kept. The compliance snapshot is frozen at execution and sealed into the trade's own record.

In the docs: where each check runs →

Compliance gate health: checks run, pass rate, blocked orders and where the gate catches
compliance · gate health
Compliance workflows with the nine-check platform floor
compliance · platform floor and workflows
03 identity and access

Every signature
maps to a person.

Members, roles, groups, service accounts and API keys in one place, with approvals and whitelisted destinations under your own policy.

  • Named signers. Link wallets to named members, so every signature maps to a person.
  • Scoped keys. Workspace API keys are minted against service accounts with explicit scopes.
  • Your approvals. Approvals and whitelisted destinations stay under your policy.
Identity and access: members, custom roles, groups, service accounts, API keys and MFA policy
identity and access · members, roles, service accounts, api keys
next · 05 Solutions Every side of the flow. One network.
book a demo

Stop sending first.

See a trade requested, cleared, priced and settled in one flow, on your own corridors.

Book a demo → How a trade settles →