Papers Non-Custodial by Design

Non-Custodial by Design

How U.CASH settlement works: payment rails that route across 30+ blockchains and settle directly to wallets you control. The network never holds funds or keys.

Updated · canonical source: u.cash/technology

The routing layer, not a custodian

Money moves on-chain, peer to peer. U.CASH is the routing and checkout layer: it prices, addresses, monitors and notifies, and the value itself settles on public chains between the payer and wallets you control.

How settlement works

  • Direct to your wallets: buyers pay into addresses you control, xpubs and per-chain wallets. Funds never pass through a U.CASH custody account.
  • Multi-chain routing: one checkout accepts 30+ blockchains and custom tokens across 23 token networks, 34 networks in all. The customer picks the asset; you get paid.
  • Cards via your processor: fiat card payments run through your own card-processor account. No middleman holds the money.
  • Signed webhooks: every payment event is delivered to your server with a signed webhook so you can fulfill with confidence.
  • Per-coin confirmations: configurable confirmation policies per chain and per coin, so you balance speed against finality.
  • Web3-name payouts: resolve ENS, Unstoppable and FIO names to addresses, so payouts can go to a human-readable name.

Security model

  • No pooled custody: because the network does not hold funds, there is no central honeypot to attack. Each merchant risk is isolated to their own wallets.
  • You keep the keys: wallet keys and card-processor keys stay with you. U.CASH stores only what is needed to route and notify.
  • Signed, replay-safe events: webhooks are signed and guarded against replay, so fulfillment triggers only on verified payments.
  • Open and auditable: REST APIs, SDKs, and transparent fee models. Settlement is verifiable on-chain by anyone.

Open APIs and SDKs

Integrate payments, build invoicing, or put an AI agent on HTTP-402: REST APIs, signed webhooks, and JavaScript and Python SDKs, plus an MCP server for agent tooling. The reference documentation starts at docs.u.cash.

This paper condenses a canonical source. When details drift, the upstream wins: u.cash/technology.