Standardizes network and asset formats, allowing servers to accept stablecoins across various networks and even fiat currencies through the same interface, without needing custom logic for each.

Introduces optional structured data passing between clients, servers, and facilitators. This enables features like identity verification, multiple discovery mechanisms, and more, while letting developers extend the protocol without forking the main specification.

Cleanly separates the specification, SDK, and facilitators, making it easier to integrate new networks, payment schemes, and transports. The protocol fits wherever agents operate.

A new Discovery extension allows facilitators to automatically crawl and update pricing and routes, eliminating stale catalogs and manual updates.

Replaces deprecated X-* headers with cleaner, more compatible names such as PAYMENT-REQUIRED, PAYMENT-SIGNATURE, and PAYMENT-RESPONSE, improving integration with proxies, infrastructure, and frameworks.

The "payTo" field can now be an on-chain address, a role (e.g., "merchant"), or a callback that selects the recipient per request. This supports new use cases like x402-enabled marketplaces, multi-tenant APIs, and multi-chain catalogs.

Features a simpler, plug-in model for adding new chains, schemes, facilitators, and business rules without modifying core code.

Ensures V1 applications continue to function seamlessly, while V2 provides enhanced capabilities. Facilitators can advertise support for both versions.

Overall, x402 V2 enhances flexibility, power, and ease of use for paid APIs and agentic payments, building on millions of payments processed and extensive community feedback.

For the full specification and details, refer to the launch blog at https://www.x402.org/writing/x402-v2-launch

Standardizes network and asset formats, allowing servers to accept stablecoins across various networks and even fiat currencies through the same interface, without needing custom logic for each.

Introduces optional structured data passing between clients, servers, and facilitators. This enables features like identity verification, multiple discovery mechanisms, and more, while letting developers extend the protocol without forking the main specification.

Cleanly separates the specification, SDK, and facilitators, making it easier to integrate new networks, payment schemes, and transports. The protocol fits wherever agents operate.

A new Discovery extension allows facilitators to automatically crawl and update pricing and routes, eliminating stale catalogs and manual updates.

Replaces deprecated X-* headers with cleaner, more compatible names such as PAYMENT-REQUIRED, PAYMENT-SIGNATURE, and PAYMENT-RESPONSE, improving integration with proxies, infrastructure, and frameworks.

The "payTo" field can now be an on-chain address, a role (e.g., "merchant"), or a callback that selects the recipient per request. This supports new use cases like x402-enabled marketplaces, multi-tenant APIs, and multi-chain catalogs.

Features a simpler, plug-in model for adding new chains, schemes, facilitators, and business rules without modifying core code.

Ensures V1 applications continue to function seamlessly, while V2 provides enhanced capabilities. Facilitators can advertise support for both versions.

Overall, x402 V2 enhances flexibility, power, and ease of use for paid APIs and agentic payments, building on millions of payments processed and extensive community feedback.

For the full specification and details, refer to the launch blog at https://www.x402.org/writing/x402-v2-launch