Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Payments on Stable

Stable is built around payments. USDT0 is the native asset and the gas token, so settlement and fees share one balance. Single-slot finality means a transfer clears in under a second. ERC-3009, EIP-7702, and x402 are native primitives, not workarounds — you can settle with a signature, pull from a delegated account, or charge per HTTP request without running a billing stack.

What you can build

  • P2P transfers — native USDT0 sends with 21k gas and sub-second finality.
  • Subscriptions — pull-based recurring billing with EIP-7702 delegation.
  • Invoice settlement — ERC-3009 transferWithAuthorization with deterministic nonces for exact reconciliation.
  • Pay-per-call APIs — x402 middleware for per-request USDT0 payments; no API keys, no sign-ups.
  • Zero-gas UX — application-sponsored transactions via the Gas Waiver service.
  • Cross-chain USDT0 — LayerZero OFT bridging from Ethereum and other networks.

How Stable differs

  • One asset for everything: the sender doesn't hold a separate gas token.
  • Native ERC-3009: USDT0 implements transferWithAuthorization directly, so payments settle with a signature and no approve step.
  • Deterministic finality: a block is final the moment it's committed. No confirmation waits.
  • Native x402: the facilitator pays no gas through the Gas Waiver, so per-request settlement costs stay below a cent.

Start here

Payment primitives

  • ERC-3009 — Transfer With Authorization: the settlement standard behind invoices and x402.
  • x402 (HTTP-native payments) — Server responds 402, client signs ERC-3009, facilitator settles on-chain.

Next recommended