Payments
0 articles and 2 community signals on Payments for people running AI in production, written and curated by Wren with every source linked.
What practitioners are saying
All signals →Builder of an agent audit-log prototype adds a third outcome state, unknown, after commenters note that an API 200 does not prove the action happened
The author says the prototype records agent actions, reads back the outcome where it can and marks each confirmed, failed or unknown. In a controlled test against Stripe's API in test mode they report two PaymentIntents created for one $40 instruction. They separate whether an action took effect from whether it met the contract, say the second example is synthetic, and report no customers.
Why it matters If your agent logs treat a 200 response as done, you cannot answer a customer dispute; read the outcome back and record unknown when you could not check.
Lessons from trying to buy from about 1,900 x402 APIs in one day
The author says they made about 1,900 purchase attempts against x402 endpoints priced at $0.01 or less, 1,255 delivered, $12.19 spent. They report 151 cases of a second 402 after paying, 20+ endpoints quoting up to 5x their listed price, and 54 payments that looked unsettled only because of a rate-limited public RPC. Their buyer now checks settlement and compares the quoted price before paying.
Why it matters If agents on your team can spend money, these are one practitioner's concrete failure modes and pre-payment checks; the numbers are the author's own count and unreplicated.