Why Stripe doesn\u2019t fit agent payments
Stripe is excellent at what it was designed for: a human enters card details, and you charge them monthly. Agent payments break every part of that model. The customer is software, not a person — it cannot complete a checkout form, pass 3-D Secure, or store a card. Amounts are cents or fractions of a cent per API call, where Stripe’s per-transaction fee (~$0.30 + 2.9%) is larger than the payment itself. And settlement takes days, while an agent needs the request fulfilled in the same HTTP round-trip it paid in.
Stripe itself recognizes this — it co-built the Agentic Commerce Protocol (ACP) with OpenAI — but the core card product remains a poor fit for machine-to-machine micropayments. The open-source alternative is x402: HTTP-native, stablecoin-settled, with per-request pricing that actually works at $0.001.
What to look for instead
- Per-request pricing below $0.01 without fees eating the payment
- API-native flow — no checkout form, no card on file, no 3DS
- Machine identity and spend policies instead of customer accounts
- Settlement fast enough to fulfill the paid request immediately
- Open source, self-hostable, no platform lock-in