# Pesa

> Peer-to-peer fiat and stablecoin settlement, with payments proven on the user's phone.

- [What is Pesa?](https://docs.pesapay.xyz/index.md): Pesa lets people buy and sell digital dollars with local payment apps, peer to peer, with every payment proven on the user's phone.
- [How Pesa works](https://docs.pesapay.xyz/how-it-works.md): One trade from start to finish: lock, pay, prove, release.
- [Developer quickstart](https://docs.pesapay.xyz/quickstart.md): Move USDC from an EVM chain into a Stellar wallet in about 30 lines.
- [Buy USDC](https://docs.pesapay.xyz/using-pesa/buy.md): Pay a seller with your payment app and receive USDC in your own wallet.
- [Sell USDC](https://docs.pesapay.xyz/using-pesa/sell.md): Lock your USDC, get paid in local money, and release only when the payment is proven.
- [Provide liquidity](https://docs.pesapay.xyz/using-pesa/provide-liquidity.md): Run an offer: deposit USDC, set your rates, and get paid in local money.
- [Protocol overview](https://docs.pesapay.xyz/protocol/overview.md): Three Soroban contracts settle every Pesa trade on Stellar.
- [Escrow](https://docs.pesapay.xyz/protocol/escrow.md): Holds depositors' USDC and their rail terms, and pays out only through the orchestrator.
- [Orchestrator](https://docs.pesapay.xyz/protocol/orchestrator.md): Opens, fulfils, cancels and expires orders, and is the only contract the escrow obeys.
- [Claims contract](https://docs.pesapay.xyz/protocol/claims-contract.md): Checks zkTLS claims on-chain and keeps the set of spent payment nullifiers.
- [Order lifecycle](https://docs.pesapay.xyz/protocol/order-lifecycle.md): Order states, time windows, and the buy and sell flows.
- [Fees and limits](https://docs.pesapay.xyz/protocol/fees-and-limits.md): What a trade or a transfer costs, and how much can move.
- [Chain abstraction](https://docs.pesapay.xyz/chain-abstraction/overview.md): Every chain is a spoke. Stellar is the only place balances, escrow and trades live.
- [Supported routes](https://docs.pesapay.xyz/chain-abstraction/routes.md): Which assets can move in and out, from which chains, and who signs.
- [USDC through CCTP](https://docs.pesapay.xyz/chain-abstraction/cctp.md): How a USDC burn on an EVM chain becomes native USDC in a Stellar wallet, and back.
- [USDT through USDT0](https://docs.pesapay.xyz/chain-abstraction/usdt0.md): USDT moves over LayerZero as USDT0, then converts to USDC on the Stellar DEX.
- [Transfer lifecycle](https://docs.pesapay.xyz/chain-abstraction/transfer-lifecycle.md): Each transfer's stage path, and the SEP-24 status your app should show.
- [Failure handling](https://docs.pesapay.xyz/chain-abstraction/failure-handling.md): What the transfers service does when a chain, a provider or a user does something unexpected.
- [zkTLS verification](https://docs.pesapay.xyz/zktls/overview.md): Prove a fact from a user's own HTTPS account, from their phone, without the account data leaving it.
- [Architecture](https://docs.pesapay.xyz/zktls/architecture.md): Split TLS capture across two enclaves, a native VOLE proof on the phone, and an attested verifier.
- [Profiles and policies](https://docs.pesapay.xyz/zktls/profiles-and-policies.md): A site is described by a profile, a rule by a policy. Adding a rail adds two files and no code.
- [Claims](https://docs.pesapay.xyz/zktls/claims.md): The platform's only output: a signed statement that a policy held for the user's account.
- [Trust bundle](https://docs.pesapay.xyz/zktls/trust-bundle.md): The signed list of every enclave and verifier key a consumer may trust.
- [Payment rails](https://docs.pesapay.xyz/zktls/payment-rails.md): How a Wise transfer becomes a claim that can settle exactly one Pesa order.
- [Trust model](https://docs.pesapay.xyz/security/trust-model.md): What each party can and cannot do, and what you trust when you use Pesa.
- [Settlement invariants](https://docs.pesapay.xyz/security/invariants.md): The rules every fund path must keep. Each change to a fund path names the invariant it preserves.
- [Risks](https://docs.pesapay.xyz/security/risks.md): Known risks for users, liquidity providers and integrators, and how each is bounded.
- [Developer overview](https://docs.pesapay.xyz/developers/overview.md): What you can build on Pesa, and which piece to use.
- [Authentication](https://docs.pesapay.xyz/developers/authentication.md): Prove which Stellar account your user owns. Every transfer belongs to that account.
- [Install the Pesa SDK](https://docs.pesapay.xyz/sdk/installation.md): A thin TypeScript client for the transfers API, the chain registry, and the verifiers that check every action before a wallet prompt.
- [Client reference](https://docs.pesapay.xyz/sdk/client-reference.md): Every method of the transfers client, with its types.
- [Verifiers](https://docs.pesapay.xyz/sdk/verifiers.md): Check every action against what the user picked, before the wallet prompt.
- [Deposit into Stellar](https://docs.pesapay.xyz/guides/deposit.md): Bring USDC or USDT from an EVM chain into the user's own Stellar wallet.
- [Withdraw from Stellar](https://docs.pesapay.xyz/guides/withdraw.md): Send USDC from the user's Stellar wallet to USDC or USDT on an EVM chain.
- [Send on Stellar](https://docs.pesapay.xyz/guides/send.md): Pay USDC from the user's wallet to another Stellar address, with no XLM needed.
- [React Native with Privy](https://docs.pesapay.xyz/guides/react-native.md): Give each user a Stellar wallet and an EVM deposit address, and run sponsored deposits in an Expo app.
- [Read the order book](https://docs.pesapay.xyz/guides/order-book.md): List LP offers, market depth, provider stats and order status.
- [zkTLS SDK](https://docs.pesapay.xyz/zktls-sdk/overview.md): Prove a fact from a user's own account, such as a completed payment, without the account data leaving their phone.
- [iOS](https://docs.pesapay.xyz/zktls-sdk/ios.md): Install the zkTLS SDK and run a proving session in a UIKit or SwiftUI app.
- [Android](https://docs.pesapay.xyz/zktls-sdk/android.md): Install the zkTLS SDK from Maven Central and run a proving session.
- [Verify claims on your backend](https://docs.pesapay.xyz/zktls-sdk/backend-verification.md): Never trust the phone. Check every claim again on your server, in TypeScript, Go or Rust.
- [Errors](https://docs.pesapay.xyz/zktls-sdk/errors.md): Every SDK error, what to tell the user, and whether they can start again.
- [API reference](https://docs.pesapay.xyz/api-reference/introduction.md): Base URLs, conventions, errors and limits for the Pesa HTTP API.
- [Authentication](https://docs.pesapay.xyz/api-reference/authentication.md): SEP-10 challenge and token endpoints.
- [Routes](https://docs.pesapay.xyz/api-reference/routes.md): List every route with its chains, assets, limits and availability.
- [Quotes](https://docs.pesapay.xyz/api-reference/quotes.md): Price a transfer. A quote is stored on the server and used once.
- [Transfers](https://docs.pesapay.xyz/api-reference/transfers.md): Create a transfer from a quote, get the next action, submit signed results, and track it.
- [Order book](https://docs.pesapay.xyz/api-reference/order-book.md): Public, read-only market data: offers, depth, providers and orders.


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