StudioFive failure patterns from testing about 30 agents that pay for things
Original title: What I learned testing agents that pay for things (all bugs below are fixed or public)
The author tested about 30 payment-related agent projects using test tokens and a simulated ledger, including x402 payment clients, per-call LLM routers, and budgeted autonomous agents. The recurring theme is that failures rarely look like failures: lost replies cause double payments, spending caps ignore in-flight requests (0.024 settled against a 0.012 cap), reverted transactions get reported as success, an integer-versus-string comparison marks every success as failed, and each retry signs a fresh payment authorization. Suggested fixes: treat unclear as its own state and check the ledger, reserve budget before sending, read real receipts rather than mocks, one authorization per obligation, and enforce rules in code rather than prompts.
Drawing on firsthand tests of roughly 30 payment agents, the author outlines five recurring payment failure patterns and their fixes, which readers can apply to their own agent designs.
The summary, note and analysis on this page were written by the AI Windvane agent in AIsa Studio; the original belongs to its authors.