Agentic Commerce Is Here: Agent Payments and Real World AI Workflows
I showed business teams what can go wrong when an AI assistant buys a service, and why a successful payment is not the same as a finished task.
AI Summit Seoul · South Korea · 19 August 2026
A Paid Download Is Not a Finished Task
I asked an AI assistant to store a photograph with a paid service and bring back the original unchanged. The service took payment but delivered a text file instead of the photograph. Another download was damaged. The assistant eventually recovered the original, which I compared with the starting file before accepting the result.
The talk uses that failure to explain what businesses need to retain when software shops on their behalf: approval of the purchase, a check of the delivery, and a way to stop or seek correction when something goes wrong. I also compared shopping experiences that finish a purchase inside the assistant with those that send the customer to the merchant's checkout.
Checking Delivery After Payment
Settlement Versus the Returned File
The storage example used Machine Payments Protocol (MPP) with settlement on Tempo. One download returned 66 bytes of ASCII text instead of a JPEG. Recovery took six attempted paths, multiple paid transactions, and tool changes. Comparing the recovered original with the starting file supplied the completion check that a payment confirmation could not.
Discovery, Terms, and Checkout
MPP Services and x402 Bazaar help find APIs, but the service request supplies the final price and terms. I treated discovery, customer authority, wallet limits, and settlement as separate concerns: finding a seller or having funds available does not approve a purchase.
The checkout comparison covered Qwen, Taobao Instant Commerce, and Alipay AI Pay versus the earlier merchant handoff in Shopee and Shopify. Completing checkout inside an assistant changes the customer experience, while the commerce platform remains the system of record for the purchase.
Recovery Within an Approved Budget
I proposed a task budget covering storage, retrieval, retries, and verification, with a stop at the limit. Before retrying an uncertain payment, the assistant should inspect its status rather than risk paying again. Changed terms return for approval; a wrong result calls for correction or refund, not silent substitution of sellers, accounts, or payment methods.
Internal Workflow Testing
The talk also drew on an internal suite of 174 test cases covering quotations, orders, invoices, payments, calendars, and business rules. After one autonomous correction cycle, 105 passed, 44 were partial, 21 were blocked, two failed, and two were not run. These results describe that test workload, not a general business success rate.