x402 Payments in 2026: Coinbase, Stripe, Cloudflare, AWS and Alternatives Compared

Last verified: 12 July 2026. x402 is an open payment protocol built on HTTP's 402 Payment Required response. It lets software receive machine-readable payment terms, sign an authorization, retry the request and receive the paid resource. The protocol is not a processor: Coinbase, Stripe, Circle, wallets, facilitators and self-hosted infrastructure implement different parts of the stack.

That distinction is the whole buying decision. Coinbase and Stripe are not direct substitutes for Cloudflare and AWS. Coinbase CDP operates a production facilitator. Stripe turns x402 payments into familiar PaymentIntents, reporting and fiat settlement. Cloudflare gives Workers and agents x402 tooling. AWS orchestrates buyer-side agent payments. Circle batches nanopayments. You can combine several of them.

What is x402, exactly?

x402 is an open, HTTP-native payment protocol that uses the 402 response to let software request, authorize and prove payment before receiving a resource. A client receives payment terms, signs a payload, retries the request, and the server verifies and settles it directly or through a facilitator.

It is important not to overstate the word “standard.” RFC 9110 still reserves HTTP 402 for future use; HTTP itself does not define payment semantics. x402 supplies the application-layer schemas, headers and flow. In April 2026, Coinbase contributed the project to the Linux Foundation's x402 Foundation, giving the protocol a neutral governance home.

How does an x402 V2 payment work?

1. Request. A client or AI agent calls a paid API, MCP tool, file or page.
2. Challenge. The server returns 402 Payment Required and a Base64-encoded PaymentRequired object in PAYMENT-REQUIRED.
3. Authorization. The client selects an accepted scheme, network and asset, signs locally, and retries with PAYMENT-SIGNATURE.
4. Verification and settlement. The resource server checks the payment itself or calls a facilitator's /verify and /settle endpoints.
5. Fulfilment. The server returns the resource and a settlement receipt in PAYMENT-RESPONSE.

The V2 specification is the recommended baseline. It uses CAIP-2 network identifiers and separates transports, payment schemes and extensions. Older V1 examples use X-PAYMENT; do not mix those headers into a V2 integration.

Which x402 solution should you choose?

Choose Coinbase CDP for the shortest crypto-native route to a managed, production facilitator on several networks. Choose Stripe if Stripe reporting, refunds and fiat settlement matter more than broad network coverage and you qualify for its private preview. Choose Circle Gateway for extremely small, high-frequency USDC payments. Use Cloudflare for edge and MCP integration, and AWS AgentCore for buyer-side agent wallets, budgets and observability. Self-host when control justifies the operations and compliance burden.

This table is a snapshot, not a quote. Network support, geography, pricing and preview status are moving quickly. Verify the linked primary documentation before approving a production budget.

Coinbase x402: the reference managed facilitator

Coinbase CDP's facilitator verifies signed payloads, submits settlement and performs KYT screening without taking custody of the buyer's funds. Its documented production endpoint supports Base, Polygon, Arbitrum, World and Solana, with EIP-3009, Permit2 and SPL capabilities varying by network and scheme. Pricing is currently 1,000 transactions per month free and $0.001 thereafter.

Two caveats matter. The public x402.org/facilitator is testnet-only; production requires CDP credentials or another facilitator. And Coinbase's pages describe both gas sponsorship and separately paid on-chain gas. Treat gas as configuration-dependent and confirm the exact network, token and scheme rather than marketing an “all free” payment.

Does Stripe support x402?

Yes. Stripe documents x402 support for machine-to-machine payments in private preview. Stripe creates a crypto PaymentIntent and deposit address, captures it after on-chain funds settle, and puts the funds in the seller's Stripe balance. That brings ordinary Stripe reporting, refunds and fiat settlement to an x402 endpoint.

The current scope is narrower: live x402 uses USDC on Base, access requires US eligibility and enablement, and Stripe lists 1.5% per successful charge, rounded to the nearest cent. Charges can be as low as 0.01 USDC, so test the effective economics at one-cent scale. Stripe also supports its separate Machine Payments Protocol (MPP). MPP and x402 both use HTTP 402 patterns, but they are not the same protocol.

Cloudflare, AWS and Circle solve different layers

Cloudflare: deploy and enforce at the edge

Cloudflare Agents and Workers provide first-class server and client helpers, including paid MCP tools. Their examples use Coinbase's facilitator; Cloudflare is not automatically your settlement provider. Its Monetization Gateway was announced in July 2026 as early access/waitlist, so do not plan around it as a generally available managed product yet.

AWS: let agents pay under policy

Amazon Bedrock AgentCore Payments is a preview buyer-side service. It detects a 402 challenge, checks a time-bounded budget, uses Coinbase CDP or Stripe/Privy wallet infrastructure to sign, retries the call, and records the flow in AWS observability. It does not replace the seller's facilitator.

Circle: batch the tiny payments

Circle Gateway Nanopayments demonstrates why x402 is a negotiation protocol rather than one rail. A buyer deposits USDC once, signs gas-free authorizations for individual calls, and Circle nets many of them into batched on-chain settlement. Circle documents payments down to $0.000001, which targets workloads where one on-chain transaction per request would be irrational.

x402 vs MPP vs Google AP2

Not every product that returns status 402 implements x402. Check its actual headers, schemas and payment semantics. Cloudflare Pay Per Crawl, Visa's agent protocols and MPP may use 402 while speaking a different protocol.

What does x402 really cost?

The protocol has no protocol fee. The system does. Your cost can include facilitator or processor fees, network gas, token approvals, wallet operations, RPCs, FX and off-ramp, custody, monitoring, fraud/KYT and engineering. At one million monthly settlements, Coinbase's published facilitator fee alone is roughly $999 after the free tier; Stripe's percentage model depends on payment value and cent rounding; self-hosting replaces vendor fees with infrastructure and people.

The correct denominator is not “price per transaction” but cost per successfully delivered paid action: include rejected payments, chain failures, agent retries, duplicate requests, refunds and support. Batch or meter tiny actions if fixed operational cost dominates their value.

Production security and compliance checklist

x402 is trust-minimizing, not trust-free. Signed authorizations constrain how funds move, but production still depends on wallet security, TLS, facilitator availability, smart contracts, chain finality and application delivery.

1. Bind the payment to the resource. Validate recipient, amount, asset, network, validity window, nonce and the exact route or resource being fulfilled.
2. Design idempotency before retries. Replayed HTTP requests must not duplicate paid work; settlement retries must not create ambiguous fulfilment.
3. Choose verify/work/settle ordering. Expensive work after verification can still fail to settle; settling first can leave a buyer paid but unserved. Record receipts and define compensation.
4. Put policy around agent wallets. Use per-call and daily limits, asset/network allowlists, recipient rules, approvals for unusual spend and immutable audit logs.
5. Plan refunds and disputes. Exact on-chain payments are push payments; a refund is normally a new seller-originated transfer unless your processor supplies a refund workflow.
6. Map compliance by role and market. “No account needed” between buyer and endpoint does not remove merchant onboarding, KYC/KYT, sanctions, tax, accounting, consumer or data obligations.
7. Monitor the whole trace. Challenge, signature, verify, settle, chain confirmation and resource delivery need one correlation ID and alertable states.

"The protocol demo is one middleware call. The production system is wallet policy, idempotency, settlement accounting, compliance and a failure path that does not charge twice."

Build, buy or combine?

• Buy a facilitator when speed, supported networks, KYT and predictable operations matter more than custom settlement logic.
• Use Stripe when finance already lives in Stripe and fiat payout plus refunds are decisive.
• Combine layers when Cloudflare serves the paid endpoint, Coinbase or Circle settles it, and AWS controls the buyer agent.
• Self-host when you need a custom scheme, data boundary or chain and can own RPC uptime, signer security, gas, monitoring, upgrades, compliance and incident response.

A credible proof of concept should test one real paid resource, both V1 rejection and V2 success paths, duplicate and expired signatures, settlement failure, budget enforcement, refunds, observability and an end-to-end cost model. Then decide whether the abstraction earns its place.

Sources and methodology

We compared public protocol specifications and primary vendor documentation, not affiliate pages. Besides the sources linked above, useful implementation references include thirdweb's facilitator docs, PayAI pricing and the x402 ecosystem directory. Commercial terms and supported networks can change; this article records what the providers published on 12 July 2026.