Cowrie Research

t402-primary-sources-2026-05-03

4 min read

t402 primary-source snapshot

Last reviewed: 2026-05-03 UTC

Project status snapshot

What the official materials say

1) Docs homepage: t402 is framed as an HTTP-native stablecoin payment protocol, not just a wallet SDK

  • URL: https://docs.t402.io/
  • Key takeaways:
    • The homepage calls t402 “the open payment protocol for USDT.”
    • It says developers can enable stablecoin payments across 13 blockchain families with a single HTTP header.
    • The quick-start flow centers HTTP responses like 402 Payment Required, Payment-Required, and Payment-Signature, which signals that the main product is the paid-request protocol itself.
    • The docs navigation emphasizes guides, packages, facilitator APIs, supported chains, and production integrations rather than a single hosted checkout or branded wallet.

2) README: the project is a broad protocol-and-tooling stack

  • URL: https://raw.githubusercontent.com/t402-io/t402/main/README.md
  • Key takeaways:
    • The README says t402 is an open standard for internet-native payments that aims to support all networks and forms of value.
    • It explicitly separates t402 from Tether WDK: t402 is the payment protocol while WDK is the wallet layer.
    • The published package architecture spans core protocol types, framework middleware, client wrappers, chain-specific mechanisms, WDK modules, an A2A transport, React Native tooling, an MCP server, and a CLI.
    • That package breadth strongly suggests t402 should be cataloged as a payment-auth and settlement-control stack rather than a one-off SDK.

3) Multi-chain posture is not incidental; it is central to the pitch

  • URLs:
  • Key takeaways:
    • The docs homepage advertises support across EVM, Solana, TON, TRON, NEAR, Aptos, Tezos, Polkadot, Stacks, Cosmos, Bitcoin, Stellar, and Spark.
    • The README enumerates dedicated mechanism packages for many of those ecosystems and even includes Bitcoin/Lightning support via @t402/btc.
    • This makes t402 look much more like a reusable payment protocol family than a single-chain monetization tool.

4) Facilitator docs: t402 also ships the operational verification-and-settlement layer

  • URLs:
  • Key takeaways:
    • The facilitator API docs say the public facilitator provides payment verification and onchain settlement services.
    • The API surface includes health/readiness endpoints, metrics, supported-network discovery, verify/settle endpoints, key registration, usage dashboards, webhook settings, restrictions, and other operational features.
    • The self-hosted guide documents a production deployment with Redis-backed idempotency, Prometheus/Grafana monitoring, per-chain RPC configuration, rate limiting, Docker deployment, reverse-proxy setup, and wallet-funding requirements.
    • This is one of the strongest clues that t402 is infrastructure in practice, not just a spec document.

5) Agent-payments docs: t402 explicitly targets MCP and autonomous paid access

  • URL: https://docs.t402.io/guides/ai-agent-payments
  • Key takeaways:
    • The AI guide says T402’s MCP server lets agents pay for APIs and services autonomously.
    • It highlights budget controls, multi-chain support, and compatibility with MCP-capable assistants.
    • The same guide extends the pitch into paid APIs and premium content access, reinforcing that t402 is being positioned as a programmable internet-payments layer for both humans and agents.

6) Whitepaper status: there is a canonical protocol whitepaper

  • URLs:
  • Key takeaways:
    • The README directly links a “Whitepaper” badge to https://t402.io/t402-whitepaper.pdf.
    • A local copy of that PDF was saved for the library as t402-whitepaper.pdf.
    • The PDF extraction via generic text tooling was not clean enough to rely on for detailed claims in this pass, but its presence still matters as evidence that the team treats t402 as a protocol-level project with a canonical paper.

Whitepaper / technical-doc status

  • A canonical t402 whitepaper PDF exists and was saved locally as t402-whitepaper.pdf.
  • The most legible current operational sources remain the docs site, facilitator reference, and public monorepo README.

Research notes

  • Best current category for the library: open payment protocol / multi-chain stablecoin payment-auth infrastructure / facilitator-and-agent-payments stack.
  • The key distinction from a simple crypto-payments SDK is that t402 combines protocol semantics, server/client integrations, chain mechanisms, facilitator infrastructure, and agent tooling into one operating layer.
  • The self-hosted facilitator docs materially increase confidence that this is real deployable infrastructure rather than only standards theater.
  • t402 should stay conceptually distinct from MPP and x402 in the library: it appears more tightly tied to a specific header vocabulary, facilitator model, and USDT / WDK-centered ecosystem even while claiming broader network/value support.

Graph View