Skip to main content
x402 is an open payment protocol that brings blockchain payments into the HTTP standard. By reusing the HTTP 402 Payment Required status code, it lets developers handle onchain and agentic payments with the same tools they already use for APIs and web services. Instead of building complex wallet integrations or subscription systems, developers can treat payments like any other part of the HTTP request/response cycle. This approach works for web2 developers experimenting with paid APIs and for web3 builders who need a lightweight way to support pay-per-use APIs, agent-to-agent transactions, and micropayments. Read more about x402 here.

​
Access on Polygon

Polygon supports x402 v2 on mainnet and Amoy through the following facilitators:
  1. Polygon Mainnet Facilitator: https://x402.polygon.technology
  2. Polygon Amoy Facilitator: https://x402-amoy.polygon.technology
Both Polygon facilitators run x402 v2. Use the @x402/* packages in the Quickstart for Buyers and Quickstart for Sellers. Upgrading from V1? See Migration: V1 to V2.
Additional facilitators compatible with Polygon:

​
High-frequency payments with Paychannels

Each standard x402 payment is one onchain transfer. For workloads that pay many times per task, such as per-token inference, pay-per-call APIs, or streaming payments, Paychannels carry x402 payments through a channel instead: the payer deposits once, then pays with a signed voucher that a hub verifies in microseconds, and settlement to Polygon happens in batches. Paychannels use the x402 batch-settlement scheme, so the same 402 response can offer both. Paychannels are not limited to x402; they accelerate any high-frequency payment flow. Try a demo.

​
Build with x402

To implement x402 with Polygon and your applications or agents, follow the tutorials and guides in these docs. Alternatively, the x402 community has created multiple examples which can be adapted for Polygon.