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

# Risks

> Known risks for users, liquidity providers and integrators, and how each is bounded.

| Risk | Who it affects | Bound |
| - | - | - |
| **Frozen USDC.** Circle can freeze an address, including the escrow. | Everyone holding USDC | A freeze is reversible. `withdraw` and `depositor_release` are never blocked by Pesa. |
| **Release to a frozen taker fails.** | Depositor and taker | The order stays open. After `settle_by`, `expire_intent` returns the USDC to the depositor, and the fiat side is settled off-chain. |
| **Payment reversal.** Some providers allow chargebacks after release. | Depositor | Buy proofs accept only balance-funded Wise-to-Wise transfers. Orders are capped at \$20. |
| **Bank payout bounces.** On a sell, a bank payout can be reported as sent and later returned. | User selling | The LP's proof shows the payout was completed by Wise. The \$20 cap bounds the loss. |
| **Griefing.** A taker opens orders and never pays. | Depositor | The lock lasts until `settle_by` only. Per-address quotas apply to retail takers. |
| **Enclave compromise.** | Everyone | Two capture enclaves on two clouds must both fail. Chips, images and keys are pinned in the trust bundle and revocable. Losses are bounded by the order cap. |
| **Funds sent to an unsponsored chain.** | Users of deposit addresses | The app warns before showing the address. Recovery needs the user's own signer. |
| **Bridge and messaging delays.** | Users moving funds | Pesa never burns or sends twice. A late burn still completes. |
| **DEX price on USDT0 swaps.** | USDT users | Swaps use a fresh quote and a minimum output. If the price moves, the user approves a new quote or keeps USDT0. |

## For integrators

* Always run the SDK's verifiers before a wallet prompt. A wrong burn field loses funds permanently.
* Never log a zkTLS `SessionConfig`, a capture handle or a cookie.
* Consume nullifiers on your backend if a fact may be proved once.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.