x402 V2: What's New in the Internet-Native Payments Protocol

Originally posted at blog.payin.com

The x402 protocol has hit a major milestone. Since its launch in May 2025, it has processed over 100 million payments. Now, with the release of V2 on December 11, 2025, the internet-native payments standard evolves beyond single-call transactions into a comprehensive payment infrastructure.

Let's break down what's new and why it matters.

The Evolution from V1 to V2

The original x402 specification elegantly solved a core problem: enabling HTTP-native payments without intermediaries. You make a request, get a 402 response with payment requirements, pay, and access the resource.

V2 keeps this simplicity while addressing the real-world needs that emerged from production usage:

• 
  Multi-chain complexity — Different networks, different tokens, different routing


• 
  Repeated access — Paying for every single request is inefficient


• 
  Developer experience — Integrations required too much custom logic


• 
  Ecosystem growth — Adding new chains meant modifying core specs

What's New in V2

Unified Payment Interface

One of the biggest friction points in crypto payments is dealing with multiple networks and assets. V2 standardizes how networks and assets are identified across the entire protocol.

Supported Networks:

├── Base (Coinbase L2)

├── Solana

├── Other L2s

└── Traditional rails (ACH, SEPA)

The key insight: no custom logic required. Whether a user pays with USDC on Base or SOL on Solana, the protocol handles the differences. Services can accept payments from any supported chain without building chain-specific integrations.

Extensible Architecture

V2 introduces a clean separation between three layers:

This plugin-driven architecture means developers can register new chains and payment schemes without touching the core specification. Want to add support for a new L2? Write a plugin. New stablecoin? Plugin. The protocol grows without fragmenting.

Wallet-Based Access & Sessions

Here's where V2 gets interesting. The original model required a payment for every resource access. Fine for one-time purchases, problematic for repeated interactions.

V2 introduces the @x402/paywall package with session support:

How it works:

1. User connects wallet and makes initial payment


2. Service issues a session token tied to wallet identity


3. Subsequent requests within the session skip the full payment flow


4. No additional on-chain interactions needed

This enables subscription-like experiences without traditional subscription infrastructure. Your wallet becomes your identity and your access credential.

Automatic Discovery

Services now expose structured metadata that facilitators automatically crawl. Pricing, supported networks, and payment routes stay synchronized without manual updates.

For developers, this means:

• No hardcoding facilitator endpoints


• Automatic route optimization


• Real-time pricing updates

Multi-Facilitator Support

V2 treats multiple facilitators as first-class citizens. Developers can express preferences:

// Prefer Solana for lower fees

{ prefer: "solana" }



// Only accept USDC

{ assets: ["usdc"] }



// Use specific facilitator

{ facilitator: "preferred-facilitator.com" }

The SDK handles chain selection and payment routing automatically. If your preferred path is congested or expensive, it falls back to alternatives.

New HTTP Headers

V2 modernizes the HTTP header structure:

The SIGN-IN-WITH-X header is particularly notable. It enables wallet-based authentication following the CAIP-122 standard, bringing Sign-In with Ethereum (SIWE) patterns to the x402 ecosystem.

Backward Compatibility

V2 maintains backward compatibility with V1 implementations. The reference SDKs support both versions, so existing integrations continue working while you migrate to new features at your own pace.

What This Means for Developers

Simpler Integrations

Before V2, supporting multiple chains meant writing chain-specific code. Now:

// V2: One integration, all chains

import { x402 } from '@x402/sdk';const payment = await x402.pay({

  resource: 'https://api.example.com/premium',

  // SDK handles chain selection automatically

});

Better User Experience

Sessions mean users don't pay per-request. Automatic discovery means services always have current pricing. Multi-facilitator support means payments route through the best available path.

Future-Proof Architecture

New chains and payment methods integrate as plugins. Your integration today will support networks that don't exist yet.

The Bigger Picture

x402 V2 represents a maturation of internet-native payments. The protocol has moved from "proof of concept" to "production infrastructure" status.

Key metrics tell the story:

• 
  100M+ payments processed since May 2025


• 
  600+ builders in the community Telegram


• 
  Multi-chain support across major L2s and traditional rails

The vision remains the same: HTTP 402 as the standard for web payments, just as HTTP 200 is the standard for successful responses. V2 brings that vision closer to reality by solving the practical problems that emerged at scale.

Getting Started

The x402 V2 specification and SDKs are available on GitHub through the Coinbase Developer Platform. The community is active on Telegram with 600+ developers building on the protocol.

x402 is an open protocol for internet-native payments. Learn more at x402.org.