x402 and Stripe both move money for digital products, but they are built for different payers. Stripe is optimized for human checkout; x402 is optimized for software paying per request.
The core difference
Stripe expects an account, API keys, and usually a stored card or a hosted checkout a human completes. x402 expects none of that: the price is returned inline as a 402 response and the client pays by signing a stablecoin authorization that rides along with the retry. There is no onboarding step between discovering a resource and paying for it.
Where each fits
Stripe: subscriptions, one-time human purchases, invoicing, marketplaces with payouts, rich dispute/refund tooling.
x402: an agent or script paying per API call, micro-amounts, no-signup access, machine-to-machine commerce where a human is not in the loop.
See the x402 side in action
With x402 there is nothing to sign up for — fund a wallet and call. Try it free first:
cURL — free trialbash
# Free trial call — real data, no payment, no signup (1/endpoint/hour):
curl "https://2s.io/api/weather/zip?zip=94103&trial=1"
Not generally. They target different payers. Stripe is best for human checkout, subscriptions, and invoicing. x402 is best for software paying per call with no signup. Many businesses could use both.
Why use x402 instead of Stripe for an API?
If your callers are agents or scripts, x402 removes signup, API-key management, and minimums — the caller pays per request in USDC and you settle on-chain. That is friction Stripe is not designed to remove for machine callers.
Does x402 handle refunds and disputes like Stripe?
No. x402 is a lightweight pay-per-request settlement, not a full payments platform. It has no built-in dispute/refund tooling; settlement is on-chain and per call.