In this piece
x402 Payments in 2026: Coinbase, Stripe, Cloudflare, AWS and Alternatives Compared
Last verified: 11 November 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.
Need an x402 feasibility and architecture check?
Discuss Your Payment StackWhat 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?
- Request. A client or AI agent calls a paid API, MCP tool, file or page.
- Challenge. The server returns
402 Payment Requiredand a Base64-encodedPaymentRequiredobject inPAYMENT-REQUIRED. - Authorization. The client selects an accepted scheme, network and asset, signs locally, and retries with
PAYMENT-SIGNATURE. - Verification and settlement. The resource server checks the payment itself or calls a facilitator’s
/verifyand/settleendpoints. - 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 managed settlement across several networks. Choose Stripe if finance needs payments in Stripe and the account can be approved for stablecoins. Choose Circle Gateway for very small, frequent USDC payments. Use Cloudflare for edge and MCP integration, and AWS AgentCore for buyer-side wallets, budgets and observability. Self-host if the control justifies the operational and compliance cost.
| Solution | Layer and status | Networks / funds | Public cost signal | Best fit |
|---|---|---|---|---|
| Coinbase CDP | Production facilitator; V1 and V2 | Base, Polygon, Arbitrum, Monad, World and Solana | 1,000 on-chain transactions/month free, then $0.001 each | Managed, multi-network x402 settlement |
| Stripe | Processor; account approval required | Base USDC; access depends on location and approval | Confirm account terms and rounding | Stripe balance, reporting, refunds and fiat payout |
| Circle Gateway | x402 payment method with batched settlement | USDC through Gateway balance | No per-payment gas; check current commercial terms | Sub-cent, high-frequency nanopayments |
| thirdweb | Facilitator and SDK stack | Broad EVM coverage plus documented Solana support | 0.3% facilitator fee in current pricing | Multichain EVM and configurable server wallets |
| PayAI | Third-party facilitator | Multiple EVM networks and Solana | 1,000 starting credits; $1 per 1,000 thereafter, usage varies by network | Low-cost settlement and alternative chains |
| Cloudflare | Workers/Agents SDK; gateway in closed beta | Gateway: US buyers and sellers; Coinbase CDP settlement | Confirm platform and settlement terms | Edge APIs, content and paid MCP tools |
| AWS AgentCore | Generally available buyer orchestration | Coinbase CDP or Stripe/Privy wallet connections | Provider wallet operations and related AWS services can cost extra | Agent fleets needing budgets, IAM and CloudWatch |
| Self-hosted | Reference SDK plus your facilitator | Whatever your bindings, nodes and tokens support | No protocol fee; you pay gas, RPC, operations and compliance | Maximum control and custom schemes |
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, Monad, 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.
The x402 Foundation facilitator guide recommends the public endpoint for development and testnet use, and a production facilitator or self-facilitation for mainnet. The paid unit at CDP is an on-chain transaction. Verification is free; batched vouchers can share a single claim transaction, while deposits, refunds and withdrawals count separately.
Does Stripe support x402?
Yes. In Stripe’s x402 integration guide, a seller creates a deposit address up front. After the facilitator settles a payment, the server records the transaction hash as a crypto PaymentIntent using transaction_verification. That step uses a preview API version. Keep a reconciliation record so a failed Stripe write does not trigger a second on-chain charge.
The machine payments availability table lists Base USDC for x402. Stripe’s lower-level PaymentIntent verification API also lists Tempo and Solana, but that list does not establish x402 support on those networks. US businesses outside New York can apply in the Dashboard; Stripe invites businesses outside the US to request access in more than 30 countries. Confirm approval, fees and rounding for this flow before pricing one-cent calls. Stripe documents card payments separately through MPP.
Cloudflare, AWS and Circle solve different layers
Cloudflare: deploy and enforce at the edge
Cloudflare’s Agents SDK has client and server helpers, including paid MCP tools. The separate Monetization Gateway entered closed beta on 30 September. Buyers and sellers must be based in the US. Sellers request access in the Dashboard; the gateway settles through Coinbase CDP.
Cloudflare has since announced a separate buyer-side product. Our Cloudflare Wallets guide for AI agents separates the live handle reservation from the planned Account Wallet, Virtual Wallets and spending controls.
AWS: let agents pay under policy
Amazon Bedrock AgentCore Payments became generally available on 18 August. The buyer-side service connects a Coinbase CDP or Stripe Privy wallet, enforces spending limits and records activity. It supports MPP and x402, including the x402 upto scheme for metered usage. Sellers still need their own acceptance and settlement path.
Circle: batch the tiny payments
Circle Gateway Nanopayments uses a prefunded USDC balance and batches signed payment authorizations. This spreads on-chain cost across many calls. Circle also offers a separate Facilitator Service for individual on-chain settlement. Compare minimums, settlement latency and refund operations for the chosen product.
x402 vs MPP vs Google AP2
| Protocol | Primary job | Relationship |
|---|---|---|
| x402 | Payment challenge, authorization and receipt for paid resources | Stablecoin-led today; extensible schemes and transports |
| Stripe/Tempo MPP | Machine payments with formal HTTP authentication semantics, sessions and multiple methods | Alternative protocol; MPP clients can interoperate with x402 services |
| Google AP2 | Agent mandates, authorization and auditability | Can complement x402 settlement through the A2A x402 extension |
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?
Budget for facilitator and processor fees, gas, wallet operations, FX, screening and engineering. At one million monthly on-chain transactions, the CDP facilitator fee alone is $999: 999,000 billable transactions × $0.001. A million paid API calls can settle in fewer transactions when batched. Compare the total cost per delivered call, and include the provider’s account terms.
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.
- Bind the payment to the resource. Validate recipient, amount, asset, network, validity window, nonce and the exact route or resource being fulfilled.
- Design idempotency before retries. Replayed HTTP requests must not duplicate paid work; settlement retries must not create ambiguous fulfilment.
- 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.
- Put policy around agent wallets. Use per-call and daily limits, asset/network allowlists, recipient rules, approvals for unusual spend and immutable audit logs.
- 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.
- 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.
- 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.
From paid endpoint prototype to production payments
Book an x402 Architecture ReviewSources 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 11 November 2026.
Frequently Asked Questions
Is x402 an official HTTP standard?
Does Stripe support x402?
Coinbase or Stripe for x402?
What is an x402 facilitator?
Is x402 limited to USDC or Base?
Can x402 monetize MCP servers?
Does x402 eliminate accounts and API keys?
Is x402 production-ready?
Final thoughts
x402 makes payment a machine-readable HTTP negotiation. That is powerful for APIs, MCP tools, agent-to-agent services and content priced below conventional card economics. It does not make settlement, compliance or delivery atomic.
The best stack is usually layered: choose the protocol version first, then the buyer wallet and controls, the seller runtime, the payment scheme, and the facilitator or processor. Coinbase, Stripe, Circle, Cloudflare and AWS can coexist in one architecture because they solve different problems. Compare the layers, test the failure paths, and buy only the operations you do not want to own.